8.8

l The "Metadata Level Creation" on page524 creates the Document level of the metadata
by placing each PDFdata file in its own Document level. It does this by detecting when
the Address in the document changes.
l Then, the "Metadata Fields Management" on page515 adds a few fields at the Document
level in order to properly tag each document with the appropriate information, in this case
the CustomerID, Country and Rep ID. These fields are identical to ones that would have
been added in PlanetPress Design, and are used for the following metadata tasks.
l The "Metadata Filter" on page521 follows by removing any invoice that is not in the US.
Note that the Metadata filter is an *inclusive*filter, meaning that the filter includes the
parts of the metadata where the result of the filter is true, and filters out anything else.
l The "Metadata Sorter" on page530 then re-orders the metadata documents by Rep ID, so
that all of the invoices for any particular sales representative are all together.
l "Lookup in Microsoft® Excel® Documents" on page440 then uses the Rep IDfield to
retrieve each sales rep's email from a specific Excel spreadsheet.
l The "Metadata Sequencer" on page528 acts like a splitter, where the separation
happens whenever the Rep ID changes. Since documents are sorted with that field, each
sequence can contain one or more document, but they will all be for the same Rep ID.
l "Create PDF" on page293 is then used to generate a single PDFfor each sales rep.
Because Create PDFworks in conjunction with Metadata and because it can be used in
pass-through mode, in this instance it will only take the relevant PDFpages from the
original data file in order to create a single PDF file. Other than the extraction of these
pages, the original concatenated data file is untouched.
l Finally, the output is done using a "Send to Folder" on page641 in this case. Obviously,
this should be a "Send Email" on page636 output, but since we don't want to spam
anyone, instead we place the PDFin a folder with the rep id's email as a folder name.
Workflow processes in a Connect Send solution
OL Connect Send needs one Workflow process to handle the job transfer, and in licensed
mode it needs at least one other process to interact with the user. Reports about the use of OL
Connect Send might be produced in yet another Workflow process.
Each OLConnect Send solution will require the Workflow processes to be configured
differently, but certain plugins will always be part of the solution.
Job transfer process
The Workflow process that handles the job transfer starts with an HTTP Input task. The action
name of this HTTP Input task must match the last part of the URL for print job submission set in
Page 189