2018.1

This task can be added as an Action task (see "Action Tasks" on page254) or as an Output
task. 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.
Input
This task must receive either a valid Record ID or a JSON object.
Record ID
A valid Record ID can be retrieved from various data sources. By default, when the Record ID
input option is selected, the metadata is used as input. The "Execute Data Mapping" on
page479 task and the "Retrieve Items" on page489 task output metadata containing
information regarding records.
JSON
The Create Web Content task supports two types of JSON:
l A JSON object or an array of JSON objects representing records. If a value in a record
object is a string, it is considered to be a field value. If a value in a record object is a
JSON object, it is considered to be a nested table with detail records. For examples, see
"JSON string samples" on page470.
l A JSON Record Data List (see the REST API Cookbook). When the "Retrieve Items" on
page489 task is set to output Records in JSON, it outputs this kind of JSON data.
If the input is JSON data, the task makes a call to the REST workflow/contentcreation/html/
{templateId} endpoint on the Connect Server. For more information see the REST API
Cookbook.
Note that only the first JSON object is processed, as the endpoint generates HTML output for a
single record.
Processing
For a single record, this task generates the output for the HTMLContext of the specified
template. Any external resources such as images, css stylesheets or JavaScript files, are also
produced and put aside on the OLConnect Server component.
Page 476