2019.2

All of these files are made with the Designer and need to be sent to PlanetPress Workflow
before they can be used in the Workflow process; see "Sending files to Workflow" on page457.
When the necessary files have been created and sent to Workflow, the next step is to create a
process in PlanetPress Workflow that generates Print output, using these files.
For more information about how to create a process in Workflow, please refer to the Online
Help of Workflow.
Web processes with OL Connect tasks
Serving a web page, made with a template, via an automated process requires you to design a
web process in the PlanetPress Workflow configuration tool.
This topic explains which tasks and files are used in a web process.
Tip
An easy way to start an OL Connect web project including the web process and the files
that it needs, is to use a Project Wizard. There are two Project Wizards that generate a
sample web project. See "Project Wizards" on page973.
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713.)
Page 222