Configure an end-to-end workflow for the service

  • Release version: Washingtondc
  • Updated April 22, 2025
  • 3 minutes to read

    • Configure an end-to-end workflow for the service to fetch the CSDM dependencies and red flags data to Operational Resilience. You must ensure that entities are generated and associated with pillars, and that the Main node configurations are set up before fetching the required data.

    Before you begin

    Role required: sn_oper_res.manager

    Procedure

    1. Navigate to Operational Resilience Workspace > List > Service and select the service.

      You can select a service, for example, Blackberry as shown in the illustration.

      Service.
    2. Ensure that the CSDM Main node configuration property, sn_oper_res.opres_csdm_main_node_config, is set to Services.
      For information on setting the property, see Configure property for the Business services or Services configuration.
    3. To add the selected service to Operational Resilience reporting, select Add to OpRes reporting.
      The selected service is added to Operational Resilience reporting.
    4. Verify that the entity is created for the service and it is listed in the Services (OR) entity type in the Entity types page.
      Entity type.
      1. Verify that the entity is listed in the Entities tab and it is marked as Active.
        Entity.
      2. In the Entity Filters tab, verify the filter condition for the service that you want to include and fetch in Operational Resilience.
      3. To update the entity filter condition, change the filter and select the Update entities from filters button on the Entity Types record form to generate the entities for the service.
        Filter.
      Entities are generated for the selected service.
    5. On the Main node configurations menu, verify that the Service (CMDB) Main node configuration is set to Active in the column.

      The Service (CMDB) Main node configuration is used for the services.

      Service (CMDB) Main node configuration.

      In this configuration, only one level of dependency is supported. For example, a parent service can have a child service, a process, or a dependency. A child service can have a process and a dependency, and a process can have a dependency, as shown in the following sample hierarchy.

      Hierarchy.
    6. Open the service record and to view its dependencies from the CMDB, select Open dependency view.

      The dependency view shows how the relationships of the selected service are configured in the CMDB.

      Dependency view.

      You can view the CI relationships of the service, BS1-Pri, by viewing the [cmdb_rel_ci.list] table in the List view.

      List.
    7. To fetch all these relationships into the entity hierarchies in Operational Resilience, execute the Update CSDM and other dependencies scheduled job.

      The following illustration shows all scheduled jobs and their set schedules.

      Schedule.

      The UpdateCSDMDependencies function in the Update CSDM and other dependencies scheduled job fetches all dependencies of the business service into an entity hierarchy, as part of the Opres with CSDM header Main node configuration.

      After the first (Opres with CSDM header) Main node configuration is executed, three events run in parallel to fetch the dependencies.

      Events.

      When the scheduled job is executed, it creates an entity hierarchy for preconfigured relationships in the Main node configurations.

    8. Verify that the corresponding entities are generated in the service record.

      The following example shows that the dependencies of the Email service are rolled up to the parent service, Blackberry.

      Entities.
    9. In the service record, select Go to entities and select the Hierarchy tab to view how the entities are inherited from each other.

      Based on the node relationship configurations set up in each Main node configuration, the downstream dependencies are pulled from the CSDM or dependency assessment in the BIA.

    10. To calculate the red flags, execute the Calculate red flags for CSDM and dependencies scheduled job.
      Red flags, including issues, high risks, failed controls, change requests, tasks, incidents, and outages, are updated in the business service record.
    11. To update only the dependencies and not the CSDM, run the Update other dependencies scheduled job.

      This step is optional. The scheduled job updates additional dependencies for the business service and is configured to run on demand. For more information on the scheduled jobs, see Execute the scheduled jobs.

      All downstream dependencies of the service are rolled up and displayed in the service record.

      Dependencies.

      This step completes the workflow to fetch the CSDM dependencies and red flags data for a service into Operational Resilience reporting.