2020.1

Table Of Contents
Properties
General Tab
l
Data Mapping Configuration: Executes data mapping on the appropriate source. Select
the appropriate data mapping configuration in the list:
l
"None": Select to execute default, basic data mapping on the input PDF/VT file.
l
"%o": Select to use a dynamic data mapping configuration name. Click on %o to
change the expression that determines the name of the data mapping configuration
to use. Right-click it to open the contextual menu that allows to select variables,
data and lookup functions (see "Data selections" on page52).
l
Configuration Names: Select the appropriate data mapping configuration. Adding
configurations is done through the Send to Workflow option in the DataMapper
Module.
Click the Open data model of selected configuration button to view the data
model attached to the configuration in the Data Mapper module, to verify that the
correct one is used. Only works for configurations listed (will not work for "None" or
"Dynamic" options).
l
Output Type group:
l
Metadata - IDs only: Select to only output the Record and Job IDs in the Metadata.
This does not permit sorting and filtering, but it enhances performance since only
minimal data is exchanged between the OL Connect Server and PlanetPress
Workflow.
l
Metadata: Select to output the full Record table (no Details table) as Metadata in the
task. It is then possible to sort and filter the Metadata using the regular Metadata
tools, as long as the Update Records from Metadata option is used in further tasks
to use the modified Metadata.
l
XML: Select to output an XML structure containing the full Record Set including all
detail tables. This option cannot be used with other OL Connect tasks.
l
JSON: Select to output a JSON Record Data List (see the REST API Cookbook and
"JSON Record Data List example" on page91). The file contains the full Record Set
including all detail tables and boundary information, which can then be processed
in a "Run Script" on page477 task.
l
None (validate only): Select to run the operation in Validation mode and output the
validation results in the Metadata. No data is extracted or stored in the Connect
Database.
The task performs a validation REST call and stores the returned JSON object in a
Page 618