2018.1

Input
This task can receive either Metadata containing information regarding a valid Record Set, or
JSON data, or a PDF/VT File (see "Create PDF/VT" on page463).
Metadata
The "Execute Data Mapping" on page476 task and the "Retrieve Items" on page486 task
output Metadata containing information regarding a Record Set.
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467.
l A JSON Record Data List (see the REST API Cookbook). When the "Retrieve Items" on
page486 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459 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476 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.
Page 470