2022.2

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 con-
sidered to be a nested table with detail records. For examples, see "JSON string examples" on
page78.
l
A JSON Record Data List (see the REST API Cookbook and "JSON Record Data List example"
on page79). When the "Execute Data Mapping" on page524 or "Retrieve Items" on page538
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/server-
engine/workflow/contentcreation/email/{templateId} endpoint on the Connect Server. For more inform-
ation 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, an HTML Email is generated using that record's or object's data. The output
generated is then sent via an SMTP server with the email address set by the template.
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. For example, when the
recipient’s email address in a record is invalid, that record produces a non-fatal error; subsequent
records will still be processed.
Output
Within the Workflow process, the output to this task is only modified metadata indicating that the task is
complete. It is the Server component that outputs the emails themselves and sends them to each recip-
ient.
Note: If sending email is not included in the license, the emails will be sent to the sender instead
of to the intended recipients.
Page 503