2018.1

Output
The task outputs HTMLcode as a job file. Within this HTMLcode, references to external
resources point to the local OLConnect Server and are served to the requester directly when
the HTMLfile is opened in a browser.
Properties
General Tab
l Template File:
l "%o":Select to use a dynamic template name. Click on %o to change the
expression that determines the name of the template to use.
l Template Names:Select the appropriate template. Adding template is done
through the Send to Workflow option in the Designer Module.
l Section:Enter the section name that will generate output. Only one section can be
output. If no section is defined or if the section name is invalid, the default section will be
output.
l
Data Source (see "Input" on the previous page):
l
Record ID:
l Enter a valid IDfor a record, or 0 to provide no data. The record must be valid
for the template used. By default, the record ID is pre-filled with the first record
in the metadata. Right-click the field to access other data selection methods
(see"Data selections" on page26).
l
JSON:
l
JSON String: A JSON object or an array of JSON objects representing
records (see "JSON" on the previous page) or a JSON Record Data List (see
the REST API Cookbook).
This option requires that keys in the JSON data have matching field names in
the data model of the template. When they have, the JSON values are passed
to the template and the personalization scripts of the template will have
access to the values through the record's data fields. (See the Designer help:
Adding Variable Data.)
Page 477