2019.1

You can quickly identify variable information that is already present in your variable properties
as such:
l
A percentage sign identifies standard variables, as well as standard and custom job info
variables — %f, for example.
l
A backslash indicates a control character — \004, for example.
l
An at sign (@) indicates a data selection for emulations other than database — @
(1,1,1,1,17,KeepCase,Trim), for example.
l
Field indicates a data selection for a database emulation — field(1,0,0,'Billing_
Email',KeepCase,NoTrim), for example.
l
The lookup() function indicates a lookup in the "Data Repository Manager" on page744.
Special workflow types
PlanetPress Workflow supports multiple input and output types, in so many different
combinations that it would be hard to give example processes for each possibility. However,
some types of processes like PDF and HTTP processes, and processes related to another
product, are important enough to pay some attention to them.
This chapter will describe each of these special workflow types and give at least one example
of an implementation that uses them.
HTTP Server workflow
An HTTP workflow receives requests from a client via a GET or POST request, sometimes only
with information, sometimes with attached files. An HTTP workflow is basically an XML
workflow since that is the type of file created by the HTTP Server Input action task. See the
"HTTP Server Workflow" on page184 page for more details.
PDF Workflow
A PDF workflow uses a PDF as its job file and manipulations are generally made in the
Metadata instead of the PDF itself, since PDF files are much larger than most other data files
compatible with PlanetPress Workflow. The Metadata Tools are extensively used in the
example presented, which is a weekly sales report sent to all the sales associates of a
particular company branch. See the "PDF Workflow" on page191 for more details.
Page 609