Difference between revisions of "Template Variables"

From LongJump Support Wiki
imported>Alice
(Removed gif)
 
imported>Aeric
Line 13: Line 13:
*[[Workflow Templates]], which describe email communications from [[Workflows]]
*[[Workflow Templates]], which describe email communications from [[Workflows]]


A convenient Template Variable Builder is provided, to look up the field names, based on category.
A convenient Template Variable Tool is provided to look up field names.


 
==Template Variable Tool==
==Template Variable Builder==
{{:Template Variable Tool}}
{{:Template Variable Builder}}


== Template Variable Syntax ==
== Template Variable Syntax ==
{{:Field Scripting Variables}}
{{:Field Scripting Variables}}


==Template Variable Resources==
==Template Variable Resources==
{{:Template Variable Resources}}
{{:Template Variable Resources}}
 
<noinclude>


[[Category:Glossary]]
[[Category:Glossary]]
</noinclude>

Revision as of 21:17, 19 July 2011

Template Variables are used to personalize communications from the platform.

For example, instead of a generic "Dear Sir" salutation, messages can be personalized:

"Greetings Carl! You're invited to Friday nite Yappy Hour at the Dog Owners Club! Hope to see you and Bruiser there! "

Template variables embedded into HTML templates provide this mail merge capability.

Learn more: HTML Resources

HTML templates can be used in these areas of the platform:

A convenient Template Variable Tool is provided to look up field names.

Template Variable Tool

Template Variable Syntax

Depending on where they are used, variables may need to be specified with braces (${variable}) or without them ($variable). (See Template Variable Resources for a list of contexts in which variables are available.)

Except for that difference, variables are standardized using the following syntax:

$objectname.fieldname
Where objectname is the name of the tab or object (Prospect, Account, Contact, etc.) and the fieldname is the name of the field (owner, description, etc.)
Second-degree Related Objects

Second-degree related objects can also be used in templates, and provide the ability to to drill down to one level of the hierarchical lookup from the object.

Second-degree related object variables are standardized using the following syntax:

$objectname.fieldname.seconddegree
Where objectname is the name of the tab or object (Prospect, Account, Contact, etc.), fieldname is the name of the field (owner, description, etc.) and seconddegree is the name of the second-degree related object
Examples
  • To include the email address of a primary contact in a prospect, use this syntax:
$prospect.primary_contact_id.email
  • To get the tax_type of an autopolicy insurer, use this syntax:
$autopolicy.insurer.tax_type
Where 'autopolicy' and 'insurer' are objects, and 'tax_type' is a field in the 'insurer' object

Template Variable Resources

Learn more about Template Variables: