2022.2

Table Of Contents
l
Runtime Parameters: Runtime parameters pass information from the Workflow process to the
data mapping configuration (see Properties and runtime parameters in the Online Help of OL
Connect).
Initially, the value of runtime parameters that are defined in the selected data mapping con-
figuration is set to that of a local variable or else a global variable if there exists a variable with
the same name. If no such variable exists, the value will be an empty string.
To change the source of the value for any runtime parameter, right-click to open the contextual
menu that allows to select variables, data and lookup functions (see "Data selections" on
page49).
If the data mapping configuration name is dynamic, you must enter the name (or select a variable
that contains the name) and set the value of all the runtime parameters that may occur in the data
mapping configuration.
If a runtime parameter is defined in a data mapper configuration, but not set in the task prop-
erties, an error will be raised.
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.
l
Bypass content creation: Check this option to make the task create a Print Content Set as well
a Record Set, so that in a print process, content creation - normally performed by the Create Print
Content task - can be skipped if there is no need to merge the extracted data with a template.
l
Duplex: Whether the page sheet is duplex.
l
Tumble: Whether to duplex pages as in a calendar. For this to work, the duplex option
must be checked as well.
Note: The Bypass content creation option only works if the input is paginated.
Set the Output type to Metadata if the Content Creation task is omitted and the output is to
be used by the Job Creation task later on in the print process.
OL Connect Proxy Tab
This tab is common to all OL Connect tasks and defines where to process the jobs sent through these
tasks. When these fields are empty, they use the defaults set in the "OL Connect preferences" on
page654.
Note: Defaults are not used unless the configuration is sent to the Workflow service.
Page 527