---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Configuring Operational Resilience properties

# Configure Operational Resilience properties {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure main properties of the Operational Resilience so that you can set up and fetch data into the application for reporting purposes.

## Before you begin

Role required: sn_oper_res.admin

## About this task

Configurations and customizations: When you update an application property, it's considered a configuration. If a function change needs modifications to the code in  Operational Resilience, like the script include, it's classified as a customization.

## Procedure

1. Navigate to AllSystem PropertiesAll Properties.
2. Filter the properties for GRC: Operational Resilience application.  
   The properties for GRC: Operational Resilience application are displayed. For a list of the properties, see [Properties installed with Operational Resilience](https://www.servicenow.com/docs/9NDzAFVqlmUQcX4U2sDWVg "When you install the Operational Resilience application, several system properties are added to your instance. You may not need to modify these properties. The user with the sn_oper_res.admin role can maintain these properties.").
3. Update the values of Dependency pillars in the sn_oper_res.dependency_pillars property by adding the sys_ids of the pillars to the Value field.  
   You can add the sys_ids separated by commas such as e4f77de4537310108722ddeeff7b1263,ab5c78b0533112105806ddeeff7b126f,9c38fde4537310108722ddeeff7b12d0,a5187de4537310108722ddeeff7b127a,c4c775e4537310108722ddeeff7b12d7,2fad3034533112105806ddeeff7b123f. Refer to the following pillars and their corresponding sys_ids:
   * Application Service: e4f77de4537310108722ddeeff7b1263
   * People: ab5c78b0533112105806ddeeff7b126f
   * Data: 9c38fde4537310108722ddeeff7b12d0
   * Suppliers: a5187de4537310108722ddeeff7b127a
   * Technology: c4c775e4537310108722ddeeff7b12d7
   * Facilities: 2fad3034533112105806ddeeff7b123f
   {#configure-opres-prop__ul_jwp_bq1_z2c}
4. Update the sn_oper_res.max_top property.  
   This property is used for the 'Top vulnerabilities to be fixed' section on the Home page. If the property value is set to 5, records are generated for the top 5 vulnerabilities which have most impacted entities, and they are displayed in the ''Top vulnerabilities to be fixed' report on the Home page.
5. Configure the sn_oper_res.top_class_name property to designate any class as the top class in the dashboard.  
   Starting with Operational Resilience Release 21.0.x, this property is updated so that any node, such as business service, business process, or application service, can be the top node. This property is applicable only for the dashboards and not for the Workspace forms. For information on configuring the property, see [Using the flexible data model](https://www.servicenow.com/docs/iBhtgYw~_iZlzWYgxvIrVg "Starting with Operational Resilience, Release 21.0.x, the flexible data model enhances operational resilience metrics by improving data visualization and the flow of dependent services. It also supports multiple dashboards with insights into red flags, business service importance, and impact tolerance.").
6. Select Update.  
   The updated properties are saved.

*[\>]: and then