---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/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


---

# Properties installed with Operational Resilience

# Properties installed with Operational Resilience {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](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 Properties installed with Operational Resilience

When you install the Operational Resilience application in your ServiceNow instance, several system properties are automatically added.
These properties are primarily maintained by users assigned thesnoperres.adminrole.
While modification is not always necessary, understanding these properties helps you manage and configure the Operational Resilience features effectively.
Show full answer Show less  

## Key Properties and Their Practical Uses

* **snoperres.allowedtasktables**: Specifies task-related tables (e.g., Problems, Incidents) that link to Operational Resilience tasks. This enables tracking of configuration items used across resilience and task management.
* **snoperres.businessprocesspillar** , **snoperres.criticalbusinessprocesses** , **snoperres.criticalservices**: Store sysids for key pillars and entity types, helping define critical business processes and services within the resilience framework.
* **snoperres.dependencypillars**: Contains a comma-separated list of sysids representing various dependency pillars such as Application Service, People, Data, Suppliers, Technology, and Facilities. You can add new pillars by creating records in the \[sngrcchoice\] table and updating this property accordingly.
* **snoperres.logging.verbosity**: Controls the detail level of log files, selectable from Debug (detailed) to Error (minimal). Default is Warn (2), which balances detail and conciseness.
* **snoperres.maxlevels**: Defines the number of hierarchy levels processed by Operational Resilience APIs. Currently, only one level is supported by default.
* **snoperres.maxnodes**: Limits the maximum number of nodes processed during API calls, defaulting to 10,000. This controls performance and data volume in API responses.
* **snoperres.maxtop**: Sets how many top vulnerabilities appear in the "Top vulnerabilities to be fixed" report on the dashboard. Default is 5.
* **snoperres.oprescsdmmainnodeconfig**: Identifies the main node configuration used to create records in the \[sngrcm2mprofileprofile\] table, essential for data mapping and record creation.
* **snoperres.redflagsexclusion**: Lists classes excluded from red flag alerts, such as profiles, BCM plans, and tasks, helping reduce noise in alerts.
* **snoperres.topclassname** : Defines the top-level class displayed on the Operational Resilience dashboard, typically set to *cmdbciservicebusiness* to focus on business services.
* **snoperres.useAdvancedRisk**: Determines whether the high-risk computation uses Advanced Risk or standard Risk Management. Default is True (Advanced Risk enabled).
* **glide.ui.snoperresimportanceimpacttoleranceassessmentactivity.fields** and **glide.ui.snoperresscenarioanalysisactivity.fields**: Specify which fields appear in formatter views for respective activities, streamlining UI display and user interaction.

## Practical Impact for ServiceNow Customers

These properties collectively control how the Operational Resilience application integrates with your existing ServiceNow data, manages key business processes and services, determines logging detail, and limits data volume for performance optimization.

By understanding and, if necessary, customizing these properties, administrators can tailor the resilience capabilities to better align with their organizational structure, risk management preferences, and reporting needs, ensuring more effective risk and resilience management.  
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.

## Properties installed {#props-installed-with-or__section_glq_czh_wdb}

{#props-installed-with-or__table_dx3_gb1_wdb__entry__2}

| Property | Description |
|-|-|
| sn_oper_res.allowed_task_tables | Property used to assign the task relevant tables, such as problems and incidents, that are referenced in the Operational Resilience \[sn_oper_res_task\] table. When a configuration item is used by both the Operational Resilience application and the task relevant tables, a record is generated and maintained in the \[sn_oper_res_task\] table. Type: string Value: Problem |
| sn_oper_res.business_process_pillar | sys_id of the Process pillar. Type: string Value: 6408bde4537310108722ddeeff7b121e |
| sn_oper_res.critical_business_processes | sys_id of the business process entity type. Type: string Value: 221c1c9a53d310108722ddeeff7b12ae |
| sn_oper_res.critical_services | sys_id of the service entity type. Type: string Value: 2d7bd49a53d310108722ddeeff7b1297 |
| sn_oper_res.dependency_pillars | sys_id of the Dependency pillars. It uses a comma-separated list of dependency pillars. For a new pillar, create a new record in \[sn_grc_choice\] table with the Choice category set to Pillar and append the sys_id to the Value using a comma as shown in the example: 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 {#props-installed-with-or__ul_jwp_bq1_z2c} Type: string Value: e4f77de4537310108722ddeeff7b1263,ab5c78b0533112105806ddeeff7b126f,9c38fde4537310108722ddeeff7b12d0,a5187de4537310108722ddeeff7b127a,c4c775e4537310108722ddeeff7b12d7 |
| sn_oper_res.logging.verbosity | Level of detail recorded in the log files, ranging from minimum to highly detailed information. Type: choice list Debug=0, Info=1, Warn=2, Error=3 Default: 2 |
| sn_oper_res.max_levels | Maximum number of levels to be processed (The default value is 1). For current release, only 1 level is supported. Type: string Value: 1 |
| sn_oper_res.max_nodes | Maximum number of nodes to be processed when the Operational Resilience API is called. * Type: integer * Default value: 10,000 {#props-installed-with-or__ul_ldg_5r1_z2c} For example, when the API is called, it displays the results for a maximum 10,000 nodes. |
| sn_oper_res.max_top | Number of vulnerabilities to be displayed in the Top vulnerabilities to be fixed report in the Operational Resilience dashboard. * Type: integer * Default value: 5 {#props-installed-with-or__ul_ppm_vpd_qnb} |
| sn_oper_res.opres_csdm_main_node_config | Main node configuration that is used to get the data and create records in the \[sn_grc_m2m_profile_profile\] table. Type: string Value: c483a911ff2a311051b15c97d53bf1db |
| sn_oper_res.red_flags_exclusion | Classes that are excluded from red flags. Type: string Value: sn_oper_res_profile, sn_oper_res_bcm_plan, sn_oper_res_task |
| sn_oper_res.top_class_name | Property to designate any class as the top class in the dashboard. Type: string Value: cmdb_ci_service_business |
| sn_oper_res.useAdvancedRisk | Property to define if the Operational Resilience High Risk computation should use Advanced Risk or Risk management. Type: True \| False Value: True |
| glide.ui.sn_oper_res_importance_impact_tolerance_assessment_activity.fields | Impact and Importance Assessment activity formatter fields. Type: string Value: assigned_to, state,work_notes,comments, Attachments, opened_by, active, approver |
| glide.ui.sn_oper_res_scenario_analysis_activity.fields | Scenario Analysis activity formatter fields. Type: string Value: state, assigned_to, plan_approver, result_approver, work_notes, comments, Attachments |
[ ]

{#props-installed-with-or__table_dx3_gb1_wdb}