View affected CIs in the Dependency Views map
Use the Dependency Views map to identify the configuration items (CIs) that are affected by the CI that caused an incident.
Before you begin
Role required: itil, itil_admin, sn_incident_write, or admin
About this task
Often, an incident is related to one or more specific configuration items (CIs). If the configuration management database (CMDB) is populated, the CI records hold information that can help resolve incidents. You can associate configuration items with an incident to see how the incident affects dependent CIs.
Use the Configuration Item field when a single CI is the cause of the incident and use the Affected CIs related list when multiple CIs are affected by the incident. For example, suppose a load balancer in a data center is no longer operational. The Configuration Item field lists the specific server that is out of memory. The Affected CI related list contains the load balancer, the data center, the servers that depend on the load balancer, and business services that are impacted by the missing server.
Procedure
- On the Incident form, associate the CIs.
|
From where |
Action |
|---|---|
|
Configuration item field |
Select the lookup icon ([Omitted image "look-up-icon.png"] Alt text: The Look up icon) beside the field and select the CI. |
|
Affected CIs related list |
|
The Dependency Views map opens in a new tab or window.
-
To see items that this CI affects, select the down arrow and then select View Affected CIs.
[Omitted image "IM_CIOptionsDepViews.png"] Alt text: Dependency Views map with the CI menu open, showing the View Affected CIs option
To add another affected CI to the incident, select the down arrow beside the CI and then select Add Affected CI(s).
Related topics
---
title: View affected CIs in the Dependency Views map
description: Use the Dependency Views map to identify the configuration items \(CIs\) that are affected by the CI that caused an incident.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/it-service-management/incident-management/t\_UsingTheBSMMapToLocateAffectedCIs.html
release: brazil
product: Incident Management
classification: incident-management
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Managing incidents, Incident Management, IT Service Management]
---
# View affected CIs in the Dependency Views map
Use the Dependency Views map to identify the configuration items \(CIs\) that are affected by the CI that caused an incident.
## Before you begin
Role required: itil, itil\_admin, sn\_incident\_write, or admin
## About this task
Often, an incident is related to one or more specific configuration items \(CIs\). If the configuration management database \(CMDB\) is populated, the CI records hold information that can help resolve incidents. You can associate configuration items with an incident to see how the incident affects dependent CIs.
Use the **Configuration Item** field when a single CI is the cause of the incident and use the **Affected CIs** related list when multiple CIs are affected by the incident. For example, suppose a load balancer in a data center is no longer operational. The **Configuration Item** field lists the specific server that is out of memory. The **Affected CI** related list contains the load balancer, the data center, the servers that depend on the load balancer, and business services that are impacted by the missing server.
## Procedure
1. On the Incident form, associate the CIs.
<table id="choicetable_crl_z1k_yy"><thead><tr><th align="left" id="d81725e73">
From where
</th><th align="left" id="d81725e76">
Action
</th></tr></thead><tbody><tr><td id="d81725e82">
**Configuration item field**
</td><td>
Select the lookup icon \(\[Omitted image "look-up-icon.png"\] Alt text: The Look up icon\) beside the field and select the CI.
</td></tr><tr><td id="d81725e97">
**Affected CIs related list**
</td><td>
1. Select **Add** at the top of the list.
2. Select the CI to associate.
3. Select **Add Selected**.
4. Select the Additional Action icon \[Omitted image "additional-actions.png"\] Alt text: and then select **Save**.
</td></tr></tbody>
</table>2. Select the dependency views icon \(\[Omitted image "BusinessServiceMapIcon.png"\] Alt text: Dependency views icon\) beside the **Configuration item** field.
The Dependency Views map opens in a new tab or window.
3. To see items that this CI affects, select the down arrow and then select **View Affected CIs**.
\[Omitted image "IM\_CIOptionsDepViews.png"\] Alt text: Dependency Views map with the CI menu open, showing the View Affected CIs option
To add another affected CI to the incident, select the down arrow beside the CI and then select **Add Affected CI\(s\)**.
**Related topics**
[Dependency Views map](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/c_NextGenBSMMaps.md)
| title | View affected CIs in the Dependency Views map |
| description | Use the Dependency Views map to identify the configuration items \(CIs\) that are affected by the CI that caused an incident. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/it-service-management/incident-management/t\_UsingTheBSMMapToLocateAffectedCIs.html |
| release | brazil |
| product | Incident Management |
| classification | incident-management |
| topic_type | task |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | Managing incidentsIncident ManagementIT Service Management |