2021.1

the list below.
l
Preset Names: Select the appropriate Job Preset file. Listed are the Job Presets
that are present in the Connect Resources (see "Connect resources" on page40).
l
Runtime Parameters: The Runtime Parameters defined in the selected Job Creation
Preset are displayed and their values can be edited here. Right-click the field to open the
contextual menu that allows to select variables, data and lookup functions (see "Data
selections" on page54).
Note that it is not possible to change a parameter's type here; that can only be set in the
Job Creation Preset itself.
At runtime, Workflow passes the parameter values as strings, and the type defined in the
Job Creation Preset will be used to try and parse the input parameter value. In order to
make this work:
o
Boolean values need to be entered as either “true” or “false”. (When the comparison
actually occurs, it will be a full Boolean comparison. Thus it can compare this
runtime parameter with Boolean data values that are stored as 0/1 in data fields.)
o
Numeric string values need to be parseable as a number (either a whole integer or
decimal value).
o
Dates should be in an ISO8601 compatible format (e.g. 2019-10-15) or use the
current Windows Locale date settings options.The latter is not recommended as it
requires all computers in the cluster have the same locale data format.
The order of the parameters doesn't affect the way they are handled at runtime.
Note
Backslashes (\) and double quotes (") in a JSON string must be escaped with a
backslash (\\, \") if the JSON string is passed via a global, local, or Job Info variable.
If the JSON is entered directly in the runtime parameter field, the plugin adds the
necessary backslashes.
Output Creation Tab
The Output Creation step generates the output for the current job, using the selected Output
Creation Preset. Note that the Job Creation task normally necessary when using the individual
tasks is implicitly executed before output creation.
Page 596