2022.2

l
%o: Select to use a dynamic template name. Click on %o to change the expression that determ-
ines the name of the template to use.
l
A template name: Select the appropriate template name from the list. Adding templates to this
list is done from the Send to Workflow option in the Designer module.
A preview will be displayed of the output generated by the Print context of the selected template.
(Not available for a dynamic template name).
If on the Datamapper tab, the source has been set to Metadata or JSON, the following option is also
available.
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49).
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 tem-
plate 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 actu-
ally occurs, it will be a full Boolean comparison. Thus it can compare this runtime para-
meter 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 Win-
dows Locale date settings options. The latter is not recommended as it requires all com-
puters in the cluster have the same locale data format.
Note: Backslashes (\) and double quotes (") in a JSON string must be escaped with a back-
slash (\\, \") 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 neces-
sary 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,
Page 514