Dependency Definition

Dependencies are tasks that must be assigned prior to assigning the task of interest. If all of the defined dependency task constraints are not satisfied, the task of interest will not be assigned. Dependencies can consist of both predecessor types and during types. Predecessor types may have temporal constraints for min/max time between the start/stop of the identified predecessor task. During types must be assigned wholly within the assignment window of the during task dependency task.

If the task of interest is a recurring parent definition, and another recurring parent definition is selected as the dependency task, then scheduler will smartly use the other recurring children task that matches the end indices in the name as the dependent task. For example, if I have a recurring parent defined called 'TaskA' that defines 3 children ('TaskA(01), TaskA(02), TaskA(03)'), and I am currently defining another task parent definition called 'TaskB', and I set a predecessor task as 'TaskA', then the following will match up:

• 'TaskB(01)' will use 'TaskA(01)' as a predecessor task constraint.
• 'TaskB(02)' will use 'TaskA(02)' as a predecessor task constraint.
• 'TaskB(03)' will use 'TaskA(03)' as a predecessor task constraint.

If 'TaskB' has more children than 'TaskA', then the task names who's indices do not have a match will not have a dependency definition.

A task's predecessor(s) may be defined on the Dependency Tab of the Task Definition Form.