Page Comparison

Data templates transforms Data templates transform the data model into text or HTML content. Templates are used in many areas in emakin like form controls or mail templates etc.

Templates basically consist on of xpath queries within {{ and }} qualifiers.

Assume you have a field named as "username" in the data model. Basic temple template example is:

Hello {{ username }}!

...

Because all xml values are string by default, no formatting is performed while generating the output. If you need to perform formatting for number or date values, you have to convert the data type or use a format function.

Culture Support

Data templates are culture sensitive and all formatting rules are derived from culture being used. Culture information is automatically derived from user preferences or you can explicitly specify it. If no culture is specified, invariant culture is used.

...

All text or string types are exactly transformed without any format formatting being performed.

Number formatting

Like Functions like "sumSum" or "countCount" functions already returns return number value values, therefore there is no need to convert but if need use data model field you have to wrap field with for number conversions, but in case it is necessary, number() function should be used. Ex: number(MyNumberField) 

All number values are by default formatted with decimal rules.

Examples:

Date formatting

Template system does automatically detects the xml date types in formatted with "YYYY-MM-DD-THH:MM:SSTZ". Emakin always use uses this format in data model for date values.

...

Examples:

Assume data model has an a MyDate field with 2014-01-31T09:00:00+02:00 value.

2014-01-31T09:00:00+02:00

Scripting example

var myNode = $Xml.Parse("<Customer><Name>John</Name><BirthDate>2014-01-31T09:00:00+02:00</BirthDate></Customer");
var result = myNode.Format('<p>Birth date : {{Customer/BirthDate}}</p>');

// result : <p>Birth date : 01/31/2014 09:00:00 +02:00</p>

Scripting example

A way to remove time from date node:

$Xml.SetValue('Test/testdate', new DateTimeOffset());  // testdate will be saved to an XML as "2015-11-12T15:27:16.2568549+02:00"
$Xml.SetValue('Test/testdate2', $Xml.Format("{{ format(Test/testdate,'yyyy-MM-dd') }}"));  // testdate2 will be saved to an XML as "2015-12-11"

// result : 2015-12-11

Format Function Options

Conditional Formatting

If conditional rendering is needed, the format below can be used;:

if XPathConditon then Template
if XPathConditon then Template else Template

...

If you need to apply template for multiples multiple nodes in a data model, you can use repeating template expression like following syntax:

ItemXPath => Template

This format applies the same template for every matched element by ItemXPath.

var result = $Xml.Format('SAMPLE REPORT\{{ SAMPLE REPORT
   <h1>{{Customer/Name}}</h1>\
   <table>\
   {{ Rows/Row =>> 
     <tr><td>{{Date}}</td><td>{{Description}}</td></tr>  }}\
   </table>', {
  MyVariable : 'Long text'
});

result

 }}

Generates the following output:

SAMPLE REPORT
<h1>John</h1>
<p>Long<table>
text</p> <table> <tr><td>2010-01-01</td><td>description</td></tr>
  <tr><td>2015-01-01</td><td>other description</td></tr>
</table>

...

While generating HTML content some tags ( like table tag ) may become corrupted if {{ x => y}} template is used. As an alternative method, format function supports the x-repeat attribute to perform the repeating content. 

{{ SAMPLE REPORT
   <table>
     <tr x-repeat="Rows/Row">\
       <td>{{Date}}</td><td>{{Description}}</td>\
     </tr>\
   </table>', {
  MyVariable : 'Long text'
});
 }}

This attribute can be used with any element. For example, it can also be used with "li" tag also.

var{{ result<ul>
= $Xml.Format('\ <ul>\   <li x-repeat="Rows/Row">\
       <span>{{Date}}</span>\
     </li>\
  </ul>'); }}

Recursive Repeating Template

If recursive repeating templates are being needed, format below can be used;:

ItemXPath =>> Template

For each item at specified in ItemXPath, sub template is generated, and also the same template is repeated again for the Template content recursively.

{{ <h1>SAMPLE REPORT</h1>\
<p>{{DocumentTitle}}</p>\
   {{ Sections/Section =>>>> 
      <h2>{{Name}}</h2><p>h2>
      <p>{{Body}}</p>  }}');
}}

result:

<h1>SAMPLE REPORT</h1>
<h2>My Section</h2>
<p>Section content</p>
<h2>Sub Section</h2>
<p>Child section content</p>

Template Variables

All of the custom defined process variables can be used in templates. Additionally, some of the system properties are automatically imported to the template engine. Because of the environment limits, client and server side variables use different variable contexts.

Client Template Variables

In scripts like form script, for the validation rules running on the client side environment, following variables are defined:

Server Template Variables

In process scripts like pre work, post work and other scripts that running on the server side environment, following variables are defined:

Activity Notification Template

Activity notifications, like assigning a work item to a user or reminder notifications, use the same template context. Additionally to the server variables, the following variables can also be used:

User Registration Template

Additionally to the server variables, user registration invitation defines the following variables: