2019.1

l Step through the process in Debug mode until you reach the emulation or data change.
l
Click on View as Text (or View as PDF if your data is PDF at this point) in the Data group
of the Debug tab.
l In the viewer that appears, save the file to a location on your hard drive.
l Stop the process, and select the file you saved as your process's sample data file (see
"Choosing a sample data file" on page65).
l If you need to continue debugging your process after the emulation change, you can still
do it by using Skip on all the tasks until the emulation change, inclusively. Then use Step
or Run to continue debugging.
Lastly, PlanetPress Workflow has an option that can be used in conjunction with the previous to
avoid skipping through large processes:
l
Step through the process until the emulation or data change, as in the first method.
l
Save the data file locally and then select it as your sample data file, as with the second
method.
l
Instead of skipping through each task, use the Run from here or Step from here options,
either from the Debug tab or by right-clicking on the task where you want to start the
process.
About printing
To print a document you can either use an Output task, or a combination of "PlanetPress
Workflow printer queues" on page100 and the Printer Queue Output task. Decisive factors, in
addition to the printer that you're using, are:
l The type of job (Connect, or PlanetPress Suite).
l
The features that you want to use. When you associate a single Printer Queue Output
task with multiple printer queues, you have the option of using load balancing or not (see
"Load balancing" on page108).
l The file type. Printer Queues can only handle PostScript and PDF files.
Printing can be done locally or remotely. The spool file is sent to the printer by the Output task
itself, or by Workflow if the file is placed in a Workflow Printer Queue.
Printer-centric printing - which means that a document and data are merged on a printer - is
Page 98