2019.2

l
A regular process will run as soon as an input file is available through its input task or, if it
is scheduled not to run at that time, will start processing as soon as the schedule permits
it. To learn how to create a process see: "Adding a process" on the facing page.
l
Startup processes run only once before every other process in a given configuration
(see "Startup processes" below).
l
Subprocesses can be called by any other process (see "Subprocesses" on the facing
page).
l
Error processes can only be used in the On Error tab of a task in your process (see
"Creating and using Error processes" on page101).
Self-replicating processes are in fact regular processes that replicate themselves in the
background when multiple input files are received simultaneously. The input task in a self-
replicating process polls its source once, determines the number of files to process, then
replicates itself up to the maximum allowed and treats the files simultaneously. The initial
process runs again once it has completed itself and replicates again as necessary, until all files
have been processed.
You can either create a regular process that is set to be self-replicating from the start (see
"Creating a process" on the facing page) or change a regular process into a self-replicating
process and vice versa (see "Process properties" on page890).
Processes in a configuration (except startup processes) will always run concurrently. You can
schedule processes to run only at certain times or intervals via their properties (see "Process
properties" on page890).
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132.
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864.
Startup processes always run sequentially.
Page 127