2019.2

Note
If the input data is JSON, you don't need a data mapping configuration: JSON data can
be used in a template as is. See: "Adding JSON data from a JSON file" on page798.
However, if you want the data to be saved in the OL Connect database, put the
XML/JSON Conversion plugin before the Send to Folder task to convert the JSON to
XML, and create an XML data mapping configuration to extract the data.
The email
Often this type of email has a Call to Action button which redirects the user to the website of
the vendor, where the user could log on to the site and follow an online payment process, for
instance.
To get an example (or to start over) you could use one of the template wizards that start an
'action email'; see "Email Template Wizards" on page522.
You could add text, images and other elements to the email (see "Content elements" on
page628) and change the layout (see "Styling and formatting" on page741). Keep in mind
though that there are special design standards for HTML email (see "Designing an Email
template" on page517).
In order to further personalize the email, open your data mapping configuration (or JSON data,
if the input data will be in that format; see "Adding JSON data from a JSON file" on page798)
and use the data fields to personalize the email. (See: "Personalizing content" on page786.)
Tip
The Designer can have one data mapping configuration and one template open at the
same time. Use the tabs at the top of the workspace to switch between the two. Click the
synchronize button on the Data Model pane to make sure that the Data Models are the
same in both.
Once the template is ready, send it to Workflow (see "Sending files to Workflow" on page457).
Finally, in Workflow, adjust the process: double-click the Create Email Content task to open it,
and select the new template. This is only necessary when the file name has changed.
Page 179