2021.1

l
Data Source (see "Input" on page599):
l
Metadata:
l
Update Records from Metadata: If the process metadata has been modified
by any of the "Metadata tasks" on page559, 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 "JSON string examples" on page91) or a JSON Record Data
List (see the REST API Cookbook and "JSON Record Data List example" on
page93).
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
access to the values through the record's data fields. (See the Designer help:
Adding Variable Data.)
Warning
The JSON format is not validated by the plugin; it is passed as is to the
server.
l
Runtime Parameters: The runtime parameters defined in the selected template are
displayed and their values can be set here. (See Runtime parameters in the Online Help
of OL Connect.)
Right-click the field to open the contextual menu that allows to select variables, data and
lookup functions (see "Data selections" on page53).
If the template name is dynamic, you must enter the name (or select a variable that
contains the name) and set the value of all runtime parameters that may occur in the
template.
If a runtime parameter is defined in a template, but not set in the task properties, an error
will be raised. Note that it is not possible to change a parameter's type here; that can only
be set in the template itself.
At runtime, Workflow passes the parameter values as strings, and the type defined in the
template will be used to try and parse the input parameter value. In order to make this
Page 601