8.8

JSON
The Create Print 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 considered to be a nested table with detail records. For examples, see
"JSON string samples" on page579.
l A JSON Record Data List (see the REST API Cookbook). When the "Retrieve Items" on
page609 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/serverengine/workflow/contentcreation/{templateId} endpoint on the Connect
Server. For more information see the REST API Cookbook.
Note
When JSON data is used as input, the "Create Job" on page567 plugin (the next task in a print
process) cannot use a Job Creation Preset. The Create Print Content task doesn't create a record
set based on the provided data, like the "Execute Data Mapping" on page591 task does. Job
Creation Presets need such a record set to group, sort and filter items.
Processing
In the case of a record set or a JSON object/array and template, this task loops through each
record (or object) in the set (or array). For each record or JSON object, one or more pages are
generated using the record's data and these pages are saved as a content item in the
database.
In the case of a PDF/VTfile, content items are created based on the structure of the
PDF/VTmetadata and content items are stored using the data for each of those metadata
records.
By default, the entire Print Context is used to create print content items. Individual Print sections
can be selected dynamically via a Control Script. (For more information see the Designer Help.)
Output
The output of this task is modified metadata with information about the job processing and each
created content item. No content item is actually output from the task, they are only saved in the
Page 583