Templates lend form and reason to Web requests. Each template controls the content used within a notification event. Events supply templates with parameters used within placeholders and tags. In return, the template translates these parameters into readable messages. Templates includes a powerful syntax engine that provides further control on how messages appear.

1.   Template Name: This details a user-friendly name that helps differentiate message templates

2.   Template ID: An auto generated, non-editable, unique identifier for the current message template

3.   Content View: Contains different formats for viewing and editing the template:

o   Plaintext: A simple, non-formatted text editor. This provides users with the option to add more advanced HTML beyond the HTML toolbar

o   HTML: A simplified content editor that supplies common text formatting options

Important Note:

Users that wish to add custom HTML beyond what the HTML toolbar provides should use Plaintext. Then switch between content views to see how the changes will appear to users.

Additionally, users that wish to send pre-formatted text through parameters will need to wrap their placeholders with pre-formatted text elements. This can be done using the following syntax:

<pre>{{ <Placeholder>[ | <Filter>[ : arguments,...n]...n] }}</pre>