Search

Modifying Process Execution Parameters

Process execution parameters can be managed in the Execution parameters edit box.

Procedure

Click the Manage Execution Parameters icon in the command bar.
Configure each parameter, following the indications given in the table below.
Click Save.

Parameter name	Description
Maximum number of parallel tasks	The maximum number of tasks that can be executed in parallel at any one time.
Fail policy	How you want to manage any failed tasks. The possible options are: Continue: all other tasks in the process continue to execute, apart from those directly downstream of the task that raised the error. Stop neighbors: the tasks in the same sub-process, and who are connected to the task that raised the error, change from pending to ready status. Any other sub-processes will continue to run and can be successfully computed. Stop process: the whole process stops executing.
Priority policy	How tasks will be executed when there are apparent contrasts in priority order definition: Parent first: in cases of ambiguity, the hierarchical position of tasks will be considered to have a higher priority than the priority number itself. See example below Priority first: in cases of ambiguity, the priority number of the task will be considered to have a higher priority than the hierarchical position of the task. see example below.
Fail policy macro	How you want to manage any failed macros. The possible options are: Continue - if a macro fails, any other macros in the flow will continue to run Stop macro - if a macro fails, the other macros in the flow will not execute
Number of decimals for continuous (-1 for default)	The number of decimal places considered when implicitly or explicitly casting a continuous data type to a nominal data type. -1 is used as a default value for backward compatibility for previous versions of Rulex (prior to Rulex 4), where this option was not included, in which case the value expressed in the Preferences section of the Stage Settings is considered valid).
Cache Vault Variables	If enabled, a cache will be created of vault variables.

Priority policy example

Consider the following process:

If parent first is selected as the priority policy, the tasks will be computed according to their priority level, respecting the hierarchy of the process tasks.

Consequently:

ImportC (as it has the highest priority among the parent tasks: 3)
Import B (priority 2)
ImportA (priority 1)
Concat
Data Manager (priority 10, but it cannot be computed before its parent tasks)

If priority first in selected as the priority policy, the highest priority becomes the Data Manager, despite its hierarchical position. Consequently all the tasks required to compute the Data Manager are assigned its same priority. So ImportA, ImportB, and Concat all assume priority 10, and the computation order consequently becomes:

ImportA and ImportB are executed in parallel
Concat
Data Manager
ImportC (whose priority of 3 is now the lowest priority in the process).