2022.1

lookup functions (see "Data selections" on page54).
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
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.
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.
Note
It is not currently possible to specify Runtime parameters on the Content Creation tab if,
on the Datamapper tab, the source has been set to "Data mapping configuration". There
is, however, an easy workaround: insert an Execute Data Mapping task immediately
before the Create Preview PDF task, configure it to output either Metadata or JSON and
adjust the settings on the Datamapper tab of the Create Preview PDF task accordingly.
The Content Creation tab then allows to specify Runtime parameters for the selected
Page 569