2020.2

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.
l
Output Preset: Select the appropriate Output Creation Preset to use:
l
"None": Select to prevent the execution of Output Creation.
l
"%o": Select to use a dynamic Output Preset name. Click on %o to change the
expression that determines the name of the Preset to use.
l
Preset Name: Select the appropriate Output Preset to create output with. Listed are
the Output Presets that are present in the Connect Resources (see "Connect
resources" on page38).
l
Output Management group:
l
As defined by Output Preset: Select to send the output of the job to the location
set in the Print Preset (file, printer, etc).
Page 588