8.5

l Stop the process, and select the file you saved as your process' data file.
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, PReS Workflow 7.4 and higher also has a new 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.
Once you have created and fully debugged all your processes, you will be ready to send it to
PReS Workflow service. See "Saving and Sending" on page544.
The Plug-in Bar
PReS Workflow offer a constantly increasing number of plugins, while always allowing third
party plug-ins to be installed and set up to be used by PReS Workflow. The PReS Workflow
Plug-in Bar lists the available plugin in any of PReS Workflow, and is divided into categories,
which users can customize at will.
A"Plug-In"is normally something that is added to a software and, while most of the PReS
Plug-ins are installed by default, some may be added so the term is correct. However, because
the plug-ins are always expected to execute some sort of task, they are always referred to, in
this documentation, as "tasks", except in the specific case of importing a new plug-in or
customizing the Plug-in bar.
Categories
Page 55