2019.1

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.
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.
Tip
To determine if there were any errors in a job and handle it accordingly, you
can use a Condition that checks if GetMeta(SelectedCount[0], 11,
Job.Group[0]) is greater than 0, immediately after the task (see
"Conditions" on page130).
OL Connect Proxy Tab
This tab is common to all OL Connect tasks and defines where to process the jobs sent through
these tasks. When these fields are empty, they use the defaults set in the OL Connect User
Options page of the preferences.
Note
Defaults are not used unless the configuration is sent to the Workflow service.
l
OL Connect Proxy Address: Enter the machine name or IP Address where the OL
Connect Server resides.
l
Port: Enter the port to use to communicate with the OL Connect Server. Default: 9340
l
User name: Enter the user name expected by the OL Connect Server.
Page 614