2019.2

On Workflow's side, information about the pre-rendered email messages become available to
the process 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-
365032648aed.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"}
],
"contentSet":8769}
Known issue
If the Render Email Content plugin receives JSON input and outputs Metadata, only 1 record
will be written to the Metadata. This issue is fixed in version 2020.1.
Properties
General Tab
l
Template: Click the Browse button to select a template from the resources (see "Connect
resources" on page40), 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54).
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54).
Only one section can be output. If no section is defined, an error will be thrown.
Page 662