The Gantt task dependencies show the relationships between the rendered tasks in the Timeline section.
Each dependency object has to contain the following fields:
- (Required for internal use)
id—Serves as a unique identifier for the current dependency.
fromId—The ID of the task where the dependency starts.
toId—The ID of the task where the dependency ends.
type—The type of Gantt dependency (read more).
If the provided
dependenciesitems do not conform to the
GanttDependencyinterface, you have to provide a
dependencyModelFieldsobject which is internally used to extract the required data from the provided objects (read more).
The following example demonstrates how to bind a
GanttDependency object array to the Gantt.
According to the specified task relationships, the Gantt supports a set of task dependency types. These indicate the way the tasks rely on one another:
- finish to finish (FF)—Task B cannot finish before task A finishes.
- finish to start (FS)—Task B cannot start before task A finishes.
- start to finish (SF)—Task A cannot finish before task B starts.
- start to start (SS)—Task B cannot start before task A starts.
DependencyType enumerable determines the type of the provided dependency.
As sometimes data coming from a remote server cannot be mapped in advance, if you have provided a
dependencyModelFields object, you can use a custom object interface for defining the
dependencies array. The
dependencyModelFields requires information about the custom objects fields which the Gantt will look up when it tries to extract the dependency ID, the start task ID, the end task ID, and the dependency type.