2018.2

Triggers
In PReS Workflow, a trigger is typically a two line piece of PostScript code placed just before
the data. Triggers tell the printer to turn on PostScript mode and specify which document should
be used in the merging process (PlanetPress Design document+data).
Triggers are used in two situations:
l When the server running PReS Workflow sends a PlanetPress Design document along
with the data to the printer, it adds a trigger before the document (trigger+document+data).
l When the server running PReS Workflow only sends the data to the printer, because the
document is already present on the printer, it adds a trigger before the data (trigger+data).
PReS Workflow adds the trigger code automatically, but you may want to use custom triggers.
You would do this, for example, to use special printer functions. For more on custom triggers,
see the PlanetPress Design User Guide.
Objectif Lune Printer Driver (PS)
Introduction
The Objectif Lune Printer Driver (PS) allows end-users to print directly to PReS Workflow from
any Windows application, by using the familiar File|Print option. At the other end, PReS
Workflow specifically can capture the incoming stream and convert it internally into a PDF file
along with its metadata.
Although it is available with every PReS Workflow, this feature becomes even more useful in
environments where the Document Input emulation is available (with PReS Workflow).
Install a Objectif Lune Printer Driver (PS)
The Objectif Lune Printer Driver (PS) is automatically installed during the PReS Workflow
setup, along with a default Windows Printer Queue called PReS Printer.
Install a Windows Printer Queue using the Objectif Lune Printer Driver (PS)
A Windows Printer Queue using the Objectif Lune Printer Driver (PS) can be installed from
PReS Workflow WinQueue Input plugin properties.
To create a new Windows printer queue from any PReS Workflow:
Page 115