Creating Dependencies in Task Templates

Projects are all about building a timeline. Taskfeed helps you create repeatable project timelines in Salesforce using Task Templates. In your Task Template define the dependencies between the tasks so when the Template is selected your project plan will be built automatically.

Setting Dependencies Between Tasks

In Taskfeed, the scheduling of any Task that has a dependency on another task (the ‘Predecessor’ task) can be determined when the Predecessor has an End Date and the dependent task has a predefined Lead or Lag number of days in relation to End Date of its Predecessor task.

In other words, the task dependencies are always set as Finish to Start.

A Finish to Start dependency means Task A must finish before Task B can begin" (or "B can't start until A has finished"). (1)

Defining Dependencies within Task Templates.

We can define dependencies within Task Templates by setting a reference against each task, and then setting the predecessor reference on the dependent task. Taskfeed will use this to link all the Tasks together when the template is used. 

  • Every Task will be identified with a unique Reference value

  • If a Task is dependent on another Task, we identify its Predecessor in the Predecessor Reference column. The Predecessor Reference value is the Reference of the task that precedes it.

  • The task dependency is always relative to the End Date of the predecessor task. This is defined on the template with a Lead/Lag (Days) number on the dependent task.

  • The Predecessor Task should always have a set Duration in Days on the template. This is so Taskfeed can set the End Date based on its Start Date and Duration. Without an End Date, dependent tasks cannot be scheduled.

  • If a dependent task can start before the predecessor’s End Date, then we assign a negative number (-1, -2 etc) for the dependent task’s Lead/Lag (Days) value. This represents a Lead in relation to the finish of its predecessor.

💡 In Taskfeed,  it only makes sense to set a negative number for Lead/Lag (Days)  if the Predecessor’s Duration is longer than 1 day - because task dependencies in Taskfeed are calculated Finish to Start.  

    • If a dependent task can start on the same day as the predecessor’s End Date, then we set the Lead/Lag (Days) number as 0 (zero).

    • If a dependent task should start 1 or more days after the predecessor’s End Date, then its Lead/Lag (Days) number is positive to reflect that lag.

Note: In this example a Start Date is provided for each of the Tasks. This is not necessary as we have set the Duration and Lead/Lag (Days). As we have set the Duration and Lead/Lag for each task these will be used to schedule the tasks automatically. 

Considerations for References

  • The reference has to be unique to the Board, this means the same template cannot be used on the same Board more than once.
  • The predecessor references can refer to a reference from another template, however if the predecessor does not exist at the time the template is imported you will receive an error.
  • When defining dependencies if the Tasks have a Duration and Lead/Lag then Taskfeed will build the project schedule automatically. This is done using the End Date of the Predecessor Task then adding the Lead/Lag to get the Start Date for the Task.

Feedback and Knowledge Base