2022.2

Process properties
To have access to the properties of a process or subprocess:
l
Right-click on the process in the Configuration Components pane.
l
Select Properties.
You can also double-click on the process to show its options.
Note: Subprocesses do not have the General tab which is only used for scheduling, but they do
have the Information tab.
Options
General tab
l
Active: Select to make the process active. Clear to prevent this process from running when you
send the configuration to PlanetPress Workflow.
l
Startup: Select to make this process a startup process (see: "Startup processes" on page107).
This option is not available for self-replicating processes and error processes.
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 change the order you may drag and drop them (see "Moving and
copying configuration components" on page697).
l
Self Replicating: Check this if you want the process to replicate itself in the background when
multiple input files are received simultaneously. When this is checked, the input task 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.
l
Max percentage of threading (%): Determines how many processes you may have running at
the same time. This is a percentage of the maximum number of threads specified in the "Mes-
senger plugin preferences" on page658. For example if the maximum number of threads is 10
and you specify 50% here, a maximum of 5 replications will occur (the original process + 4 cop-
ies).
l
As soon as possible: Select to have the process run continuously. Clear to enable the Time
Grid to fine-tune the schedule of the process.
Tip: Non-startup processes starting with the HTTP Server Input, NodeJS Server Input,
LPD Input or SMTP Input task will run trigger-based if they are set to run As soon as pos-
sible with a Polling interval of 0. This reduces CPU usage.
Page 724