{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":17646,"path":"governance-risk-compliance/main-node-relationship-fw.md","title":null,"bundle":null,"doc_type":null,"release":null,"body":"---\ntitle: Main node configurations: A component of the Data Relationships Framework\ndescription: 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.\nlocale: en-US\ncanonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/main-node-relationship-fw.html\nrelease: australia\ntopic_type: concept\nlast_updated: \"2026-03-12\"\nreading_time_minutes: 17\nbreadcrumb: [Explore, Operational Resilience, Governance, Risk, and Compliance]\n---\n\n# Main node configurations: A component of the Data Relationships Framework\n\nStarting 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.\n\n## Data Relationships Framework\n\nThe Data Relationships Framework \\(sn\\_grc\\_rel\\_config\\) application provides the underlying framework to retrieve data from the CMDB. The Main node configurations in Operational Resilience support different business views in the CSDM model. The relationships defined in the Main node configuration align with the relationships specified in the CSDM model.\n\n\\[Omitted video\\] Description: An overview of creating a main node configuration.\n\nThe video gives you an overview of creating a main node configuration to visualize incident relationships with affected configuration items and child incidents.\n\n## Setting up the Main node configurations\n\nThe Operational Resilience administrators set up the Main node configurations via the Main node configuration module listed in the **General administration** menu of the Core UI.\n\nFor information on configuring the Main node configurations, see [Configure the Main node configurations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/set-up-main-node.md).\n\n\\[Omitted image \"main-node-config-src-path.png\"\\] Alt text: Source module.\n\nAdministrators can also configure the sources of the Main node configurations by accessing the Main node configuration source module. For information on configuring the Main node configuration source, see [Main node configuration source](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/main-node-configuration-source.md).\n\n## Changes in the Main node configurations in Operational Resilience, version 21.1.x\n\nBeginning with Operational Resilience, version 21.1.x, the following changes are introduced in the Main node configurations.\n\n1.  Properties tab in the UI: A **Properties** tab has been introduced in the UI of the Main node configurations. For more information, see the \"Properties tab introduced in the Main node configurations UI\" section.\n2.  Node relationship configurations related list: The existing Node relationship configurations related list has been enhanced. For more information, see the \"Node relationship configurations related list\" section.\n3.  Nexus map configurations related list: Define the UI configuration for the selected main node by configuring the Nexus map configuration settings. You can configure the node and edge settings as defined in the following sections:\n    -   Node configurations\n    -   Node status configurations\n    -   Edge configurations\n    -   Edge status configurations\n\n## Properties tab introduced in the Main node configurations UI\n\nTwo new properties have been introduced to control the display settings for node maps:\n\n-   Maximum number of nodes: Determines the total number of nodes that are displayed in the node map.\n-   Maximum number of levels: Specifies the maximum number of hierarchical levels to be shown, from top to bottom.\n\n\\[Omitted image \"main-node-config-properties-tab.png\"\\] Alt text: Properties.\n\nThese properties enable you to have more customized and controlled visualization of complex node maps, enhancing the overall user experience.\n\n## Changes in the Node relationship configurations related list\n\nThe existing Node relationship configurations related list has been updated and includes the following changes:\n\n-   Type column: The Type column has been added, offering two distinct options for displaying node relationship information:\n\n    -   Default type: As shown in the earlier illustration, the \"Default type\" column displays the hierarchy from top to bottom. It’s the default option.\n    -   Group type: Aggregates data at a specific node, providing a more focused view.\n\n        \\[Omitted image \"main-node-config-group-type.png\"\\] Alt text: Group type.\n\n    This enhancement enables for more flexible and meaningful visualization of node data.\n\n-   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.\n-   Maximum number of children: You can control maximum number of children to be displayed at the specific node relation. The minimum value for this field is 2.\n-   Another field added to the relationship configuration is \"Direction.\" It specifies the direction of the relationship between the source and target tables.\n\n    The direction can be set to either \"Target to source\" or \"Source to target.\" When set to \"Target to source,\" selecting a node displays all its upstream nodes. This shows the relationships leading to that node. When set to \"Source to target,\" selecting a node displays all its downstream nodes.\n\n    \\[Omitted image \"main-node-config-direction.png\"\\] Alt text: Direction.\n\n    The \"Direction\" column helps you to visualize and understand the relationships between nodes.\n\n-   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.\n\n    \\[Omitted image \"copy-main-node.png\"\\] Alt text: Copy functionality.\n\n\n## Nexus map configurations related list\n\nThe Nexus map configurations related list has been introduced in the UI. Configuring the Nexus map configuration for the selected main node helps you define its UI configuration. This determines how the selected node is displayed in the Nexus map. This setting includes settings for colors, icons, edge configuration, and other visual elements. A single main node configuration can have multiple Nexus configurations, enabling for different data views for the same structure. This flexibility is achieved through configuration at the Nexus map level.\n\n\\[Omitted image \"main-node-config-nexus-map.png\"\\] Alt text: Nexus map configuration.\n\nYou can select the Nexus map configuration from the related list and view or update its configuration details. The Nexus map configuration for \"OpRes resilience map UI\" is shown in the example.\n\n\\[Omitted image \"main-node-config-nexus-map-main-node-tab.png\"\\] Alt text: Main node.\n\nFor every selected main node configuration, you must choose the workspace type where you want to apply this configuration. The available workspace type includes the Operation Resilience Workspace.\n\n**Note:** To display the Nexus map, choose the desired workspace from the available options. If the required workspace isn’t listed, you can create a workspace record by accessing the **Nexus map configuration workspace type** from the **All** menu.\n\nThe **Main node** tab displays the name of the Main node table along with its associated conditions. The **Node UI details** tab shows the Node UI type, which is set to \"Node map default node\" by default.\n\nTo synchronize changes made at the Main node level, such as adding or modifying relationships, into the Nexus map configuration, use the **Sync from main node configuration** UI action. This action helps you to maintain synchronization between the Main node and Nexus map configuration.\n\nThe Nexus map configuration is also referred to as the Main Node UI configuration.\n\nWithin the Nexus map configuration, you can customize two key aspects:\n\n-   Node configuration: This setting involves configuring the UI settings for nodes, including their appearance.\n-   Edge configuration: This configuration involves customizing the edges between nodes, including their type \\(dashed or solid\\), color, and other conditional settings.\n\nThese configurations enable you to tailor the visualization of your Nexus map according to your requirements.\n\n## Node configurations\n\nThe Node configurations related list helps you to configure the UI settings for the selected node. Then the selected node is displayed in the Nexus map according to the UI settings. The following example shows the node configuration settings for the \"Opres resilience map UI \\(Top to bottom\\)\" Nexus map configuration.\n\n\\[Omitted image \"main-node-config-nexus-map-main-node-tab.png\"\\] Alt text: Main node.\n\nNode configuration settings: Selecting the Node configuration related list shows the node configuration settings defined for the selected node. The example shows the node configuration settings defined for the \"Entity \\[sn\\_grc\\_profile\\]\" table.\n\n\\[Omitted image \"main-node-nexus-map-node-configuration.png\"\\] Alt text: Node configuration.\n\nYou can update the following UI parameters for the node:\n\n-   Primary label: Update the primary label to be displayed for the node, for example, Name.\n-   Icon: Update the icon to be used for the node in the main node UI, for example, briefcase-outline.\n-   Secondary label: Update the secondary label to be displayed for the node, for example, class.\n-   Tooltip: Update the tooltip to be displayed when hovering over the node, for example, Name.\n-   **Configuration for set as main node** field \\(Setting a node as the Main Node\\): To enable the **Make this primary** functionality for a node \\(To make a node as a primary node\\), you must configure the **Configuration for set as main node** setting. This configuration reflects the hierarchy flow for the node that is designated as primary. To set a specific node as the Main node \\(primary node\\) at any point, select the Nexus map configuration in the **Configuration for set as main node** field. For example, when viewing node relationships from primary node A to node B and node C, the node chain such as \"A ->B ->C\" is displayed. You can select node B as the Main node \\(primary node\\). The display then shows node A as the upstream node and node C as the downstream node.\n\n    **Configuration for 360° view** field: You can configure this setting to determine the configuration to be used when viewing a 360° view, for example, **Entity**.\n\n    **Context record**: You can define the context record for the selected entity, for example, **Applies to record**.\n\n\nNode map grouping and expansion: The node map displays grouped nodes, such as first node, second node, and third group as expandable. Right-selecting on the grouped node provides the options to either expand the node or view the open list, which lists the number of nodes grouped at that point.\n\n\\[Omitted image \"expand-fun-node.png\"\\] Alt text: Grouped node.\\[Omitted image \"open-list.png\"\\] Alt text: Open list.\n\nExpansion functionality: The node expansion feature enables you to view additional nodes, such as the \"passenger information\" level shown in the example. The expansion of the nodes is updated dynamically based on the number of levels available, enabling a more detailed and controlled exploration of the node map. By using the expand and open list options, you can efficiently navigate the map and better understand the relationships between nodes.\n\n\\[Omitted image \"expand-group.png\"\\] Alt text: Expand group.\n\nNode map aggregation feature: The node map includes an aggregation feature that enables you to group nodes at a specific level. To use this feature, you can change the main node configuration type from **Default** to **Group** as shown in the example. This action aggregates the nodes at the selected level, providing a more consolidated view.\n\n\\[Omitted image \"main-node-config-group-type.png\"\\] Alt text: Group type.\n\nWhen loading a map with a grouped configuration, nodes are initially displayed in a grouped state. Right-selecting on an aggregated node provides the **Open list** option, which displays the entities aggregated at that point.\n\n\\[Omitted image \"open-list-option.png\"\\] Alt text: Open list option.\n\nThis feature simplifies complex node maps, allowing you to focus on specific areas of interest and enhancing overall usability. By using the Group feature, you can more easily analyze and understand the relationships between nodes.\n\n## Node status configurations\n\nThe Node status configurations related list helps you to define conditions for a table and its related lists for the selected node. The example shows entity conditions since the Entity \\[sn\\_grc\\_profile\\] table is being used. These conditions can be set using fields from the node table or related lists. For example, when the conditions defined in the \"Related list conditions\" panel are met, that specific node is marked with the \"Critical\" color and the \"Exclamation-outline\" icon.\n\n\\[Omitted image \"main-node-nexus-map-node-status-configuration.png\"\\] Alt text: Node status.\n\nIn this way, when the defined conditions are met, the node status configuration is updated accordingly.\n\nYou can define multiple filter conditions as shown in the Conditions column.\n\n\\[Omitted image \"main-node-node-status-condition.png\"\\] Alt text: Conditions.\n\nDefault node status configuration: When a condition isn’t defined for the node status configuration, it’s the default node status configuration.\n\n\\[Omitted image \"main-node-node-status-default-condition.png\"\\] Alt text: Default node status configuration.\n\nBy configuring these settings, you can customize the display and behavior of nodes in the Nexus map to suit your needs.\n\n## Edge configurations\n\nEdge configurations can be set up similarly to node configurations. For a given relationship between entities \\(for example, upstream or downstream\\), you can define two edge configurations.\n\n\\[Omitted image \"main-node-nexus-map-edge-configuration.png\"\\] Alt text: Edge configuration.\n\nEdge settings: You can customize the following edge settings:\n\n-   Label: The label to be displayed on the edge.\n-   Tooltip: The tooltip to be shown when hovering over the edge.\n-   Edge type: The type of edge to be displayed \\(for example, solid or dashed\\).\n\nThe Edge configurations related list and Edge configuration record are displayed in the following examples.\n\n\\[Omitted image \"edge-config-record.png\"\\] Alt text: Edge configurations related list.\\[Omitted image \"edge-config-record.png\"\\] Alt text: Edge configurations record.\n\nThe following example shows the maximum number of children from Source to target direction as 3.\n\n\\[Omitted image \"node-rel-config-3.png\"\\] Alt text: Maximum number of children.\n\nAs a result, for every node, the maximum number of children shown is 3.\n\n## Edge status configurations\n\nEdge status configurations can be defined based on specific conditions. You can set the edge color, type, and other properties based on these conditions. For example, you can set an edge to display in magenta by default, or change its type to dashed or solid based on a specific condition. By configuring these edge settings, you can create a more informative and visually appealing Nexus map. The edge configuration settings complement the node configuration settings, enabling for a comprehensive visualization of the relationships between entities.\n\n\\[Omitted image \"edge-status-config.png\"\\] Alt text: Edge status configuration.\\[Omitted image \"edge-status-config-example.png\"\\] Alt text: Edge status configuration example.\n\n## Main node configurations included with the base version\n\nThe Main node configurations are included with the Operational Resilience base version. The following Main node configurations, with the source being the \"OpRes CMDB\", are shipped with the base version:\n\n-   Opres with CSDM header\n-   Business process to dependencies\n-   Business service to dependencies\n-   Service offering to dependencies\n-   Service \\(CMDB\\)\n\n\\[Omitted image \"main-node-menu.png\"\\] Alt text: Menu.\n\n**Note:** You can fully customize the Main node configurations and for each configuration, you can configure the node relationships and Nexus map configurations from the Node relationship and Nexus map configuration related lists. For more information on how to configure the node relationships and Nexus map configurations, see [Configure the Node relationship configurations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/update-node-rel-config.md).\n\n1.  Opres with CSDM header configuration for business services: The Opres with CSDM header configuration defines the relationships for a business service and is primarily used by new customers.\n\n    This configuration sets up the direct and indirect relationships between the following objects:\n\n    1.  Application services\n    2.  Business processes\n    3.  Business services\n    4.  Service offerings\n    The following diagram illustrates the structure of the Opres with CSDM header configuration, available as a base version in Operational Resilience. A business service can have relationships configured with one or more application services, service offerings, and business processes. When entities are generated and scheduled jobs are executed, dependencies are fetched and rolled up to the parent business service. The configuration supports multiple levels of dependencies, as shown in the example.\n\n    \\[Omitted image \"main-node-structure-opres-csdm-header.png\"\\] Alt text: Header.\n\n    For more information on the Opres with CSDM header configuration, see [Opres with CSDM header Main node configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/opres-with-csdm-header.md).\n\n2.  Service \\(CMDB\\) configuration for services: The Service \\(CMDB\\) configuration defines the relationships for a service and is primarily used by existing customers. It supports only one level of dependency, such as a parent service having a child service, a process, or a dependency. A child service can have a process and a dependency \\(such as Dep2 or Dep4 as shown in the example\\). A process can have a dependency \\(such as Dep3 as shown in the sample hierarchy\\).\n\n    \\[Omitted image \"s-sam-hier.png\"\\] Alt text: Sample hierarchy.\n\n    For more information on the Service \\(CMDB\\) configuration, see [Service \\(CMDB\\) Main node configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/main-node-config-bs-cmdb.md).\n\n3.  Dependency configurations:\n\n    The Dependency configurations define the relationships for dependencies that are related to business services, business processes, and service offerings.\n\n    1.  Business process to dependencies: The Business process to dependencies configuration defines the relationships from a business process to its dependencies. The following diagram shows the dependency relationship framework for a business process, available as a base version in Operational Resilience. A business process can have relationships with application services, other business processes, technical services, contracts, third parties, and more. When entities are generated and scheduled jobs are executed, dependencies are fetched and rolled up to the parent business process.\n\n        \\[Omitted image \"main-node-structure-bp.png\"\\] Alt text: Processes.\n\n        For more information on the Business process to dependencies configuration, see [Business process to dependencies Main node configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/main-node-config-bp-to-dep.md).\n\n    2.  Business service to dependencies: The Business service to dependencies configuration defines the relationships from a business service to its dependencies. The following diagram illustrates the dependency relationship framework for a business service, available as a base version in Operational Resilience. A business service can have relationships with locations, contracts, third-parties, third-party engagements and more. When the entities are generated and scheduled jobs are executed, dependencies are fetched and rolled up to the parent business service.\n\n        \\[Omitted image \"main-node-structure-dep-bs.png\"\\] Alt text: Services.\n\n        For more information on the Business service to dependencies configuration, see [Business service to dependencies Main node configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/main-node-config-bs-to-dep.md).\n\n    3.  Service offering to dependencies: The Service offering to dependencies configuration defines the relationships from a service offering to its dependencies. The following diagram shows the dependency relationship framework for the service offerings, available as a base version in Operational Resilience. A service offering can have relationships with application services, other business processes, technical services, contracts, third parties, and more. When entities are generated and scheduled jobs are executed, dependencies are fetched and rolled up to the parent service offering.\n\n        \\[Omitted image \"main-node-structure-so.png\"\\] Alt text: Offerings.\n\n        For more information on the Service offering to dependencies configuration, see [Service offering to dependencies Main node configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/main-node-config-so-to-dep.md).\n\n4.  BCM dependency configurations: When the Business Continuity Management application is installed in an instance, BCM related dependencies are fetched into the Operational Resilience application. The Main node configurations related to BCM, such as BCM-CMDB, Downstream related plan, Plan primary assets, Plan related assets, and Upstream related plans, are shown in the example.\n\n    \\[Omitted image \"bcm-related-main-node-configs.png\"\\] Alt text: Main node configurations for BCM.\n\n    For more information on the BCM dependency configurations, see [BCM dependencies related Main node configurations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/bcm-dep-config-to-opres.md).\n\n\nFor information on gathering data aligned with the latest CSDM model, see [Gathering data aligned with the CSDM setup](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/using-csdm-v5.md).\n\nAfter setting up the Main node configurations, you must verify that the entities are generated in Operational Resilience. Only when the entities are generated in Operational Resilience and the relationships are created in the Main node configurations, CMDB data can be brought into Operational Resilience for reporting.\n\n-   **[Node relationship configurations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/node-relationship-configurations.md)**  \nNode 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.\n-   **[Nexus map configurations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/nexus-map-configuration.md)**  \nBeginning 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.\n\n**Parent Topic:**[Exploring Operational Resilience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/what-is-opres.md)\n\n"}}