2021.2

Regular and startup processes can be set to be Active (process runs normally) or Inactive
(process will not run at all); see "Activating or deactivating a process" on page131.
Startup processes
Startup processes run only once before every other process in a given configuration. They can
be used to perform operations that need to be completed once before the configuration can
actually be run, such as to map network drives.
The order in which the Startup processes are arranged in the Configuration Components pane
determines, from top to bottom, the order in which the Startup processes are executed when the
Workflow Service launches. To learn how to reorder processes see: "Reordering objects in the
Configuration Components pane" on page840.
Startup processes always run sequentially.
To learn how to create a startup process see: "Adding a startup process" on the facing page.
Subprocesses
Subprocesses are special processes that can be called by any other process. Subprocesses
act exactly as subroutines in programming languages, allowing users to reuse existing
processes by sharing them to the whole configuration file. They can thus be used to perform
redundant operations that may need to be executed numerous times; for instance, archiving a
copy of a zipped file received as the input job file, then decompressing it before sending the
unzipped version of it back to the calling process.
To learn how to create a subprocess see: "Adding a subprocess" on the facing page.
To call a subprocess from another process, use the "Go Sub" on page479 Process logic task.
Whenever a process calls a subprocess, the main process (the caller) will wait for the called
subprocess to finish its execution before carrying on with its own. This means the subprocess
feature is synchronous with the main process. This also means the calling process actually
appends the subprocess to its own workflow.
Creating a process
Adding a process
There are two different ways to create a new regular process.
Page 127