Dependencies determine the order among tasks. When an action requires the creation of several tasks, setting a dependency for each task sets the relationship between the tasks and their start or end dates. For example, it ensures the completion of a designated task before the start of another task.
Note: The functionality of dependencies and offset field is enforced only during the tasks automated creation using task templates.
For example, a support manager wants an employee to call back to a customer and another employee to follow up with a salesperson. Dependencies can be created to ensure the salesperson is contacted before the customer is called back. Dependent tasks are tasks that are completed in a specific order.
Use the offset feature to organize tasks with time-sensitive restrictions. Enter a numeric value in the Offset field plus an appropriate unit of measure, such as one hour or 30 minutes, to separate the initial task template from a subsequent task template. This way, tasks are time dependent. For example, you can have a one day (offset) time frame between when the salesperson is contacted and the customer is called back. This allows the salesperson to have one day preparation before the customer is called back.
Please note that the difference between dependencies and parent-child tasks is that a parent task and its child tasks do not have a specific order for completion. They are not, therefore, dependent on each other. The dependent tasks have to follow a specific sequence. If desired, specific time restrictions (offsets) can be specified between each dependent task.
The Offset value determines the time that separates the action of initial tasks from subsequent tasks. Use this feature to organize tasks with time-sensitive restrictions.
Responsibility: CRM Administrator
Dependency types define the relationship between dependent tasks and their start or end dates. There are four dependency types:
Finish to Start: The successor task cannot start until the predecessor task finishes.
Example
For example, a document needed for a customer is completed before an agent calls on the customer.
Start to Finish: The successor task cannot finish until the predecessor task starts.
Example
For example, the on-site training person cannot leave until the implementation consultant arrives and is ready to start.
Start to Start: The successor task cannot start until the predecessor task starts.
Example
For example, two service representatives need to call on the same customer at the same time to perform two different tasks that are related and require cooperation.
Finish to Finish: The successor task cannot finish until the predecessor task finishes.
Example
For example, the implementation consultant starts weeks before user training begins, but the consultant assists with training and isn't finished until the training is also completed.
There is a validation flag for each dependency, which is defaulted to no. If it is set to Yes, then validations are done when dependencies are created, updated, or deleted. The following are some of the validations that are performed:
The schedule for a scheduled task is validated against the dependency type.
For the Finish to Start dependency type, the task B start date is not less than the task A end date.
For the Start to Finish dependency type, the task B end date is not less than the task A start date.
For the Start to Start dependency type, the task B start date is not less than the task A start date.
For the Finish to Finish dependency type, the task B end date is not less than the task A end date.
A task depends only once upon another task.
The predecessor task cannot depend on the successor, creating a cycling dependency.
Tasks cannot make a cyclic chain, with the first task linked with the last one in a cyclic manner.