Content within templates is defined as HTML, and contains tokens with placeholders for dynamic content sourced from record data. There are various types of tokens each of which is surrounded by square brackets [] and will be replaced with data from source records when the template is applied into an email or document

Tokens available for use in dynamic content are listed below. Click into each for more detail and examples

• Field – will be replaced with the value of a column from the target record, or a record linked through one or more lookup fields
• If – content between the start and end will only be included if an expression within the token resolves to true based on fields in the target record, or records linked through one or more lookup fields
• For Fetch – content between the start and end will be repeated for each record returned by a Fetch XML query. This is intended for listing content from records related by a one to many relationship
• Include – these will be replaced with content in a different content template. Generally it would be used to insert a reusable content snippet template into a document
• First – will be replaced by a column from the first record returned of a given type. This would be used for example to insert the environment URL from a settings record into part of a hyperlink, or to insert an organisations address into a document from the settings rather than having to repeat it across multiple content templates
• View – will be replaced by an html table representing to output of a system view. This is generally used to notify users where records returned by a system view need to be actioned