Available with Workflow Manager license.
Job dependencies allow you to create relationships between jobs that determine the order in which related jobs need to be completed. When a dependent job is added to an existing job, it temporarily restricts that job from progressing while work is performed in the dependent job. Once the work in the dependent job is completed, the dependency is released, and work can continue in the original job.
The following patterns are commonly used to model relationships between jobs:
- Sequential—One job cannot be started until another job is completed.
- Parallel—Two or more jobs are dependent on each other, and none can be closed until all are completed.
- Staggered—A job cannot start until another job reaches a certain step in its workflow.
When a job is paused due to an outstanding dependent job, you are notified of the dependency. You can get more information about the dependency on the Holds tab.
Organizations can manually manage dependencies when necessary or automatically apply them using the Create Job step. For example, a child job can be created for a survey crew to gather additional data in an area before work resumes on the original job. Dependencies can also be used in tandem with parent-child relationships when work is dependent on the completion of subtasks.