Properties installed with Operational Resilience
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.
Operational Resilience properties
| 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: Integer 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 |