2022.2

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 PReS Workflow. For example, if the data file is a text file and this file is sent to PReS Image
using the Image connector, it is a text file that is returned, not the output of the Imaging. Similarly, end-
ing a process with the Delete task does not return an empty file, it returns the actual data file.
Actually the most used way of returning a response is this: generate an HTML file using either "Create
File" on page297 or "Load External File" on page385, then use the "Delete" on page544 task 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227 (Customer Information+ POST)
l
"Capture Web Manager Workflow" on page236 (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 ser-
vice) 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 pref-
erences.
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 PReS
Workflow Server.
l
:8080 : The default PReS Workflow HTTP Port, set in the preferences.
l
/getinvoice : The HTTP Action Name, as set in the HTTP Server Input task.
l
?in=INV999999 : A GET Variable, specifying that the variable named invoicenum (invoice num-
ber) would have a value of INV999999 , or any other "valid" invoice number.
Page 225