Configure main properties of the Operational Resilience so that you can set up and fetch data into the application for reporting purposes.
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
-
Navigate to .
-
Filter the properties for GRC: Operational Resilience application.
-
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:
-
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.
-
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.
-
Select Update.
The updated properties are saved.