--- sourceDocument: Australia Governance, Risk, and Compliance sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/governance-risk-compliance Release : - australia ft:locale : - en-US ft:publication_title : - Australia Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Dependency Configuration records # Dependency Configuration records {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Dependency Configuration Records Dependency Configuration records in ServiceNow are managed by BCM administrators using the administrator view (UI16) to automate updates of Business Impact Analysis (BIA) dependencies, related assets, and sources by leveraging CMDB data. Starting with the Xanadu release, customers can choose to pull dependency updates from either all available source records or only the latest record for dependency updates related to Impact Analysis, Planning, and Events. Show full answer Show less ## Key Features * **Update Options:** Administrators can set configurations to pull dependencies from either all records or only the latest record in the Impact Analysis, Planning, and Event dependency update configurations. * **Dependency Sources:** * For plans, dependencies are pulled from BIA upstream/downstream dependencies and CMDB. * For events, dependencies include BIA upstream/downstream dependencies, CMDB, plan primary assets, and related assets. * **Scheduled and On-Demand Updates:** The system supports scheduling automatic updates via configuration records and allows manual updates through the "Update dependencies" UI action. ## Configuration Areas * **Impact Analysis Dependency Update Configuration:** Schedules automatic updates of BIA dependencies based on CMDB data and relationships. * **Planning Dependency Update Configuration:** Enables scheduling of automatic updates for related assets in plans, utilizing data from CMDB and BIA sources. * **Event Dependency Source Configuration:** Defines sources for event dependencies, ensuring impacted assets are added to events and exercises based on relationships from BIA, CMDB, and plans. ## Practical Implications for ServiceNow Customers By configuring these dependency records, BCM administrators can ensure that plans, impact analyses, and events have the most current and comprehensive dependency data derived from CMDB and BIA sources. This improves accuracy in risk and impact assessments and enhances the reliability of business continuity plans and exercises. Choosing between "All records" or "Latest record only" allows customers to control the scope and timeliness of dependency data updates, optimizing the relevance and efficiency of dependency management workflows. The BCM administrators configure the Dependency Configuration records. Administrators configure Dependency Configuration records in the administrator view (UI 16) to schedule an auto-update of BIA dependencies, related assets, and sources based on CMDB data. Note: Beginning with the Xanadu release, you can access up-to-date information on dependencies related to Business Impact Analysis, Plans, and Events. To access the most recent updates for dependencies, choose All records or Latest record only from the Source records to consider option in the Impact analysis dependency update configuration, Planning dependency update configuration, and Event dependency source configuration records. Based on your selection, the application pulls dependencies from all sources or only from the latest record for each source. The example shows the Planning dependency update configuration record. Consider an example where you have 2 BIAs done on Acrobat and the configuration is shown in the example. When All records option is selected and you select Update dependencies UI action from the plan record, the application pulls all the dependencies in all BIA records that satisfy the requirement. As shown in the example, dependencies of both BIA Latest and BIA Old records are pulled into the plan. When Latest record only option is selected and you select Update dependencies UI action from the plan record, the application considers one of the records of the two BIAs. It fetches the dependency assessment of that BIA record. The Update dependencies UI action and the Update BCP dependencies snapshot scheduled job require Impact analysis dependency update configuration, Planning dependency update configuration, and Event dependency source configuration records established. ## Pulling latest dependency updates for impact analysis, plans, and events {#dependency-config-modules__section_gtb_wvm_dcc} You can pull latest dependency updates for impact analysis, plans, and events. Choosing All records or Latest record only functionality is applicable for Impact analysis dependency update configuration, Planning dependency update configuration, and Event dependency source configuration records. For Impact analysis dependency updates, pulling all BIA records or the latest BIA record may yield the same information. For planning dependency updates and event dependency updates, pulling all BIA records or the latest BIA record pulls the latest dependency updates. Dependencies are fetched from these sources for the plans: * BIA upstream dependency * BIA downstream dependencies * CMDB {#dependency-config-modules__ul_w4f_vtm_dcc} Dependencies are fetched from these sources for the events: * BIA upstream dependency * BIA downstream dependencies * CMDB * Plan primary assets * Plan related assets {#dependency-config-modules__ul_uhy_mv4_b1c} For information on configuring the impact analysis dependency updates, see [Configuring impact analysis dependency updates](https://servicenow-prod.fluidtopics.net/fikJn_hRUJLCAVtLh1KSAA "The BCM administrators configure the Impact analysis dependency update configuration to schedule automatic BIA dependency updates based on CMDB data and relationships."). For information on configuring the planning dependency updates, see [Configuring planning dependency updates](https://servicenow-prod.fluidtopics.net/gctKGfRASQ9qmBwC1ePFmg "The BCM administrators configure the Planning dependency update configuration record. 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."). For information on configuring the sources for adding the event dependencies, see [Configuring sources for adding event dependencies](https://servicenow-prod.fluidtopics.net/y7ImKI95I_TjsDvmUeg0~g "The BCM administrators configure the sources in the Event dependency source configuration record. The impacted assets are added in the events and exercises based on the source data and relationships in the BIA, CMDB, and plans."). * **[Configuring impact analysis dependency updates](https://servicenow-prod.fluidtopics.net/fikJn_hRUJLCAVtLh1KSAA)** The BCM administrators configure the Impact analysis dependency update configuration to schedule automatic BIA dependency updates based on CMDB data and relationships. * **[Configuring planning dependency updates](https://servicenow-prod.fluidtopics.net/gctKGfRASQ9qmBwC1ePFmg)** The BCM administrators configure the Planning dependency update configuration record. 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. * **[Configuring sources for adding event dependencies](https://servicenow-prod.fluidtopics.net/y7ImKI95I_TjsDvmUeg0~g)** The BCM administrators configure the sources in the Event dependency source configuration record. The impacted assets are added in the events and exercises based on the source data and relationships in the BIA, CMDB, and plans.