---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Configuring planning dependency updates

# Configuring planning dependency updates {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

The BCM administrators configure the Planning dependency update configuration record so that an auto-update of the related assets in the plans can be scheduled based on the source data and
relationships in the CMDB and BIA.

## Planning dependency update configuration record {#confi-planning-dep-updates__section_ugs_sx1_c1c}

The BCM administrators configure details of the plan record, its target records, sources, and notification preferences in the Planning dependency update configuration record as shown in the
following example.

## Configure the sources for fetching the dependencies {#confi-planning-dep-updates__section_mqr_z53_b1c}

The BCM administrators configure the sources for fetching the latest dependencies of the plan from different sources such as BIA upstream dependency, BIA downstream dependencies, and CMDB.  
Nota:  
In the plans, the dependencies are fetched for all primary scope assets.

## Auto-update the dependencies {#confi-planning-dep-updates__section_cnn_ymy_mzb}

The BCM administrators can select the Auto-update dependencies option in the Target tab of the Planning dependency update configuration record to schedule an auto-update
of the related assets in the plans.

## Set the notification preferences {#confi-planning-dep-updates__section_gg1_pbk_xzb}

The BCM administrators select the Send notification option to set the notification preferences for the plan owners. For every planning dependency update, an automated
email is sent to the plan owners about the planning dependency updates and links to the updated snapshot records as shown in the example.

The plan owner and BCM lead reviews the dependency updates from the snapshot record. The delta snapshot record displays the updated dependencies such as Added, Updated, and Deleted assets for the selected
plan record.
For more information on configuring the Planning dependency update configuration record, see [Set up Planning dependency update configuration](https://www.servicenow.com/docs/fxeJlDmW4_gaO3oriKO1Zg "Configure the Planning dependency update configuration record to configure the plan record (for which the dependencies are updated), its target records, sources, and notification preferences.").
* **[Set up Planning dependency update configuration](https://www.servicenow.com/docs/fxeJlDmW4_gaO3oriKO1Zg)**   
  Configure the Planning dependency update configuration record to configure the plan record (for which the dependencies are updated), its target records, sources, and notification preferences.