Sequential progress with mandatory dependency

Mandatory Dependencies ensure that tasks or workflows only run after their required predecessors have successfully completed. This enables you to enforce a strict sequential order in your workflows, preventing tasks from starting prematurely and ensuring procedural integrity.

Previously, if a predecessor was not found in the plan, a successor would consider the dependency resolved after a short delay. This could lead to tasks running out of their intended logical order, potentially causing confusion and unexpected errors in your automated processes. With mandatory dependencies, you can orchestrate your workflows with the confidence that every step happens exactly when it should.

The introduction of Mandatory Dependencies brings significant benefits:
Prevent premature starts
Guarantee that a successor task only becomes active after its designated predecessor is fully completed, removing any ambiguity from the dependency check.
Maintain the logical flow
Build project plans with confidence, knowing that tasks are run in the precise sequence you intend. This prevents errors and rework caused by out-of-sequence activities.
Increase workflow robustness
Create more predictable and reliable automation. If a mandatory predecessor dependency is not resolved or the task is not found in the plan, the successor task never starts.
Flexible implementation
Apply mandatory dependencies at either the individual task level or the entire workflow level, giving you granular control over your critical process flows.
Mandatory dependencies enable you to build more robust and resilient automation solutions by guaranteeing that your critical tasks always run in the correct, logical sequence. For more information, see Mandatory.