Properties installed with Operational Resilience
Summarize
Summary of Properties Installed with Operational Resilience
When the Operational Resilience application is installed, several system properties are added to your ServiceNow instance. These properties are primarily maintained by users with thesnoperres.adminrole, and modifications are typically unnecessary for most users.
Show less
Key Features
- snoperres.allowedtasktables: Defines task relevant tables like problems and incidents for the Operational Resilience [snoperrestask] table.
- snoperres.businessprocesspillar: Identifies the sysid of the Process pillar.
- snoperres.criticalbusinessprocesses: Specifies the sysid for critical business process entities.
- snoperres.criticalservices: Indicates the sysid for service entities.
- snoperres.dependencypillars: Lists sysids of Dependency pillars; extends with new records in the [sngrcchoice] table.
- snoperres.logging.verbosity: Controls the level of detail in log files (options include Debug, Info, Warn, Error).
- snoperres.maxlevels: Sets the maximum number of levels for processing (default is 1).
- snoperres.maxnodes: Defines the maximum nodes processed by the Operational Resilience API (default is 10,000).
- snoperres.maxtop: Determines how many vulnerabilities appear in the Top vulnerabilities report (default is 5).
- snoperres.oprescsdmmainnodeconfig: Main node configuration for data retrieval and record creation in the [sngrcm2mprofileprofile] table.
- snoperres.redflagsexclusion: Lists classes excluded from red flags.
- snoperres.topclassname: Designates a class as the top class in the dashboard.
- snoperres.useAdvancedRisk: Specifies if the High Risk computation uses Advanced Risk or Risk management.
- glide.ui.snoperresimportanceimpacttoleranceassessmentactivity.fields: Configures formatter fields for impact and importance assessment activities.
- glide.ui.snoperresscenarioanalysisactivity.fields: Configures formatter fields for scenario analysis activities.
Key Outcomes
Understanding these properties allows ServiceNow customers to effectively utilize the Operational Resilience application, ensuring proper configuration for task management, risk assessment, and logging. By leveraging the default settings and knowing how to manage the sysids for various entities and pillars, users can enhance their operational resilience strategies and maintain effective oversight of their critical processes and services.
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:
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.
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.
|
| 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 |