8.7

Table Of Contents
Task Breakdown
l
The HTTP Server Input task receives a request through the /getinvoice HTTPAction.
Because this task either returns an HTMLpage with an error message or a PDF, the
MIMEtype isAuto-Detect.
l It checks whether the invoice request exists by checking if the size of the file is less than
1kb using "File Size Condition" on page394. The condition returns "true"if the file is not
found:
c:\PlanetPress\archives\pdf\invoices\xmlget('/request[1]/values[1]/invoicenum
[1]',Value,KeepCase,NoTrim).pdf
Here, the xmlget()function grabs the invoicenum variable from the GET request, which
would be INV999999.pdf in the specified folder.
l If the file is not found, then a simple, basic HTMLpage is created indicating the invoice
was not found. For this, a "Create File" on page197 task will suffice, followed by the
Delete output task. As we've already mentioned in "HTTP Server Workflow" on page178,
deleting the data file only means you are not doing anything with it locally - it is still
returned to the client.
l If, however, the file is found, then it is loaded with the "Load External File" on page320
task, and then deleted (for the same reasons).
HTTP Brochure Request
This workflow builds on the knowledge acquired in "HTTP PDF Invoice Request" on the
previous page and uses a single process, but in this case it also uses a PlanetPress Design
document which merges the data received from a browser form with the document to generate
a PDFbrochure, which is sent via email.
Resources
l HTTPBrochureRequest.pw7 (PlanetPress Workflow Configuration)
l InformationBrochure.pp7 (PlanetPress Design Document)
Installation
l Download both files
l Open InformationBrochure.pp7 and send it to PlanetPress Workflow.
Page 184