2018.1

string.
In case the JSON string is not a valid JSON object, the plugin will error out with an explicit
message.
Note
This option requires that keys in the JSON string have matching field names in the
data model of the template. When they have, the JSON values are passed to the
template and the personalization scripts of the template will have access to the
values through the record's data fields. (See the Designer help: Adding Variable
Data).
l
Metadata uses existing metadata, generally the output of a Create Record Set or a
Retrieve Items task set to retrieve a record.
Update fields with metadata: when this option is selected, the plugin will update fields in
the Connect database based on the metadata content. This is only useful if the Workflow
process has modified the metadata and the corresponding fields should be updated in the
database before creating the preview PDF.
Note
The Metadata option requires that entries in the metadata have matching field
names in the data model of the template. When they have, the values are passed to
the template and the personalization scripts of the template will have access to the
values through the record's data fields. (See the Designer help: Adding Variable
Data).
Using JSON
In web environments, it is common to send and retrieve data from a server using an AJAX
request (typically invoked from within a JavaScript). Then the data is often exchanged in JSON
format. JSON is short for JavaScript Object Notation. It is a way to store information in a
structured and easy to read format. It is often referred to as XML without nodes and meant for
exchanging data.
Refer to the following online resources for more information on JSON:
Page 469