2019.1

l There must not be any "Unknown tasks" on page654 in the process.
l A sample data file must be selected; see "Choosing a sample data file" on page69.
Note
The sample job file should generally be the exact same format as the data that the
process will receive when PReS 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 PReS
Workflow Configuration tool. When running in Service mode, the user configured in the
Configure Services dialog is used instead. If the credentials are different, a job that runs
in debug mode may fail at run-time if the permissions are not available to the Service.
Please see "Workflow Services" on page822 for more details.
Running in Debug mode
Debugging can be run in different ways:
l
From the Debug tab, click on Run. This executes the complete process, step by step,
until it is completed.
l
From the Debug tab, click on Step. This executes only the first task in the process and
waits for further action. While stepping through a process (using Step, not Run),
breakpoints may be used and given steps may be passed, using the buttons on the
Debug ribbon (see below).
Page 100