--- 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 --- # Nexus map configurations # Nexus map configurations {#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 Nexus map configurations Starting with Operational Resilience version 21.1.x, Nexus map configurations have been introduced to enhance visualization in the Operational Resilience Workspace. Configuring the Nexus map is necessary to display a main node and visualize related data hierarchically. This functionality helps track issues and monitor health effectively by clarifying complex relationships within the Common Service Data Model (CSDM). Show full answer Show less ## Challenges Addressed Before Nexus map configurations, visualizing dependencies across multiple CSDM stages in Workspace views was difficult due to the multidimensional and complex data hierarchies. Traditional list views were inadequate for understanding upstream and downstream impacts, often requiring manual navigation through multiple related lists. ## Key Features * Enables definition and hierarchical visualization of relationships between records on a node map. * Improves understanding of upstream and downstream relationships within complex data models. * Facilitates issue tracking and identification of areas needing attention for troubleshooting. * Integrated with the Data Relationships Framework by default. ## Dependencies The Nexus map configurations require the following hard dependencies: * Data registry for defining data relationships (sndataregistry) * Record Related Items Connected (snrecrelatedItem) Optional dependencies include components for 360° relationship visualization and navigation, especially when using GRC Common Workspace Elements. ## Security and Access Control Access to nodes and their related child records in the Nexus map respects read access control lists (ACLs). Users only see data they are authorized to access, ensuring sensitive information remains protected. ## Configuration Details BCM administrators configure Nexus maps by setting up Main node configurations, which support entities such as services, business services, offerings, business processes, and application services. Administrators can update node, edge, and property settings to tailor the visualization. The Main node configuration source can be defined to specify the data origin for these visualizations. Beginning with Operational Resilience, version 21.1.x, the Nexus map configuration has been introduced. To display a main node in the Operational Resilience Workspace, you must configure the Nexus map. The Node Map configuration UI allows you to visualize related data hierarchically, track issues, and identify areas needing attention for effective resolution or health monitoring. ## Limitations observed before using Nexus map configurations {#nexus-map-configuration__section_ffc_yvr_2hc} Before implementing Node map configurations with Operational Resilience, version 21.1.x, visualizing dependencies across multiple stages of the Common Service Data Model (CSDM) in various Workspace views was challenging. The data hierarchies, as shown in the following example model, are complex and multidimensional, making it difficult to understand relationships between different data entities: * Business Service → Business Service Offering → Business Process → Application → Dependencies * Entity → Policy → Control Objective → Control → Control Indicator {#nexus-map-configuration__ul_wgh_dwr_2hc} List views alone are insufficient for effectively depicting complex relationships, often requiring manual navigation through multiple related lists and records to understand upstream or downstream impacts. Node map configurations offer a more efficient solution, enabling you to visualize these complex relationships easily. ## Benefits of Nexus map configurations {#nexus-map-configuration__section_fzb_kwr_2hc} The Node map configurations, which are part of Data Relationships Framework by default, enable you to define relationships between records and visualize them on a node map. This visualization makes it easier to understand upstream and downstream relationships. The Node map configuration feature offers the following benefits: * It enables any consuming application to define relationships between records and visualize related data hierarchically on a node map. * It facilitates issue tracking and identification of areas requiring attention for troubleshooting purposes. {#nexus-map-configuration__ul_r2y_2zr_2hc} ## Dependencies for Nexus map configurations {#nexus-map-configuration__section_j5m_twr_2hc} The Node map configurations have the following hard dependencies: * Data registry for defining data relationships (sn_data_registry) * Record Related Items Connected (sn_rec_relatedItem) {#nexus-map-configuration__ul_b2n_wwr_2hc} The Node map configuration has the following optional dependencies: * Providing 360° Relationship Visualization for rendering 360º view and related items * Using GRC: Common Workspace Elements for navigating to 360º view and related items {#nexus-map-configuration__ul_jpz_zwr_2hc} ## Record visibility based on user access {#nexus-map-configuration__section_tzt_fxr_2hc} Access to records is determined by the read access control lists (ACLs) associated with those records. You can only view records that you have access to. Nodes and their underlying children that you don't have access to, aren't displayed in the map. This functionality verifies that sensitive information is protected and you can only see data that you're authorized to access. For details on Nexus map configurations, including Node and Edge configurations, refer to the "Nexus map configurations related list" in [Main node configurations: A component of the Data Relationships Framework](https://servicenow-prod.fluidtopics.net/TMamt19dEmvG_VKWb3WGDA "Starting with Release 20.1.x, the Main node configurations, supported by the Data Relationships Framework, are available with Operational Resilience to define dependency roll-up chains. Operational Resilience administrators configure the entity types and pillars, generate the entities, and then establish relationships between different CSDM objects. After this setup is complete, data from the CMDB is fetched into Operational Resilience, displaying rolled-up dependencies in the Workspace view."). * **[Node and edge configurations and property settings](https://servicenow-prod.fluidtopics.net/o0080siebvZnAFJNwuQsGw)** To access the Node map configuration from the Operational Resilience Workspace, BCM administrators must set up the Main node configurations. Once the Main node configuration table is set up, it enables you to create configurations for entities such as services, business services, offerings, business processes, and application services. You can update the properties, node, and edge configuration details. * **[Main node configuration source](https://servicenow-prod.fluidtopics.net/G6Ch9RkOo47PYy2MF1VZjw)** You can set up the source for the Main node configurations.