2022.2

Table Of Contents
Render Email Content
The Render Email Content task pre-renders emails from a template's Email Context and stores them
in the File Store, along with their attachments.
Note: The Render Email Content task works only if PlanetPress Workflow is licensed for send-
ing emails. It is not available for users with Demo, Test or Reseller licenses.
For the Render Email Content task in PlanetPress Workflow 2020.1 and higher to function cor-
rectly with the SendGrid and Mailjet plugins, the version 2020.1 or higher of those plugins is
required. They are available for download on the (help.objectiflune.com).
Input
This task must receive either Metadata containing information regarding a valid Record Set, or JSON
data.
Metadata
The "Execute Data Mapping" on page524 task and the "Retrieve Items" on page538 task output
Metadata containing information regarding a Record Set.
Note: The plugin takes the entire Metadata file as its input, even when it is placed after a
"Metadata Sequencer" on page478 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 con-
sidered to be a nested table with detail records. For examples, see "JSON string examples" on
page78.
l
A JSON Record Data List (see the REST API Cookbook and "JSON Record Data List example"
on page79). When the "Execute Data Mapping" on page524 or "Retrieve Items" on page538
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.
The Render Email Content task expects UTF-8 encoded JSON job data files.
Page 535