Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

You can add, edit or test an email template using the template toolbar (), or navigate to the /comms/templates URL to access all the email templates.

You can export and import email template on this page as well.

The template editor

The template editor is opened when you select 'add' or 'edit' on an existing template. The following information is required to complete a template:

  • The name of the template - must be unique amongst all the templates for the same application;
  • The name of the application to which the template belongs - the application cannot be changed for saved templates;
  • The type of templates:
    • Default - this type of template is editable using the HTML editor. It supports simple data binding using {xxx} syntax;
    • Razor - select this template type to create templates that require programming logic to generate output. This type of templates must conform to the Microsft Razor page syntax. The reference of the razor syntax can be found here: https://docs.microsoft.com/en-us/aspnet/core/mvc/views/razor?view=aspnetcore-3.0

Discover the data available for binding

A template can accept data input and use data binding to produce dynamic outputs. However, the structure and fields of the input data depend on the application of the template. You can use the following steps to discover the full data set available for the applicable operation:

  1. Create a “test” template of the "Default" template type;
  2. Add {*} to the template body and save the template;
  3. Navigate to the application's template configuration page, e.g. OneList notification channels, RoleManager email settings, and select the newly created “test” template for the operation;
  4. Click the Test Mail button on the template toolbar;
  5. The full data set is displayed as JSON.
  6. Use this JSON as reference to create data binding in your template. 



  • No labels