Dependent tasks
Dependent tasks are when one task must start after another finishes or two tasks must start at the same time. Dependent tasks are represented using records created from the business object triDependency in the triIntermediate module.
Two associations from a triDependency record to records that represent tasks are used to identify the tasks involved in a dependency relationship. One of the tasks involved in the dependency relationship is considered to be the predecessor task; the other task is considered to be the dependent task.
The predecessor task must have an association with the triDependency record. The name of the association on the predecessor task side must be Is Predecessor. On the triDependency side, the name of the association must be Has Predecessor.
The dependent task must have an association with the triDependency record. The name of the association on the dependent task side must be Has Dependency. On the triDependency side, the name of the association must be Defines Dependency.
- triDependencyRelationshipLI
- The value of this field determines the type of dependency that
this record represents. The choices available are:
- Finish-to-Finish
- This value means that the finish time of the dependent task depends on the finish time of the predecessor task.
- Finish-to-Start
- This value means that the start time of the dependent task depends on the finish time of the predecessor task. This is the most common type of dependency.
- Start-to-Finish
- This value means that the finish time of the dependent task depends on the start time of the predecessor task.
- Start-to-Start
- This value means that the start time of the dependent task depends or the start time of the predecessor task.
- triLagInputDaysNU
- If the value of this field is negative, it is a lead, which means that the successor task can start sooner. If the value is positive, it is a lag, which means the successor task has to start later. Whether this is measured from the start or finish of the predecessor task to the start or finish of the dependent task is determined by the value of the triDependencyRelationshipLI field.
- triLagInputHoursNU
- If the value of this field is negative, it is a lead, which means that the successor task can start sooner. If the value is positive, it is a lag, which means the successor task has to start later. Whether this is measured from the start or finish of the predecessor task to the start or finish of the dependent task is determined by the value of the triDependencyRelationshipLI field.
- triLagWorkingHoursNU
- If the value of this field is negative, it is a lead, which means that the successor task can start sooner. If the value is positive, it is a lag, which means the successor task has to start later. Whether this is measured from the start or finish of the predecessor task to the start or finish of the dependent task is determined by the value of the triDependencyRelationshipLI field.
Dependencies can be created from within the Gantt section by dragging a line between two tasks, provided there is workflow called triTask - Synchronous - Create Dependancy from Selected Task that creates a triDependency record with the necessary associations.