2022.1

Note
By default, the Create Web Content task inserts a <base> meta tag in the generated
HTML, specifying a default URL and target for all links on the web page. By
pointing to the Connect Server the job was sent to, the <base> tag enables the
HTTP server to retrieve the resources that were saved with the Designer template.
Since the <base> tag corrupts local anchors - links to another location in the same
web page -, the task also replaces the HREF attribute of local anchors with
JavaScript code. With this modification, local anchors will work; however, relative
URLs with hashtags still won't work.
Modifying the HTML this way isn't useful when all resources are either embedded in
the HTML file, or hosted outside of the template. So when the "Embed all
resources" or "Do not alter HTML" options (or both) are checked, the <base> tag
isn't added and local anchors aren't modified.
l
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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: 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.) Numeric string
values need to be parseable as a number (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.
Page 578