...
| Info | ||
|---|---|---|
| ||
The feature is currently available for a subset of email templates (10) and is in the beta stage. We plan to expand the capability of using a new email designer editor across all transactional email templates. Please see the details below. |
...
You will find this new feature upon the creation of the new email template for transactional email under Document types. Once you create a new model for supported document type you will be able to create a new "document model" by selecting the "Designer editor". See below.
What document types are supported?
We currently support only the subset of the document types, the remaining ones will be delivered in the following releases.
Each document type has its own supported merge tags that allow operators to design personalized, dynamic email templates (see the example below).
What are merge tags?
Merge tags are personalized variable pieces of information that is being applied to the email template dynamically respecting the data associated with (for example) an event name or individual receiving this email (e.g.: "Dear Mr Martin" - where "Mr" is "salutation" merge tag and "Martin" is "Contact first name" merge tag. Find more examples in the expansion section below per document type.
Supported document types with merge tags available
Each document type (default templates) supports 6 languages (English, French, German, Italian, Spanish and Catalan) and has its own merge tags, as shown below:
...
| UI Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
How to set up a design editor for transactional email?
| UI Steps | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
The instructions below outline how to set up a design editor for transactional email. For example: Accompanying letter.
|
Multi-language support per document model
Multi-language support for your templates is available. Simply define multiple document models per each language you need. We provided some predefined templates per language for most used templates as part of the default setting.
How to migrate a template from preproduction to production environments?
You will notice that every template newly created template will be generating a *.json file that is available for download. Currently (in Beta status of the release) the uploading is not yet enabled. In future releases, we'll enable the possibility to upload those templates so that you can test them first in testing environments (such as preproduction) before uploading a final version to your production environment.
Other details
Specialities
While this new functionality provides a significant improvement to how transactional emails are managed today, you will notice that some of the documentation templates are populated with some technical code conditions. This will be improved over time but for now ...
| Info | ||
|---|---|---|
| ||
We recommend NOT removing any of those code conditions and purely focusing on adapting the text associated with actual messaging. Some templates provide templates that cover multiple use cases and the text from such templates will be applied only when specific criteria of action are met before the template is generated and shipped to the end user. Such a case is the template for Orders that you can also see below. Such a template will trigger only a specific part of the messaging applied on the template respecting specific cases. An example can be when the user's order was made using the product "options" or "reservations". Removing the mentioned code from the view will break the template and require you to configure the template from scratch.
|
Formats available
While this feature was primarily built for transactional emails, it might be useful to design other formats of documents. We also support the creation of document models in PDF format.
...