4.2 Dependency Views and the Unified Map

Visualizing the relationships between configuration items is critical for understanding the structure of IT services. ServiceNow provides two primary visualization interfaces: Dependency Views and the modern Unified Map. These maps display the structural hierarchy of CIs, enabling administrators, helpdesk agents, and change managers to trace dependencies upstream (to business services) and downstream (to database instances, virtualization hosts, and network gear).

Architecture of Relationship Visualization

All visual mapping tools in ServiceNow rely on the backend database structure of the CMDB. Specifically:

• CI Relationships [cmdb_rel_ci]: This table is the source of truth for all relationships depicted on the maps.
• Relationship Types [cmdb_rel_type]: Defines the semantic nature of connections (e.g., Runs on::Run-time, Contains::Contained in).
• Traversals: The visualization engine queries these tables dynamically when a user clicks the map icon next to a CI field on a task or record form.

The modern Unified Map provides a single, responsive experience that replaces legacy, disjointed mapping interfaces. Whether viewing a manually mapped Application Service, a dynamically discovered Service Map, or a general infrastructure dependency view, the platform utilizes the Unified Map UI components.

---

Layout Configurations and Filtering Controls

Different infrastructure architectures require different visual representations to be readable. The Unified Map offers five primary layout styles:

1. Force-Directed Layout: Best for complex, mesh-like network topologies where nodes are distributed organically based on spring physics.
2. Radial Layout: Places the root CI at the center and radiates dependent CIs outward in concentric circles, ideal for understanding localized impact.
3. Group Layout: Groups CIs by their class or container (e.g., grouping all servers inside a virtual cluster block), emphasizing boundaries.
4. Vertical Layout: A top-down tree diagram that shows service hierarchies clearly, with business layers at the top and infrastructure layers at the bottom.
5. Horizontal Layout: A left-to-right diagram similar to the vertical layout, useful for tracing linear processing chains or data flows.

Filtering and Depth (Hops)

By default, the mapping engine displays dependencies up to 3 levels (hops) away from the focal CI (both upstream and downstream). Users can customize this setting:

• Traversal Limits: Setting the depth too high (e.g., 6 or more levels) in a massive CMDB can cause browser performance issues. The maximum traversal level is governed by system properties.
• Relationship Type Filters: Users can toggle relationship categories off or on. For example, an operator might disable Power relationships to focus strictly on Logical Application dependencies.
• Class Filtering: Users can filter out specific CI classes (e.g., hiding all IP Address CIs to declutter the map).

---

Map Indicators and Interactive Badges

The Unified Map is not just a static topology diagram; it is an active operational dashboard. The interface superimposes Map Indicators (badge icons) onto CI nodes to display real-time operational health and compliance data:

• Active Incidents: Shows critical, high, or moderate incidents currently assigned to the CI, allowing helpdesk agents to pinpoint the source of service degradation.
• Pending Changes: Displays scheduled maintenance windows or active change tasks. This helps change managers identify unauthorized changes or coordinate scheduled outages.
• Active Outages: Displays real-time service degradation or complete downtime records linked to the CI.
• CMDB Health Alerts: Badges indicate if a CI has failed a completeness, correctness (e.g., flagged as duplicate or orphan), or compliance rule. This allows CMDB managers to perform data-quality triage directly from the map.

---

Platform Integration and Operational Workflows

Dependency views are integrated throughout the ServiceNow platform to streamline common ITSM and ITOM workflows:

Incident Management and Root Cause Analysis

When an incident is raised against an Application Service, a support engineer can open the Unified Map. If a downstream server displays an active incident badge, the engineer can trace the dependency line to determine if that server's failure is the root cause of the service outage.

Change Management and Risk Assessment

Before approving a Change Request, change advisory board (CAB) members inspect the change's impact map. The platform automatically calculates the impacted upstream services and displays them on the map. This visual proof ensures that maintenance windows do not conflict and that affected business owners are notified.

Comparison Table: Layout Selection Guidelines

Personalization and System Administration

Administrators and users can save their view preferences to avoid reconfiguring maps during troubleshooting sessions:

• Saved Views: Users can save their layout, filter, and level preferences. These are stored on a per-user basis.
• System Properties: Key properties, such as glide.cmdb.dependency_views.max_levels and glide.cmdb.dependency_views.node_limit, allow administrators to establish guardrails. These prevent users from launching queries that attempt to render tens of thousands of nodes, which could crash the client browser or strain application nodes.