2018.1

automatically passed to the subprocess, which means that, if the subprocess needs to use a different
emulation than the calling process, a Change Emulation task is required.
If any task converted into a subprocess was previously using local variables, these variables
must be removed or transferred to global variables or Job Information variables to be usable in
the newly created subprocess (see "About variables" on page511).
Running a process on desktop
Since PReS Workflow configurations are typically meant to run without user interaction, all of
their processes are set to run in the background by default. In some cases, such as when a
dialog box must appear or user input is required, you may make any process run on your
desktop instead of as a service.
Generally this will happen only when calling a third-party software using the Run External
Program plugin, but also when using a Script that generates a dialog that someone must click
or interact with.
Note
The term "Desktop" is defined as the desktop of the user logged on to the computer where PReS
Workflow is installed. These dialogs cannot be displayed on any other computer.
Toggling a process’s Run on Desktop property
To toggle a process's Run on Desktop property:
1.
Select an active process in the Configuration Components pane.
2.
In the Object Inspector Pane, change the Run on desktop property from False to True,
or vice versa.
Saving and sending a Workflow Configuration
The core of the PReS Suite workflow tools is the PReS Watch service which, once started,
constantly runs in the background to perform the tasks included in its current configuration file.
The PReS Workflow Configuration tool lets you create, edit, save and send configuration files.
Page 119