2019.1

This task also accepts a PDF/VT file as input (see "Create PDF/VT" on page596), allowing the
task to be used without a Connect Template.
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596).
Metadata
The "Execute Data Mapping" on page612 task and the "Retrieve Items" on page624 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601.
l A JSON Record Data List (see the REST API Cookbook and "JSON Record Data List
example" on page87). When the "Retrieve Items" on page624 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591 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612 task does. Job
Creation Presets need such a record set to group, sort and filter items.
Page 604