2018.1

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 Connect template or Design
document and only uses PDF files as data files. The idea is that a PDF file, because it is a
formatted document in and of itself, doesn't need to go through a merge process before it can
be printed.
PReS Workflow provides a few tasks specifically designed to work with PDFs:
l "Merge PDF Files" on page234
l "PDF Splitter" on page335
l "Create PDF" on page269
In most cases, this kind of workflow also implies the use of Metadata tasks (see "Metadata
Tasks" on page418).
You can use Metadata tasks to group, sort and sequence (split) the PDF data. The Create PDF
task will apply the active Metadata to the PDF data file before creating the PDF output.
Things to keep in mind while working with Metadata are set forth in another topic: Working with
Metadata.
Page 183