2022.1

that the Connect Server and Workflow must be on the same workstation in order to create
Web output.
The structure of a web process
In a web process two plugins are essential:
l An Input task.
l The Create Web Content plugin.
If the Input task is a Server Input task, that task will return the output of the process - the web
page - to the caller.
The HTTP Action of the Server Input task determines how the process is triggered. If, for
example, the HTTP Action is /hello, the process will be invoked when the Workflow server
receives a request for a resource called hello. (You could, for example, trigger the process by
typing the following URL in the address bar of your browser: http://localhost:9090/hello, if the
browser runs on the same machine as the Workflow server and the Input task is a NodeJS
Server Input task. The protocol could be HTTPS, depending on the settings of the Input task.)
To trigger the process from a Web Form, set the Action of the Form to the HTTP Action of the
Input task. (See "Forms" on page751.)
The Create Web Content task creates an HTML output file from the Web context in a template.
Select the Web template in the task's properties.
If the Web template doesn't need any data, you can set the Data Source of this task to JSON
and enter an empty JSON string: {}, or set it to Record ID and enter 0 (zero).
However, if the template should be merged with data, the task needs either a valid Record ID or
a JSON object. In that case, one or more steps must be added to the process to provide the
required data. For example:
l An Execute Data Mapping task that retrieves data from the job file (such as the request
XML). This task outputs one or more records to the Metadata. By default, the Create Web
Content task uses the first Record ID from the Metadata.
l A Retrieve Items task that retrieves an existing record from the OL Connect database and
outputs it in the Metadata or as JSON object.
Which task or tasks fit best, depends on where the data must come from.
Page 193