2021.2

The three Output Creation Presets all create PDF output, add the template's name to the PDF's
meta data, and save the file in a certain directory. They all have the Print Virtual Stationery
option enabled. So, what are the differences between these presets?
Groups and separation
The PR_TRAN PDF Full Job preset outputs only one file.
The PR_TRAN PDF per Invoice preset outputs one file per invoice, separating the output by
document.
The PR_TRAN PDF per Customer preset outputs one file per customer, separating the output
by document set.
The last output preset needs the invoices in the job to be grouped in document sets first (by
customer number, in this case). That is what the Job Creation Preset does. This preset is used
by the Create Job task in the Workflow configuration.
Variable file names
The Job Creation Preset does something else, too: it attaches extra information - meta data - to
the documents and to the document sets. Both Output Creation Presets that produce multiple
files use that information in the output file names.
They do that by using a variable in the file output mask field. The variable refers to certain meta
data attached to items at a certain level (the document or document set, respectively). For more
information see "Print output variables" on page1486.
Workflow configuration
Whenever new input data appears in the Workspace\In folder, the invoices are automatically
merged with the data and printed to one file, one file per customer, and one file per invoice.
That is, if the Workflow server is running with the Workflow configuration installed by the Project
Wizard. (See "Running the project" on page162.)
This project's Workflow configuration contains just one process. It is a typical OL Connect Print
process (see "Print processes with OL Connect tasks" on page186), with the difference that it
does not have one Create Output task, but three. Each of them uses its own Output Creation
Preset (see "Print settings" on the previous page).
Note that the Branch tasks back up the job file and job information, so that the main branch
continues with a job file that is unaffected by what happens to the job file inside the branch.
Page 165