8.4

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 144 (Customer Information+POST)
l "Capture Web Manager Workflow" on page 137 (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 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 number)
would have a value of INV999999 , or any other "valid"invoice number.