2022.2

Note: Make sure that other components in the Workflow configuration working on the job data
handle UTF-8 encoded files correctly.
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.
When an email address is invalid, no email content will be created. Instead, an error is reported for the
record with an invalid email address.
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.
Note: The number of log messages for any non-fatal errors is limited to 100. Non-fatal errors are
errors related to one record that will not stop the processing of all records.
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).
On Workflow's side, information about the pre-rendered email messages becomes available to the pro-
cess via the current Metadata or via a JSON data structure that replaces the active Job File.
Here is an example of the JSON structure. In this case there's only one email message in the Content
Set.
{"messages":
[
{"attachments":[
{"name":"att0307c655-e14e-4400-8f90-365032648ae-
d.png","disposition":"inline"},
{"name":"myPDF.pdf","disposition":"attachment"},
],
"subject":"Take action now",
"to":"[e-mail]",
"from":"[e-mail]",
"folder":8768,
"eml":"c5f97db0-45ca-4f1d-be4d-473d000c92bd.eml",
"body":"07decd87-d03c-4969-bc2a-7527cc594878.html",
"text":"7a4e5217-0103-487f-a4f8-77d37d0c1087.txt"}
Page 536