8.7

improve data mapping performance significantly, as well as the time required for the
cleanup process. However, since the data is not written to the database, there is no
way to do post-processing on the extracted data. Any post-processors defined in the
data mapping configuration will be disabled.
This option is unchecked by default.
Note
When the data mapping configuration provides multiple records, the preview
is created based on the first record.
l
JSON string sets the data source to a JSON string (see "Using JSON" on the facing
page). A text area is shown allowing the user to enter the JSON string.
The JSON string may contain local and global variables, Job Infos and calls to the lookup
function (see "JSON string samples" on the facing page).
A single variable can be used, assuming that the respective variable contains a JSON
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.
Page 544