Properties installed with Operational Resilience

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
    • Summarize
    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 (Zurich release), a set of system properties is automatically added to your ServiceNow instance. These properties help configure and control various aspects of the Operational Resilience functionality, such as task table references, pillar definitions, logging verbosity, and risk computation. Typically, you do not need to modify these properties unless you have specific customization or maintenance needs. Users with thesnoperres.adminrole have permission to maintain these properties.

    Show full answer Show less

    Key Properties and Their Purpose

    • snoperres.allowedtasktables: Defines task-relevant tables (e.g., Problem, Incident) referenced in Operational Resilience for record generation and maintenance in the snoperrestask table.
    • snoperres.businessprocesspillar, snoperres.criticalbusinessprocesses, snoperres.criticalservices: Store the sysid references for key pillars, business processes, and services to link Operational Resilience components.
    • snoperres.dependencypillars: Contains a comma-separated list of sysids representing various dependency pillars such as Application Service, People, Data, Suppliers, Technology, and Facilities. This enables classification and management of dependency pillars within the system.
    • snoperres.logging.verbosity: Controls the detail level of logs generated (Debug, Info, Warn, Error), with a default of Warn for balanced logging.
    • snoperres.maxlevels: Limits the number of hierarchical levels processed by Operational Resilience functions. Currently, only 1 level is supported.
    • snoperres.maxnodes: Limits the maximum number of nodes processed during Operational Resilience API calls, defaulting to 10,000 to manage performance and data volume.
    • snoperres.maxtop: Defines the number of top vulnerabilities shown in the dashboard’s “Top vulnerabilities to be fixed” report, defaulting to 5.
    • snoperres.oprescsdmmainnodeconfig: Specifies the main node configuration used for data retrieval and record creation in related profile tables.
    • snoperres.redflagsexclusion: Lists classes excluded from red flag notifications, helping focus alerts on relevant entities.
    • snoperres.topclassname: Designates the top-level class displayed in the Operational Resilience dashboard, defaulting to business services (cmdbciservicebusiness).
    • snoperres.useAdvancedRisk: Determines whether to use Advanced Risk computation for high-risk assessments, enabled by default.
    • glide.ui.snoperresimportanceimpacttoleranceassessmentactivity.fields and glide.ui.snoperresscenarioanalysisactivity.fields: Configure the fields displayed in the UI for Impact & Importance Assessments and Scenario Analysis activities, respectively, tailoring user experience during assessments.

    Practical Impact for ServiceNow Customers

    These properties provide foundational configuration for Operational Resilience, enabling you to integrate resilience insights with your existing task tables, define key business pillars, and control system behavior such as logging and data processing limits. Understanding and optionally adjusting these properties helps ensure that Operational Resilience operates effectively within your ServiceNow environment, supports accurate risk assessments, and delivers meaningful reports and dashboards tailored to your organizational needs.

    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

    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

    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

    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
    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