Template Assistant

You can also assign text styles to Rich Text Content Controls to always format them accordingly.

To do so, follow the following steps:

The following table provides an overview of formatting tags that can be used to adjust the document output via the Template Assistant:

Line Break

[n/]

Text[n/]Text

Bold

[b] … [/b]

[b]Text[/b]

Underlined

[u] … [/u]

[u]Text[/u]

Italics

[i] … [/i]

[i]Text[/i]

Tab Stop

[t/]

Centered

[hcenter] … [/hcenter]

[hcenter] Text Text [/hcenter]

Align Right

[hend] … [/hend]

[hend] Text Text [/hend]

Justified

[hdistribute] … [/hend]

[hdistribute] Text Text [/hdistribute]

Uppercase

| Upcase

{{Text | Upcase }}

Hyperlink

[a target="linkTargetUri"] … [/a]

For normal hyperlinks:

[a target="https://{{Entity.Property.Value}}";] {{Entity.Property.Label}}[/a]

For e-mails:

[a target="mailto:{{Entity.Property.Value}}"]{{Entity.Property.Value}}[/a]

The following is an example for a use case of formatting tags:

The labels in the following code excerpt are written in uppercase letters and displayed in bold.

The values, on the other hand, are written in standard formatting without uppercase letters.

Additionally, the data set is divided into three lines using line breaks.

{{User.First_Name.Value}} {{User.Last_Name.Value}}[n/][b]{{User.Phone.Label | Upcase }}:[/b] {{User.Phone.Value}}[n/][b]{{User.Email.Label | Upcase }}:[/b] 
{{User.Email.Value}}

The outcome for a user called empower Admin would be the following:

If conditions can be used to make the display of values more flexible.

For example, you can define that the label for mobile_phone is only shown if a mobile phone number is entered in the profile.

If conditions always consist of an opening and a closing tag, each enclosed in a pair of curly brackets.

The pattern is as follows:

{% if <CONDITION> %} … {% endif %}

The following table provides an overview of possible comparison operators:

Equal

==

Not Equal

!=

Greater Than

>

Less Than

<

Greater Than or Equal to

>=

Less Than or Equal to

<=

The following is an example for a use case of if conditions:

If no value is entered for a property in the selected profile, you can use an if condition to ensure that the property is not displayed in the document either.

The following code excerpt shows an example of such an if condition, where the label for mobile_phone is not displayed if no mobile phone number is entered in the profile:

{% if User.Mobile_Phone.Value != null %}{{User.Mobile_Phone.Label}}: {{User.Mobile_Phone.Value}}{% endif %}

Else if conditions can be used within if conditions. If the if condition does not apply, the else if condition within the if block is evaluated.

There is no limitation on the number of else if conditions that can be included.

The pattern for an else if condition is as follows:

{% if <CONDITION> %} … {% elseif %} … {% endif %}

The following is an example for a use case of if conditions:

If the primary option is not available or not entered, an alternative is selected. If neither of the two values is available, the label is omitted.

The following code excerpt shows the else if condition for this example.

In this example, the else branch has been left empty. If a value is specified here, that value will be used.

{% if User.Mobile_Phone.Value != null %}{{User.Mobile_Phone.Label}}: {{User.Mobile_Phone.Value}}{% elseif 
User.Phone.Value != null %}{{User.Phone.Label}}: {{User.Phone.Value}}{% else %}{% endif %}

For lists that contain multiple entries of the same type (e. g., Managing Directors), for loops can be used. For loops consist of an opening and a closing tag enclosed in a pair of curly brackets.

Within the for loop, enter a variable that represents the values from your list. This variable is placed between two pairs of curly brackets.

The pattern for such a for loop is as follows:

{% for [VAR] in <ENTITY_VARIABLE> %}{{VAR}}{% endfor %}

Typically, for loops are used for the properties of the type Array, which usually display the following company information:

The following is an example for the use of such for loops:

A list of entries for Managing Directors is created. It is introduced by a label and is separated by line breaks.

The following code excerpt shows the configuration for this example:

{{Company.Managing_Directors.Label}}:[n/]{% for MD in Company.Managing_Directors.Value %}{{MD}}[n/]{% endfor %}

The outcome for a company whose managing directory are empower Admin and empower User would be the following:

If the entries in the list consist of multiple properties per value, first enter the variable followed by a period. Then specify the property and the type (label or value):

{% for [VAR] in <ENTITY VARIABLE> -%} {{VAR.PROPERTY.Label}}: {{VAR.PROPERTY.Value}}, {% endfor %}

The following is an example for the use of such for loops:

A list of entries for bank information is to be created, where each entry consists of three properties.

The following code excerpt shows the configuration for this example:

{% for BI in Company.Banking_Information.Value %}{{BI.Name.Value}}: {{BI.IBAN.Label}}: {{BI.IBAN.Value}}, {{BI.BIC.Label}}: {{BI.BIC.Value}}{% endfor %}

The outcome for a company's banking information could be the following:

List entries can be separated by line breaks, delimiters, commas, etc.

You can use formatting tags to change the formatting of each property.

For example, the name of a bank can be displayed in bold, while the rest of the entries remain unformatted.

Use an unless tag to apply an alternative formatting, for example, when the last list entry is being processed.

The pattern for this configuration is as follows:

{% for [VAR] in %}{{VAR}}{% unless %} ... {% endunless %}{% endfor %}

The following is an example for the use of such for loops:

A comma should be inserted after each list entry to separate the entries from one another.

A comma should not be inserted after the last entry in the list.

The following code excerpt shows the configuration for this example:

{{Company.Managing_Directors.Label}}: {% for MD in Company.Managing_Directors.Value -%}{{MD}}{% unless forloop.last %},{% endunless %}{% endfor %}

The outcome for a company whose managing directory are empower Admin and empower User would be the following:

Filters are special functions used to adjust and format data from templates.

Filters are implemented as follows:

{{ Variable_name | Filter_name: Argument }}

The following table provides an overview of filters that are usually used with empower^®:

Capitalize

The first character in a string is capitalized.

{{ [Property_Name] | Capitalize }}

Upcase

All characters in a string are written in uppercase.

{{ [Property_Name] | Upcase }}

Downcase

All characters in a string are written in lowercase.

{{ [Property_Name] | Downcase }}

Replace

Substrings are replaced by another substring.

{{ [Property_Name] | Replace: "cats", "dogs" }}

Size

Defines the number of characters in a string or array.

{{ [Property_Name] | Size }}

Strip

Whitespaces prior to or after a string are removed.

{{ [Property_Name] | Strip }}

In front of the pipe symbol, enter the property name and type (label or value) of the property you want to filter.

You can use multiple filters at once if you separate them with a pipe symbol.

The pattern for such a filter is as follows:

{{ Variable_name | Filter1 | Filter2 }}

The following are examples for the use of filters:

A filter is to be applied to ensure that the characters $% are used as a line break.

This filter can be used, for example, when a string contains multiple values that should be split across multiple lines.

The following code excerpt shows the configuration for this example:

{{Location.Address.Value.Street.Value | Replace: "\$\%", "[n/]"}}

The string for Street in the company management window would look as follows:

The outcome in the template would be the following:

You want to create a custom variable that adds the number of characters of two values and determines whether they fit into a single cell or need to be separated by line breaks.

The following code excerpt shows the configuration for this example:

{% assign charLength = Location.Website.Value.size | Plus: Location.Email.Value.size %}{{Location.Website.Value}}{% if charLength >46 %}[n/]{% else %}, 
{% endif %}{{Location.Email.Value}}

The outcome for a combination with less than or equal to 46 characters would be the following:

The outcome for a combination with more than 46 characters would be the following: