---
sourceDocument: Brazil Customer Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/customer-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Customer Service Management

ft:clusterId :

    - csm

bundleId :

    - csm

workflow :

    - Customer and Industry


---

# Add dependencies between template item

# Add dependencies between template item {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Add dependencies between template items in a task plan template to control the sequence in which tasks are available to agents after the template is applied.

## Before you begin

Roles required: sn_task_plan.viewer, sn_task_plan.navigation_menu, sn_task_plan.admin

Plugin IDs: com.sn_task_plan_templates, com.snc.task_dependency, and com.snc.customerservice.demo.

Confirm that the following conditions are met before you start:

* The task plan template is in Draft state. You can add or edit dependencies only while the template is in Draft state.
* The template contains at least two template items to link as a predecessor and a successor.

{#add-dependencies-between-template-item__ul_ktt_d2k_fjc}

Task dependencies define the order in which agents act on tasks generated from a task plan template. All tasks are created at the same time when the template is applied. Dependencies determine when a successor task are
available based on the status of a predecessor task and any configured time constraints.

Dependencies control the order in which agents can act on those tasks after generation. You can set how strictly a dependency is enforced and add an optional time offset between tasks.

You can define the following dependency types, which determine when a successor task becomes active:
{#add-dependencies-between-template-item__table_emp_52k_fjc__entry__2}

| Dependency type | Status |
|-|-|
| Finish to Start | The successor task is active after the predecessor task is completed. |
| Start Together | The successor task is active at the same scheduled time as the predecessor task. |
| Start after Start | The successor task is active when the predecessor task starts. |
[Table 1. Successor task active status]

{#add-dependencies-between-template-item__table_emp_52k_fjc}

## Procedure

1. Navigate to AllTask Plan Template Workspace.
2. Open a task plan template you want to edit and confirm that the status field shows as Draft.
3. Select the Dependencies tab to view the dependency map.
4. Select New Dependency and complete the required fields:  
   {#add-dependencies-between-template-item__table_omh_2hk_fjc__entry__2}

   | Field | Description |
   |-|-|
   | Predecessor | Select the template item that has to be acted on first. |
   | Successor | Select the template item that follows the predecessor. |
   | Dependency Type | Select dependency type; Finish to Start, Start Together, or Start after Start. |
   | Assignment Criteria | Select the agent assignment criteria. Options are: * None * Same agent * Same day, same agent {#add-dependencies-between-template-item__ul_p5t_phk_fjc} |
   | Minimum Lag Time | Enter the minimum time before the successor task is available, using the days, hours, minutes, and seconds fields. |
   | Maximum Lag Time | Enter the maximum time allowed before the successor task is available, using the days, hours, minutes, and seconds fields. |
   [Table 2. New dependency form]

   {#add-dependencies-between-template-item__table_omh_2hk_fjc}
5. Select Save.  
   A confirmation message indicates that the dependency is created and the dependency map updates to reflect the relationship between template items.  
   Note:  
   If the dependency condition is not met, a warning appears on the successor task when opened. Agents can dismiss the warning and continue.
{#add-dependencies-between-template-item__steps_sxn_xl2_g3c}

## Edit or delete a dependency {#ariaid-title2}

Edit the fields of an existing dependency or remove it from the dependency map in a task plan template.

### Before you begin

Role required: sn_task_plan.writer.

### Procedure

1. Navigate to AllTask Plan Template Workspace.
2. Open the template in Draft state.
3. Select the Dependencies tab.
4. Select the dependency you want to edit or delete.
5. Perform one of the following actions:  
   * To edit: update the required fields and select Save.
   * To delete: select Delete and confirm the action.

   {#task_olf_3jk_fjc__ul_ttf_xjk_fjc}

   A success message confirms the action. The dependency map updates to reflect the change.
{#task_olf_3jk_fjc__steps_r5z_mjk_fjc}

*[\>]: and then