2019.1

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535 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555 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.)
Note
Content creation may be aborted by a script in a Connect template that raises a fatal error. This
triggers the On Error tab of the Content Creation task. See Designer Script API.
Output
The output of this task is modified Metadata (see "Metadata in OL Connect jobs" on page71)
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 OL Connect Database.
Page 548