8.5

l Since the initial input task is not performed, there is no actual job information to be added
at the beginning of a data file. Note that you can use the Object Inspector on your
process to enter sample job information as required.
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 and this may lead to
unexpected behaviors. Please See "Workflow Services" on page592 for more details.
Note
The sample job file should generally be the exact same format as the data that you will
receive when PlanetPress Workflow is processing the job at run-time. For more
information on how to capture your sample data file properly, please refer to the
PlanetPress Trigger and Data Capture Guide.
Debugging can be run in different ways:
l
From the Debug tab, click on Step. This executes only the first task in the process and
waits for further action.
l
From the Debug tab, click on Run. This executes the complete process, step by step,
until it is completed.
l Right-click on any task in the process and click Run from Here or Step from Here.
These actions are the same as using the debug Step and Run buttons, but will execute
the process only starting from that task forward.
While stepping through a process (using Step, not Run):
l Double-click on any task to change its properties. If you change the properties of a task
before you step through it, those new properties will be used when the task is executed.
Note that you cannot modify the process itself while in debug mode (you cannot add,
delete or move tasks, change branches and conditions, etc).
l Click on Skip to ignore the next task or branch and go to the next one. The job file is not
modified in any way.
Page 54