Skip to main content

2.10 Configuration Section “When to run the check” in the Initial Condition Task.

Within the “Initial Condition” Tasks, i.e., those Conditional Tasks directly associated with the Start Event within which the conditions that allow the process to be triggered or not are defined, the “When to Run Control” section is presented with the following values:


- “at creation” -> the process will trigger only after the creation of a record (instance of a form)


- “upon creation and modification” -> the process will trigger after the creation or modification of a record (instance of a form), so in fact in all situations currently handled in the processes.

PLEASE NOTE: deletion of a record is a situation not handled in processes


- “upon modification” -> the process will be triggered only after the modification of a record (instance of a module)


- “whenever condition is true” -> the process will be triggered upon occurrence of the conditions (always after saving) entered in the “Conditions” section.

Conditions can also be entered in the “Conditions” section for other values, so this item turns out to be for all intents and purposes analogous to the “upon creation and modification” item, this is because both creation and modification are involved.

- “only the first time the process is triggered” -> the process will trigger are the first time the condition entered in the “Conditions” section occurs.

Thereafter, the process can never trigger on that specific record (instance of a module) again, even if the conditions configured within it have occurred.

- at subprocess launch -> is used exclusively for subprocess configuration and allows the subprocess to be triggered the moment the callback task configured in the parent process is executed.


- “in relation with” -> allows the process to be triggered the moment a relation is established between two records (instance of a module) of two modules having an N - N relation

image.png

Figure 1 (click on image for higher graphic resolution)