Advanced Template Features

Syntax:

format-number=" "

#,###.##  (Typical Currency with cents)

#,###     (Comma delimited whole number)

#.###     (EU formatting)

#.###,##

{{!Opportunity.amount format-number="#,###.##"}}

43222300.8 ➤ 4,222,300.80

{{!Opportunity.amount format-number="#,###"}}

43222300.8 ➤ 4,222,301

{{!Opportunity.amount format-number="#.###"}}

43222300.8 ➤ 4.222.301

• Larger numbers will still follow the pattern even if they exceed the 4 digits shown in the pattern. Rounding is applied when precision exceeds formatting.
• If you need to include a currency symbol, you can add it just before the merged field. E.g . ${{!Opportunity.amount format-number="#.###"}}

Syntax:

format-date=" "

{{!opportunity.createdDate format-date="MM/dd/yyyy"}}

2018-10-28 ➤ 04/04/2017

{{!opportunity.createdDate format-date="MMMMM"}}

2018-10-28 ➤ October

{{!opportunity.datetime__c format-date="MM/dd/yy hh:mm:ss TZ:America/New_York"}}

2018-10-28 ➤ 10/28/2018 12:56:32 EST

• Patterns are case sensitive. E.g. MM=month while mm=minutes. Reference to available patterns.

• Times are formatted per the database time (GMT).
• Time zones must be written using Java time codes.
• Only Salesforce-supported time zones are accepted.
• Long descriptions (e.g. Month, day of week) are in English. You can use formula fields if needed to meet a specific requirement.

Syntax:

{{!opportunity.checkbox__c checkbox="true"}}

Displays a checkbox with a dotted white border; includes a black checkmark if checked.

{{!opportunity.checkbox__c checkbox="black"}}

Displays a checkbox with a solid black border; fills in with black and includes a white checkmark if checked.

{{!opportunity.checkbox__c checkbox="radio"}}

Displays a radio button.

• When this attribute is added, the merge field will display as the checkbox in its current state on the record once the document is generated.
• Currently not supported in DOCX file format

Syntax:

{{!Check__c.RoutingNumber__c MICR="11"}}

To adjust spacing between MICR characters:

{{!Opportunity.Description MICR="[FONTSIZE (REQUIRED)],[SPACING (OPTIONAL)]"}}
e.g.
{{!Opportunity.Description MICR="20"}}
{{!Opportunity.Description MICR="20,-5"}}

{{!Opportunity.Description MICR="20,5"}}

• The output is a series of images that can be used in PDF generation of checks. Only digits and ‘t,’ ’o,' ’a,’ ’d,’ are transformed. Other characters are ignored.
• The number following MICR represents the font width. E.g.  MICR="16" will be larger than MICR="8".

• Spacing defaults to 0 if it is not specified. As shown, negative spacing values are allowed. The lower the spacing value, the closer together MICR characters.

Syntax:

{{!Opportunity.Description CR="[OCR-A/OCR-B],[FONT SIZE (REQUIRED),[SPACING (OPTIONAL)]"}}

Example:
{{!Opportunity.Description CR="OCR-A,20,5"}}

{{!Opportunity.Description CR="OCR-B,20,5"}}

• The output is a series of images that can be used in PDF generation of checks. Only digits 0-9 are transformed. Other characters are ignored.

• Spacing defaults to 0 if it is not specified. Negative spacing values are allowed. The lower the spacing value, the closer together OCR characters.

Syntax:

{{!contact.billingStreet ToUpperCase="true"}}

123 Main Street, Apt 3 ➤ 123 MAIN ST, APT 3

Syntax:

{{!contact.billingStreet ToLowerCase="true"}}

123 MAIN ST, APT 3 ➤ 123 main street, apt 3

Syntax:

{{!account.greeting__c RTL="true"}}

שלום➤ םולש

• Using the RTL merge field attribute will transform merge field data only, not static text.
• To apply RTL for both merge fields and static text,  use the following style in the template source:

<rtl>reverse</rtl>

• When using <rtl> tags, there is no need to add the RTL attribute to your  merge fields. You can wrap an entire template in <rtl> tags to transform both merge field data and static text.
• Note that <rtl> tags will not work properly with text that breaks across two lines in the generated document. You should use separate <rtl> tags for each line if text breaks across two lines.

Syntax:

{{!product2.color translate="true"}}

BLUE ➤ BLEU

Click here to learn more.

• This feature leverages Salesforce toLabel() function within a SOQL query. It is particularly useful for orgs that have Translation Workbench enabled. Translate keyword will cause an error if used on field types that do not support toLabel().
• For related list translations, or lookup fields, you should use direct SOQL query. If you set the class to "none" then only the data is returned – not in a table format.  Here is an example usage from the S-Docs template source:

<!--{{!
<LineItemsSOQL>
<class>none</class>
<soql>Select tolabel(color__c) From product2 where id='{!ObjectID15}' and toLabel(color__c) =’BLEU’</soql>
<column>color__c</column>
</LineItemsSOQL>
}}-->

• Additionally, for fields merged within related lists, you may find the substitute column attribute feature useful.

Syntax:

{{!Opportunity.Name replaceAll="ReplaceThis1,ReplaceWithThis1,ReplaceThis2,ReplaceWithThis2"}}

Syntax:

{{!Opportunity.EncryptedField__c encrypt="true"}}

• This attribute is not supported for named query merge fields.

Syntax:

{{!Opportunity.PicklistField__c Display="true"}}

• In most cases, picklist field values are identical to their API names. This attribute covers instances when the two differ.

Syntax:

{{!Opportunity.Multi_Select_Picklist_Field__c msnl="true"}}

Syntax:

{{!Opportunity.Long_Field__c breakeverynchars="10"}}

supercalifragilisticexpialidocious ➤ supercalif ragilistic expialidoc ious

• Negative, zero, or blank values will not insert any line breaks.
• If you are using this attribute with PDF-Upload templates, force the merged text to wrap by adding the following code to the Additional Style field:

white-space: normal !important;

Syntax:

{{!Object.Field toCells="Number of Cells to Generate,CSS class to apply to table cells"}}

Example:

{{!Opportunity.Three_Character_Code__c toCells="3,table873"}}

123 ➤ 1, 2, and 3 would be in separate table cells, which would each have the table873 CSS class applied to them.

• Specifying more cells than the field value will result in blank cells being created.

Syntax:

{{!Object.Field strip-html="True"}}

• For related lists, use the type="text" column attribute (explained in the Related List Column Attributes section of this article)

Syntax:

{{!Object.Field justifyNewlines=“HTMLElement”}}

Example:

INPUT: <div style=“text-align: justify;”>{{!Opportunity.Long_Text_Area__c justifyNewlines=“div”}}</div>

OUTPUT: <div style=”text-align: justify;”>Paragraph One</div><div style=”text-align: justify;”>Paragraph Two</div>

• This attribute can only be used for style=“text-align: justify”
• This attribute cannot be used with Microsoft templates

Syntax:

{{!Object.Field blobToString=“true”}}

• The blob content must be able to be converted to a string or well-formed HTML
• This attribute is also available as a related list column attribute

Substitute functionality can be useful for translating values to different languages for a template. While you may be able to do the same using a Salesforce formula field, this can drastically reduce the number of formula fields you would need to create.

Syntax:

<column substitute="value1tomatch, value1ToSubstitute, value2ToMatch,Value2ToSubstitute,

…,

OptionalCatchall-substitution">Field__c

</column>

If the substitute list contains an odd number of values, then the last value will be the catch-all that is substituted when no matches are made.

• Substitute a checkbox for German language. values:substitute="true,Ja,false,nien"
• Matches are made ignoring case sensitivity and white spaces are trimmed, but the substitute values are exact.
• For checkbox fields use true and false as the value to match on.
• For organization purposes you can optionally use parenthesis to organize your list, e.g.:

substitute="(1,one),(2,two),(3,three)"

• If your value is null, you should not
  use the substitute attribute but rather use the  nullprefix= attribute that will
  allow you to insert a value whenever null data is encountered for that field.
• If you are matching a numeric value, the precision needs to also match.

<column substitute="2.00,2">quantity</column>

• Example:  Use Substitute feature to correctly display the full month Name of field that contains the month number:

<column substitute="1, Januar,
2, Februar,
3, März,
4, April,
5, Mai,
6, Juni,
7, Juli,
8, August,
9, September,
10,Oktober,
11,November,
12,December,
unknown">MonthNumber__c</column>

1) substitute matches against (and replaces) the ENTIRE string, where as replaceall matches against (and replaces) all substring appearances of the specified string.

2) There is no "else" condition in replaceall (since we're replacing substrings, an "else" condition would be nonsensical)

This attribute supports regexs.

Syntax:

<column replaceall="replaceThis1,replaceWithThis1,replaceThis2,replaceWithThis2,...replaceThisN,replaceWithThisN">

Regex Syntax:

Start your replaceall string with [regex] (including brackets)

For example, say you want to replace all        "a) This is a test", "b) This is a test", etc. with " a) This is a test", " b) This is a test" but NOT replace anything that looks like "1. This is a    test", "2. This is a test", etc. (i.e. you want to       indent a) b) c) but not 1. 2. 3. and the data   structure / related list formatting prohibit     simpler solutions like using <li></li>). To    achieve this, you could use the following:       <column replaceall="[regex]([a-zA-Z]\)),     &nbsp;&nbsp;&nbsp;&nbsp;$1">

Syntax:

<column showcolumn="{{!Object.Fieldname}} == 'FieldValueThatTriggersColumnShowing'">...</column>

Note that the column will be hidden if the syntax resolves to false.

If your table has a header row, you will need to apply the same condition to the header row as a RENDER statement:

<!--RENDER='{{!Object.Fieldname}}' == 'FieldValueThatTriggersColumnShowing'--><th>Column Name</th><!--ENDRENDER-->

This is useful for inserting blocks of information that already contains formatting/markup.

If you wish to strip the HTML tags from your rich text field, you can specify type="text"

If you want to display a checkbox or radio button image (checked and unchecked) rather than the database values of true/false or yes/no, you can use type="checkbox" or ="radio"

Syntax:

<column type="rtf">Your content goes here.

</column>

<style type="text/css">
.sdcheckbox {
width: 10px;
height: 10px;
border: 1px solid #73AD21;
}
</style>

• type="chackbox" Currently not supported in DOCX file format

Syntax:

<column header="YourHeaderHere">

Syntax:

<column format-number="#,###.##">

#,###.##

#.###

#.###,##

For example, if a number in your column was stored as 123456 and
you chose the 2^nd type listed above, the number would appear as 1,234.56

Syntax:

<column format-date="MM/dd/yyyy">

Syntax:

<column mergenext="true">

• You can merge these two columns together and the resulting column will be

$12

$4

• Prefix and postfix are useful to put any spacing between cell values.

Note: mergenext is not supported when using group-by functionality.

Syntax:

<column colspan="4">

Syntax:

<column newrow ="4">

Syntax:

<column prefix="YourStringHere">

Syntax:

<column nullprefix="YourStringHere">

Syntax:

<column postfix="YourStringHere">

4                  dollars

Syntax:

<column nullpostfix="YourStringHere">

Syntax:

<column allprefix="YourStringHere">

Syntax:

<column allpostfix="YourStringHere">

Syntax:

<column abfprefixouter=",">

Syntax:

<column startIndex="3">

<lineitems>
<class>table646</class>
<listname>opportunitylineitems</listname>
<column startIndex="3">rownum</column>
<column>PricebookEntry.Product2.name</column>
<column>PricebookEntry.Product2.description</column>
<column>unitprice</column>
<column>quantity</column>
<column>totalprice</column>
</lineitems>
}}-->

This example would output a table with row numbers beginning at 4.

Syntax:

<column render="CONDITION_1,output_value_1,CONDITION_2,output_value_2...DEFAULT OUTPUT VALUE IF ALL RENDERS EVALUATE TO FALSE">

• This feature is only supported with <lineitemsSOQL> statements
• You must use <soql>...</soql> tags and include any field specifed in your subsitute="..." attributes in your SOQL query
• You should not specify a field between the <column></column> tags. Doing this may cause issues
• You can use RECORD.Field_Name to use related list record data fields within the render="..." attribute
• Any tags inside of the column render (e.g. <span>) will need to have the <> characters escaped (lt#, gt#)

Examples:

<column render="RECORD.Product_Type__c STARTSWITH Vacuum && RECORD.Product_Type__c ENDSWITH Cleaner,RECORD.Vacuum_Name__c,Not a Vacuum"></column>

• If the Product's Type field starts with Vacuum and ends with Cleaner, the column will output the name of the vacuum, otherwise the column will output "Not a Vacuum."

<column render="RECORD.Title==null,No Title Available,RECORD.Title"></column>

• If the Contact's title field is blank, the column will output "No Title Available," otherwise it will output the Contact's title.

You can also use nested render statements:

<column render="RECORD.Country__c == usa,[RENDER1]RECORD.City__c == new york,S-Docs HQ,[RENDER2]RECORD.City__c == ann arbor,S-Docs Innovation Center,[ENDRENDER2][ENDRENDER1],Work From Home"></column>

• If the record's Country field is USA, and the city is New York, the column will output "S-Docs HQ." If the record's Country field is USA and the city is Ann Arbor, the column will output "S-Docs Innovation Center." If the record's Country field is not USA, the column will output "Work From Home."

<column type="rtf" render="RECORD.StageName == 'Closed', lt#span style='color:red;'gt# Closed lt#/spangt#,Open"></column>

• If the Opportunity is Closed, the column will output "Closed" in red. Otherwise, the column will output "Open" in the default font color.

Syntax:

<column breakeverynchars="10">

Syntax:

<column addToEmail="To">

Syntax:

<column blobToString=“true”>

• The blob content must be able to be converted to a string or well-formed HTML
• This attribute is also available as a merge field attribute