Home 
Support
Documentation
Report Templates
Report Templates Syntax
The Syntax of the Collection Section
The Collection Section is the section that will be merged with all the elements of the Collection.
The syntax :
{{Collection CollectionName}}
{{ CollectionName["Path"]}} {{ CollectionName ["Path"]}}
{{EndCollection}}
The Collection Section, always must start with the {{Collection CollectionName}} and ends with the {{EndCollection}}, the CollectionName specifying the Collection to which this section will be linked. A Collection Section can contain rich text and Merge Fields.
If the Collection Section must display a fixed count of item, this can be forced by the following syntax: {{Collection CollectionName,ForceItemCount}} , where ForceItemCount is the needed count of elements in the section.
Examples:
{{Collection Contacts}}
{{Contacts["DisplayName"]}}{{Contacts["EmailAddress"]}} {{EndCollection}}
{{Collection Tasks}}
{{Tasks["Subject"]}}
- {{Tasks["ContentID.SearchableText"]}}{{EndCollection}}
The Syntax of the SubCollection Section
The SubCollection Section is a special Collection Section inside a Collection Section, that is additionally filtered with values from the main Collection.
The syntax :
{{Collection CollectionName}}
{{ CollectionName["Path"]}} {{ CollectionName ["Path"]}}
...
{{SubCollection SubCollectionName,SubCollectionName ["Path1"] = CollectionName ["Path2"]}}
{{EndSubCollection}}
...
{{EndCollection}}
The SubCollection Section, always must start with the {{SubCollection SubCollectionName}} and ends with the {{EndSubCollection}}, the SubCollectionName specifying the Collection to which this section will be linked. A SubCollection Section can contain rich text and Merge Fields.
If the SubCollection Section must display a fixed count of item, this can be forced by the following syntax: {{SubCollection SubCollectionName,ForceItemCount,... where ForceItemCount is the needed count of elements in the section.
Example:
{{Collection Users}}
{{Users ["Name"]}}
{{SubCollection Tasks,Users["ID"] = Tasks["OwnerID"]}}
-{{Tasks["Subject"]}} {{EndSubCollection}}
{{EndCollection}}
The Syntax of the GroupBy Section
A GroupBy Section is the section that groups together elements of the Collection that have the same value for the specified grouping path.
The syntax :
{{Collection CollectionName}}
{{ CollectionName["Path"]}} {{ CollectionName["Path"]}}
...
{{GroupBy CollectionName["GroupByPath"]}} ...
{{EndGroupBy}}
...
{{EndCollection}}
The GroupBy Section, always must start with the {{GroupBy CollectionName["GroupByPath"]}} text and ends with the {{EndGroupBy}}, the GroupByPath specifying the field on which the Collection items will be grouped. A GroupBy Section can contain rich text and merge fields.
Example:
{{Collection Tasks}}{{GroupBy Tasks["OwnerID"]}}
{{Tasks["OwnerID.Name"]}}{{EndGroupBy}}
- {{Tasks["Subject"]}}{{EndCollection}}
The Syntax of Merge Fields
The Merge Field if the part of the Merge Section that is merged with values corresponding to the Merge Field's path.
The syntax:
... {{CollectionName["Path"]}} ...
String Formating
Merge Fields of type string, can be specially formated, by specifying their length and alignement.
The syntax:
... {{CollectionName["Path,alignment"]}} ...
The optional alignment component is a signed integer indicating the preferred formatted field width. If the value of alignment is less than the length of the formatted string, alignment is ignored and the length of the formatted string is used as the field width. The formatted data in the field is right-aligned if alignment is positive, and left-aligned if alignment is negative.
Date and Time Formating
Merge Fields of type Date or Time, can be also specially formated.
The syntax:
... {{CollectionName["Path,format"]}}...
where format can have the following values:
For greater control over the formating of Date and Time, custom formats can be used. Custom formats are the combination of one or more custom format specifiers.
Custom format specifiers:
Image Formating
Merge Fields of type blob, that contain images, can be merged as images into the report.
The syntax:
... {{CollectionName["Path,Image"]}}... or,
... {{CollectionName["Path,Image( width)"]}}... or,
... {{CollectionName["Path,Image( width, height )"]}}...
Text Formating
Merge Fields of type blob, that contain plain text, can be merged as plain text into the report.
The syntax:
... {{CollectionName["Path,Text"]}}...
Rtf Formating
Merge Fields of type blob, that contain Rtf text, can be merged as rich text into the report.
The syntax:
... {{CollectionName["Path,Rtf"]}}...
Top of Page
Vertikal Systems |
Privacy Policy |
Terms of Use
Copyright © 2010 Vertikal Systems - EHR Medical Software, Electronic Medical Records and Medical Scheduling Sofware
