---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Node relationship configurations

# Node relationship configurations {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

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, filer 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/I4cX1f~CwtI~FSPMQUGdDQ "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 disabled.
    * Direction: Another field added to the relationship configuration is "Direction," which 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 set to "Target to source," selecting a specific node displays all its upstream nodes, showing the relationships leading to that node. When set to "Source to target," selecting a
      specific node displays all its downstream nodes.

      This enhancement provides more flexibility in visualizing and understanding 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/QUQM0LzqACq1foW6NFHLYw "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/M_ymS2u8ww30Qm~FECK5XQ "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/M_ymS2u8ww30Qm~FECK5XQ)**   
  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.