8.5

Task Breakdown
l The HTTPServer Input receives the initial request from the browser.
l Because this is a demonstration, a backup is made of the XMLrequest. It's not suggested to do this
every time, especially on servers receiving a large number of requests, as these files do take some
amount of space for each request.
l Acondition checks whether the form has been submitted, by verifying that one of the required fields is
empty. If it is, it means this is the initial request, so the condition becomes true.
l If this is the initial request, an HTMLpage is created which contains a form asking the client for a
required full name and email, and optional company name. A checkmark also offers to subscribe
to a newsletter (it is unchecked by default!). The form submits back to the same URL, meaning it
is handled by the same process.
l The file is renamed with the .html extension, so that both the HTTP service and the browser will
recognize it as an HTMLpage. And then, as usual, it is deleted (but still returned to the browser).
l When the condition is false, it means that there is something in the Full Name field. In this case, we
know that the form was filled and submitted back to the process, and we handle the request as such.
l First, we add the full name, email and company information to job informations, in order for them to be
available for the rest of the process.
l Then, we have a small condition that verifies if the user checked the "Newsletter"box. If so, the
conditional branch is triggered. Note that this condition is put inside its own branch because otherwise,
the rest of the process would not run when the newsletter is selected. Since we want both to happen,
the branch is there with a "stub"if the condition is false.
PDF Workflow
A PDFworkflow, in essence, is one that does not contain any PlanetPress Design document and only uses
PDFfiles as data files. In most cases, this also implies the use of Metadata, as Metadata is used to establish
boundaries between document, sort and sequence (split)the PDF data into different parts.
The idea is that a PDFfile, because it is a formatted document in and of itself, doesn't absolutely need to go
through PlanetPress Design to be processed and printed. Additionally, because of the PDFtools in
PlanetPress Workflow, you can easily merge, split, print and take parts of the PDFfile as required.
Because we are using Metadata, however, here are a few ground rules to keep in mind while working with
such workflows (these rules also apply to Metadata use in general):