Dependencies determine the order that tasks are executed within a process template by defining what actions need to be completed (or skipped) before a given task should be activated.
Any task that does not have any dependencies set will activate immediately when the process is started. To set a dependency:
- In a process template, select a task, then select Dependencies
- Select one or more tasks to add to any of the dependency types:
- Start after all of these tasks are completed: All of the selected tasks must be completed before this task will activate. If any of the selected tasks are skipped, then this task will also be skipped.
- Start after any of these tasks are completed: Any one of the selected tasks must be completed before this task will activate. If all of the selected tasks are skipped, then this task will also be skipped.
- Start after all of these tasks are either completed or skipped: All of the selected tasks must be resolved in some way (either completed or skipped). This is useful for tasks that are dependent on two different conditional branches of the process.
- Select Save
In most cases, only one dependency type is needed. When setting up a sequence of tasks that should activate one after another, each task only needs a dependency on the prior task (not all previous tasks).
- Review carefully and only add dependencies when necessary. This will reduce any chance of bottlenecks within the process.