For some particular processes, it may be necessary to halt the process run, and skip the rest of the run. This may be due to an Email Confirmation step where the recipient has rejected the confirmation, or if a validation check from a Decision Control Step has failed.
In these cases, it could be necessary to prevent the rest of the process to continue.
This can be done by configuring step dependencies in a way that skips the remaining steps in the process.
To better illustrate this, given below is an example where Step 3.1 is a Decision Control step that will pass or fail depending on a certain condition. Suppose we wish to stop the process early if Step 3.1 fails, i.e. we do not wish to process Steps 4.1 and 4.2 if the Decision Control step fails.
This can be done by adjusting the step dependency of Step 4.1 as below:
And so, Step 4.1 has been configured to be skip if the condition in Step 3.1 has failed.
Note we can then leave Step 4.2 as the default:
This default configuration indicates that Step 4.2 will only run if the previous step (4.1) has completed successfully. However, since Step 4.1 has been skipped, Step 4.2 will also be skipped.
And so, the process has essentially been configured to stop early if Step 3.1 has failed based on a condition.