2019.1

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114), 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127.
Prerequisites
Before you can start debugging, these are the prerequisites.
l There must not be any "Unknown tasks" on page595 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
Action task to actually run in the process). Do not forget, however, to remove this
duplicate task before saving the configuration!
l If any task makes an operation on the system (for example, capturing files, sending data,
printing, etc), it is actually executed, not simulated.
l
Any task is executed with the permissions of the user that is currently running the
PlanetPress Workflow Configuration tool. When running in Service mode, the user
configured in the Configure Services dialog is used instead. If the credentials are
Page 95