2018.2

In addition it may be useful to know the number of each failed page. If a job contains 1000
documents and if documents 1 to 950 were printed correctly, you might not need to resubmit the
entire job, but only the input data for the 50 last documents. However this is only useful if the
relationship between the input data and actual output documents is easy to determine.
For help on how to include (data) page numbers in a PlanetPress Suite Design document, or
page numbers in a Connect template, please see PlanetPress Design User Guide or Connect
Online Help, respectively.
Debugging your PlanetPress Workflow process
After designing a process, which is to add the different tasks, branches and conditions to the
process and configuring them (see "About processes and subprocesses" on page113), you
can test whether or not the process and configuration actually work.
Once you have created and fully debugged all your processes, you will be ready to send it to
PlanetPress Workflow service. See "Saving and sending a Workflow Configuration" on
page126.
Prerequisites
Before you can start debugging, these are the prerequisites.
l There must not be any "Unknown tasks" on page556 in the process.
l A sample data file must be selected; see "Choosing a sample data file" on page65.
Note
The sample job file should generally be the exact same format as the data that the
process will receive when PlanetPress Workflow is processing the job at run-time.
About the Debug mode
When debugging your process, it is important to keep in mind that:
l
The initial Input task is never executed. The sample data file is used instead of the initial
run. This is to prevent "live" data from being retrieved by the initial input task while
debugging is being done. If, however, the initial task is critical to the process, it can be
executed by copying the initial input task and pasting it as a secondary input task (the first
Page 94