2019.1

Table Of Contents
OL Connect Send (see "OL Connect Send" on page510) needs one Workflow process to
handle the job transfer, and in licensed mode it needs at least one other process to interact with
the user. Reports about the use of OL Connect Send might be produced in yet another
Workflow process. For examples of these processes see "Workflow processes in a Connect
Send solution" on page640.
SOAP Workflow
As SOAP can be either a client or a server, two workflows will be presented. The SOAP Client
workflow presents PlanetPress Workflow as the client and will explore how to retrieve WSDL
information and how to make a SOAP request as a client. The SOAP Server workflow will show
how to create a process that responds to SOAP requests, and where our own WSDL is located.
PlanetPress Capture Workflow (PlanetPress Suite only)
A Capture workflow is divided in two steps: Creating an output of documents containing the
PlanetPress Capture Fields, and retrieving the information from the Anoto Digital Pen to merge
it with the original documents. See "PlanetPress Capture Workflow" on page195 for more
details.
HTTP Server Workflow
An HTTP Server workflow is one that has one or more processes that always start with the
HTTP Server Input task and returns something to a client using a web browser. Each process
would have a specific task referred to as an "action", called from the browser itself.
HTTP Server Input tasks are typically used in one of the two following situations:
l
HTML Form Action: An HTML Form in the browser that may contain text and attached
files can be filled and sent to a process with the HTTP Server Input task.
l
HTTP Data Submission: A custom application or a server sends the request to
PlanetPress Workflow using either a POST or GET command. The application or server
then waits for a response from PlanetPress Workflow Tools.
PlanetPress Workflow can serve both static and dynamic resources to a web browser, however
it is not meant to be used as a fully featured web server, as it is not built for responsiveness nor
guaranteed uptime. It is much better to have a common web server (for example, IIS or Apache)
to serve your contents and to have PlanetPress Workflow available only to process things only
Page 184