2020.1

"eml":"c5f97db0-45ca-4f1d-be4d-473d000c92bd.eml",
"body":"07decd87-d03c-4969-bc2a-7527cc594878.html",
"text":"7a4e5217-0103-487f-a4f8-77d37d0c1087.txt"}
],
"contentSet":8769}
Properties
General Tab
l
Template: Click the Browse button to select a template from the resources (see "Connect
resources" on page39), or enter a dynamic template name. Right-click the field to open
the contextual menu that allows to select variables, data and lookup functions (see "Data
selections" on page53).
l
Section: Enter the section name that will generate output. Right-click the field to open the
contextual menu that allows to select variables, data and lookup functions (see "Data
selections" on page53).
Only one section can be output. If no section is defined, an error will be thrown.
l
Data Source (see "Input" on page633):
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622 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91) or a JSON Record Data List (see the REST
API Cookbook and "JSON Record Data List example" on page92).
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 the previous page): 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
Page 635