2019.2

l
Data Source (see "Input" on page660):
l
Metadata: The Metadata must contain information regarding a valid Record Set, or
JSON data. This can be the output of the "Execute Data Mapping" on page649 task
or "Retrieve Items" on the next page task.
l
JSON String: a JSON object or an array of JSON objects representing records (see
"JSON string examples" on page93) or a JSON Record Data List (see the REST
API Cookbook and "JSON Record Data List example" on page94).
This option requires that keys in the JSON data have matching field names in the
data model of the template. When they have, the JSON values are passed to the
template; the personalization scripts of the template will have access to the values
through the record's data fields. (See the Designer help: Adding Variable Data.)
Warning
The JSON format is not validated by the plugin; it is passed as is to the server.
l
Output Method (see "Output" on page661): Select how to output information about the
emails that were created, including the email addresses (to, from, etc.), subject, and the
names of the folder, HTML file, attachments, (optional) plain text email file (see Email
output settings in the Email context and sections) and EML file (see below).
l
Metadata: Write the information to the current Metadata.
l
JSON Data in Job Data File: Return the information in a JSON structure that
replaces the current Job File. This allows you to manipulate the output in a "Run
Script" on page506 task before sending it to an Email Service Provider (ESP).
l
Additional Output:
l
Render messages in EML format: Creates an EML file containing the HTML
email, its attachments and (optionally) the text version of the email, and saves it in
the File Store. EML files can be used for archiving. You could use the "Download
EML Messages" on page647 plugin to download them from the File Store.
Alternatively you could use the "File Store - Download File" on page654 task; in
that case you will need the folder ID and EML file name found in the output of the
"Render Email Content" on page660 plugin.
Page 663