2019.2

Note
The plugin takes the entire Metadata file as its input, even when it is placed after a "Metadata
Sequencer" on page597 task.
JSON
The Render Email Content task supports two types of JSON:
l A JSON object or an array of JSON objects representing records. If a value in a record
object is a string, it is considered to be a field value. If a value in a record object is a
JSON object, it is considered to be a nested table with detail records. For examples, see
"JSON string samples" on page638.
l A JSON Record Data List (see the REST API Cookbook and "JSON Record Data List
example" on page94). When the "Execute Data Mapping" on page649 or "Retrieve
Items" on page664 task is set to output Records in JSON, it outputs this kind of JSON
data.
If the input is JSON, the task performs a REST call to the
/rest/serverengine/workflow/contentcreation/email/{templateId} endpoint on the Connect Server.
For more information see the REST API Cookbook.
Processing
This task loops through each record in a Record Set or through each JSON object in an array.
For each record or JSON object, the task generates an HTML email using that record's or
object's data.
Note
Content creation may be aborted by a script in a Connect template that raises a fatal error. This
triggers the On Error tab of the Content Creation task. See Designer Script API.
Output
The output of this task is twofold.
On the OL Connect Server's side, pre-rendered email messages are saved in the OL Connect
File Store along with their attachments (and, optionally, also in EML format).
Page 661