---
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 and edge configurations and property settings

# Node and edge configurations and property settings {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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 properties tab in the UI {#configuration-for-node-map__section_dkv_fqs_2hc}

The main node configuration comprises several key properties:

* Maximum number of nodes and levels
* An order field that auto-increments by 10 (You can update the order field manually.)
* A direction property defining relationships between configuration items and entities
{#configuration-for-node-map__ul_ujb_3ws_2hc}

You can update these property settings from the UI directly. For more information on setting up the Main node configurations in your instance, see [Configure the Main node configurations](https://servicenow-prod.fluidtopics.net/d_BOjuVVe~oU~uYRvnAf4A "Create the Main node configuration record to fetch data into Operational Resilience for reporting. Main node configurations are available with the base system. You can use the existing Main node configurations or create new Main node configurations for your business needs.").

## Nexus map configuration related list in the Main node configuration {#configuration-for-node-map__section_gv1_gqs_2hc}

As of Operational Resilience, version 21.1.x, the Nexus map configuration related list is available within the Main node configuration. This enhancement enables you to create multiple configurations for a single main node. You
can designate a default configuration for a main node, which is used when loading the node map. The Nexus map configuration consists of two distinct aspects: node configuration and edge configuration.

## Node and edge configurations {#configuration-for-node-map__section_a2b_gqs_2hc}

The node configuration defines the visual representation of nodes, including their icon, tooltip, primary label, and secondary label. In contrast, the edge configuration determines the appearance of the connections between nodes, such
as line type, color, label, and tooltip.

To access the entity hierarchy graphically, select the Resilience Map button on an entity's Overview tab in the Operational Resilience Workspace list view. The node map illustrates the entity hierarchy based on upstream and downstream relationships.

## User roles and UI display {#configuration-for-node-map__section_xrl_gqs_2hc}

The Nexus map feature is accessible to multiple user roles, although its configuration settings are read-only. The configuration for Nexus Map is managed through the Main node configuration, with related lists for the node
relationship and edge configurations. You can customize properties such as maximum number of nodes, maximum number of children, and edge properties. Based on your configuration settings, the resulting node map is displayed in the
UI.