--- 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 --- # Node relationship configurations # Node relationship 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 Node relationship configurations Node relationship configurations in ServiceNow enable you to define and manage relationships between records and objects within specified tables. These configurations allow customization of key details for the main node, including its name, source, table name, and filter conditions, facilitating precise control over how data relationships are represented and visualized. Show full answer Show less ## Key Features * **Updated Node relationship configurations related list:** Now includes a **Type** column with two display options: * **Default type:** Displays the node hierarchy from top to bottom (default setting). * **Group type:** Aggregates data at a specific node for a more focused view of relationships. * **Control over map display:** You can set the maximum number of nodes and levels shown on the map globally and at specific node relationships to manage visualization complexity. * **Direction setting:** Defines whether relationships display **upstream (Target to source)** or **downstream (Source to target)** nodes, allowing flexible visualization of data flows. * **Copy functionality for Main node configurations:** Enables duplicating a main node configuration to streamline setup, requiring subsequent Nexus configuration for the copied node. * **Relationship configuration constraints:** The maximum levels property activates only when source and target tables are the same, ensuring relevant settings for hierarchical relationships. ## Practical Application for ServiceNow Customers These enhancements provide ServiceNow customers with greater flexibility and precision in modeling complex relationships between configuration items and business objects. By leveraging the Type options and Direction settings, customers can tailor relationship maps to better suit their operational resilience and data visualization needs. The ability to copy main node configurations accelerates setup processes, especially when managing multiple similar relationship mappings. Additionally, the configuration options support integration with Common Service Data Model (CSDM) objects such as business services and application services through the main node configurations, utilizing the `sngrcm2mprofileprofile` table as the relationship source. Node relationship configurations are used to set up relationships between the records and objects defined in the table. You can configure the details of the main node such as its name, source, table name, filter conditions, and so on. For details on the updates in the Node relationship configurations introduced in Operational Resilience, version 21.1.x, refer to the "Node relationship 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 relationship configurations related list : The existing Node relationship configurations related list has been updated and includes the following changes: * Type column: The Type column has been added, offering two distinct options for displaying node relationship information: * Default type: As shown in the earlier illustration, the "Default type" column displays the hierarchy from top to bottom. It's the default option. * Group type: Aggregates data at a specific node, providing a more focused view. {#node-relationship-configurations__ul_kzd_lx2_fhc} This enhancement enables for more flexible and meaningful visualization of node data. * Maximum number of nodes and Maximum number of levels: You can set the maximum number of nodes and levels for the map (as shown in the Properties tab). Similarly, you can also control the maximum number of children shown at the specific node relation and maximum number of levels shown at a specific node. The Maximum number of levels property is enabled only when the source table and target table in the Main node configuration are the same; if they're different, this property is inactive. * Another field added to the relationship configuration is "Direction." It specifies the direction of the relationship between the source and target tables. The direction can be set to either "Target to source" or "Source to target." When it is set to "Target to source," selecting a specific node displays all its upstream nodes. This shows the relationships leading to that node. When it is set to "Source to target," selecting a node displays all its downstream nodes. This enhancement provides more flexibility in visualizing the relationships between nodes. * Copy functionality at the Main node: The main node configuration now includes a Copy UI action. When this functionality is used, the selected main node configuration is copied and then you're required to set up the Nexus configuration for the copied main node. {#node-relationship-configurations__ul_uqx_2x2_fhc} For information on configuring the Node relationship configurations, see [Configure the Node relationship configurations](https://servicenow-prod.fluidtopics.net/xffF2Q7AeYVPPTVFhiKYHg "Create a Node relationship configuration record to establish relationships between nodes. Update the node relationships including source table, both Configuration Items (CI) and non-CI relationships. The Node relationship configurations define the connections between the source table and other tables (target tables), specifying how they are related."). For information on setting up relationships between different objects, see [Relationships between CSDM objects](https://servicenow-prod.fluidtopics.net/ksnRYrUi__VlMi8ik98Jeg "You can configure relationships between various CSDM objects such as business services, service offerings, business processes, and application services by using the Main node configurations. The [sn_grc_m2m_profile_profile table] serves as the source table for establishing these relationships."). * **[Relationships between CSDM objects](https://servicenow-prod.fluidtopics.net/ksnRYrUi__VlMi8ik98Jeg)** You can configure relationships between various CSDM objects such as business services, service offerings, business processes, and application services by using the Main node configurations. The \[sn_grc_m2m_profile_profile table\] serves as the source table for establishing these relationships.