2018.2

Point 7 is critical to understand, as it has an impact on what the client receives. If a process
receives a file that is split into multiple parts and each of these parts generates and output, the
last split's output will be sent to the client. If the last output task generates a PostScript file for
printing, this PostScript is returned to the client.
In most cases, what is returned is what remains after the last task, but only if this task's
processing is done in PlanetPress Workflow. For example, if the data file is a text file and this
file is sent to PlanetPress Image using the Image connector, it is a text file that is returned, not
the output of the Imaging. Similarly, ending a process with the Delete task does not return an
empty file, it returns the actual data file.
This is actually the most used way of returning a response: Generate an HTML file using either
Create File or Load External File, then delete the file as a last output. The HTML is thus
returned to the client.
Example HTTP Workflows
l "HTTP PDF Invoice Request" below (GET)
l "HTTP Brochure Request" on page190 (Customer Information+ POST)
l "Capture Web Manager Workflow" on page229 (Capture + HTTP)
HTTP PDF Invoice Request
This straightforward workflow simply receives a GET request from a browser, loads an existing
PDF invoice from a folder on the hard drive, and returns it to the browser. To do this, a client (or
a web service) would request the following page:
http://ppworkflowserver:8080/getinvoice?in=INV999999
Breakdown of this URL:
l
http:// : transfer protocol. This could be HTTPS if the SSL certificates are activated in the
preferences.
l
ppworkflowserver : name of the machine. This could also be an IP (192.168.1.123) or a
full domain name (www.myserver.com), depending on the connectivity between the client
and PlanetPress Workflow Server.
l
:8080 : The default PlanetPress Workflow HTTP Port, set in the preferences.
l
/getinvoice : The HTTP Action Name, as set in the HTTP Server Input task.
Page 188