2022.2

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 PReS 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 page79). 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426 task.
l
Simplified JSON: Select to output the full Record Set including all tables as an array of
JSON objects. Unlike the output of the "JSON" option, simplified JSON does not contain
information about the data type of fields.
l
None (validate only): Select to run the operation in Validation mode and output the val-
idation 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 val-
idationresult 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 Docu-
ment 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.
l
error: The error message, or an empty string when no errors have been reported
for this record.
Document nodes with an error are selected, while those without an error are unselected, to
make looping through all errors easy.
By default, if the validation cannot be performed the task fails and logs an error, but if the
Generate error when validation cannot be performed checkbox is unticked, the task
will log a warning and it will generate metadata with a single group containing a single doc-
ument, with the error message "DataMapper could not process the input file".
Page 524