About Multiple Dependencies
Benefits of Multiple Dependencies
Why should you use multiple dependencies over the legacy dependency functionality? Multiple dependencies will provide more granularity around structuring projects through allowing to make connections between multiple tasks and allowing you to choose different dependency types (finish-to-start, start-to-finish, start-to-start, and finish-to-finish). Multiple dependencies allow you to link multiple predecessors to individual tasks and set different dependency relationships between them. Previous TaskRay setup uses the Legacy Dependencies feature, which only supports a singular relationship.
While the legacy task dependency functionality will remain in place for existing customers who have been using TaskRay prior to the August 2018 release of TaskRay, it is not recommended to continue using the legacy functionality as it will no longer be supported. It is advised that customers using the legacy functionality complete the migration to the new dependencies.
Migrating To Multiple Dependencies [Admin]
Follow the steps below to migrate to the Multiple Dependencies functionality. All existing dependencies will be transferred to the new structure.
- In TaskRay, click on the Tools & Settings cog icon in the toolbar.
- Click on the Admin tab. You should a "Multiple Dependencies" section with instructions on how to migrate.
- Select Migrate!
- You will receive a notification when the migration is complete.
Remove Legacy Dependency Fields
If you have the Dependent On and Dependency Offset fields on the TaskRay Task details window, you will need to remove them as they are no longer supported.
To remove the fields, you will need to modify the field set on the TaskRay Task. For more information on modifying the Task Field Set, see this article.
To remove these fields, follow the steps below:
- From Setup, navigate to:
- Lightning: Objects and Fields | Object Manager
- Classic: Create | Objects
- Select TaskRay Task.
- Navigate to the Field Sets section and select TaskRay Tasks Field Sets.
- Hover over the Dependent On and Dependency Offset fields under In the Field Set box and click on the Remove button.
Automations and Reports
Because the Multiple Dependencies feature employs a new object structure, it is necessary to reconfigure any Salesforce automations or reports that were set up using Legacy Dependencies fields. Below are some of the most common configurations:
Notify Task Owners When Dependent Predecessor Tasks Are Complete
TaskRay can send out automatic notifications to task owners to let them know that their dependent predecessor tasks are complete. You can read more on this process in this article.
Prevent The Completion of a Task When The Predecessor Task Is Incomplete
Additional validation rules can be put in place to prevent the completion of a task when a predecessor task is incomplete. You can read more on this process in this article.
Legacy Dependencies (No Longer Supported)
The instructions below are for the Legacy Dependencies functionality which is no longer supported (as of the April 2018 release). Please see the new Task Multiple Dependencies article for information on the new functionality.
There are a couple of different ways to create dependencies between tasks. You can either connect dependencies in Plan View, or you can build out the dependency relationships through Task Details on individual tasks.
You can create dependencies between tasks. If you create dependencies, rescheduling a task will reschedule all of its dependent tasks as well. In addition, project start and end dates will also automatically adjust based on the task dates.
If dependencies are not enabled in your org, your admin would first have to enable them.
Additionally, if you are using Project Schedules to designate non-working days (days on which tasks cannot be scheduled), tasks that get rescheduled via dependency updates will also take non-working days into account and will get pushed to the nearest working days.
Add Dependencies in Plan View
For forward-driven tasks, you can make the Start Date of Task B dependent on the End Date and the Duration of Task A. In other words, Task B cannot start until Task A is finished.
In this case, if you move Task A, Task B will update and reschedule accordingly. However, if you move Task B, Task A will not move.
Example: Moving Task A also moves the dependent Task B, as well as all other dependent tasks. However, moving Task B does not affect Task A's dates.
For backward-driven tasks, you can make the Start Date of Task A dependent on the Start Date and the Duration of Task B.
Example: Moving Task A does not reschedule Task B. Moving Task B also moves Task A.
You can remove dependencies if necessary. The simplest way to do this is in Plan View.
- In Plan View, click on the dependency arrow between tasks to select it.
- Press Delete on your keyboard.