Configure an end-to-end workflow for the business service

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

    • Configure an end-to-end workflow for the business 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 > Business service and select the business service.

      You can select a business service, for example, BS-Pri as shown in the illustration.

      Business service.
    2. Ensure that the CSDM Main node configuration property, sn_oper_res.opres_csdm_main_node_config, is set to Business services.
      For information on setting the property, see Configure property for the Business services or Services configuration.
    3. Verify that the entity is created for the business service, it is listed in the Business Services entity type on the Entity types page, and it is set to active on that page.

      You can verify that the value of the Active column for the Business Services is set to True.

      Business Services.
      1. Verify that the entity is listed in the Entities tab and it is marked as Active.
        Flag.Entity listed.
      2. In the Entity Filters tab, verify the filter condition for the business 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 update and generate the entities.
        Filter.
      Entities are generated for the selected business service.
    4. On the Main node configurations menu, verify that the Opres with CSDM header Main node configuration is set to Active in the column.

      The Opres with CSDM header Main node configuration is used for the business services. The Business process to dependencies, Business service to dependencies, and Service offering to dependencies Main node configurations are used to fetch the dependencies.

      You can verify that the Active flag for the Opres with CSDM header Main node configuration is set to True in the configuration. The following example shows the Main node configurations that are provided with the base system for the OpRes CMDB source.

      Main node configurations.
    5. Open the business service record and to view its dependencies from the CMDB, select Open dependency view.

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

      Dependency view.

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

      List.
    6. 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.

      All scheduled jobs.

      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.

      First.

      After the first (Opres with CSDM header) Main node configuration is executed, three events run in parallel to fetch the dependencies for the Business process, Business service, and Service offering Main node configurations.

      Events.

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

    7. Verify that the corresponding entities are generated in the business service record.
      Entities.
    8. In the business 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 CSDM or dependency assessment in the BIA.Downstream dependencies.
    9. To calculate the red flags, execute the Calculate red flags for CSDM and dependencies scheduled job.

      When the Calculate red flags for CSDM and dependencies scheduled job is triggered, it cleans up all the staging records and then it starts calculating the red flags.

      Red flags.
      Red flags, including issues, high risks, failed controls, change requests, tasks, incidents, and outages, are updated in the business service record.
    10. Optional: 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.

      Dependencies rolled up.
      All downstream dependencies of the business service are rolled up and displayed in the business service record. This step completes the workflow to fetch the CSDM dependencies and red flags data for a business service into Operational Resilience reporting.