2022.2

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: 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 val-
ues that are stored as 0/1 in data fields.) Numeric string values need to be parseable as a num-
ber (either a whole integer or decimal value). 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.
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
page654.
Note: Defaults are not used unless the configuration is sent to the Workflow service.
l
OL Connect Proxy Address: Enter the machine name or IP Address where the OL Connect
Server resides.
l
Port: Enter the port to use to communicate with the OL Connect Server. Default: 9340
l
User name: Enter the user name expected by the OL Connect Server.
l
Password: Enter the password expected by the OL Connect Server for the above user name.
Miscellaneous Tab
The Miscellaneous tab is common to all tasks.
Check the option Use as step description to display the text next to the icon of the plugin in the Pro-
cess area.
Create Web Content
The Create Web Content task generates the output of the Web Context of a specified template for a
single record and returns the HTML code to PlanetPress Workflow for further processing and return to
the requester. Generally, this task is placed within an "HTTP Server workflow" on page221.
This task can be added as an Action task (see "Action tasks" on page351) or as an Output task (see
"Output tasks" on page545). Adding it as an Action task enables the process or branch to continue
after this task. An Output task is always located at the end of a process or branch.
Page 518