2018.2

Table Of Contents
l
"None": Select to execute default, basic data mapping on the input PDV/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 page48).
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
Output IDs in Metadata: 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
Output records in 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
Output results in XML data file: Select to output an XML structure containing the
full Record Set including all details table. When this option is used, the Record Set
is not saved on the OL Connect Server, the data is simply returned and processing
stops on the server side. This option cannot be used with other OL Connect tasks.
l
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
validationresult entry on the Group[0] level of the Metadata. (For the structure
of the JSON object, see the REST API Cookbook: JSON Data Mapping Validation
Result.) The JSON's result and recordcount fields are also stored at the
Group[0] level. Each Document node contains the following fields:
l index: The position of the record in the job. This value is 1-based. Note that
this is not a record ID, since the record is never stored in the database.
Page 524