2018.1

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 (see "Metadata in OL Connect jobs" on page69)
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.
Properties
General Tab
l
Template File:
l
"None" File name: Select to accept a PDF/VT file as an input and automatically
create content items based on the PDF/VT.
l
"%o": Select to use a dynamic template name. Click on %o to change the
expression that determines the name of the template to use.
l
Template Names: Select the appropriate template. Adding a template to the
resources is done through the Send to Workflow option in the Designer Module.
l
Data Source (see "Input" on the previous page):
l
Metadata:
l
Update Records from Metadata: If the process metadata has been modified
by any of the "Metadata Tasks" on page418, check this option to update the
records in the Connect database with the metadata and use the updated
records. Otherwise, only the ID of the current job is sent, and the unchanged
records are used.
l
JSON:
l
JSON String: A JSON object or an array of JSON objects representing
records (see "Create Print Content" on page469) or a JSON Record Data List
(see the REST API Cookbook).
This option requires that keys in the JSON data 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
Page 471