Sample end-to-end workflow for services

---
title: Sample end-to-end workflow for services
description: 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.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/conf-end-to-end-wf-for-ser.html
release: australia
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 3
breadcrumb: [Configure, Operational Resilience, Governance, Risk, and Compliance]
---

# Sample end-to-end workflow for services

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 with the itil user role, sn\_oper\_res.admin with the itil user role

To create a service, you also need a role that can create records on the Service \[cmdb\_ci\_service\] table, such as itil or sn\_cmdb\_editor. With the sn\_oper\_res.manager role alone, you can add existing services to Operational Resilience reporting, but you can't create them.

## About this task

For the configuration sequence and instructions in Operational Resilience, see [Configuring Operational Resilience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/configure-operational-resilience.md).

For instructions on creating the Main node configuration records, see [Configure the Main node configurations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/set-up-main-node.md).

## Procedure

1.  Download the Operational Resilience application in your instance.

    For instructions on downloading the Operational Resilience application, see [Install Operational Resilience application](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/download-opres.md).

2.  Ensure that you have set up the pillars, entity types, entity filters and entities are generated.

    Refer to the configuration instructions on the [Configuring Operational Resilience](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/configure-operational-resilience.md) page.

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

    You can select a service record as shown in the illustration.

    \[Omitted image "service-record.png"\] Alt text: Service record.

4.  To add the service to Operational Resilience reporting, select the service from the list and select **Add to OpRes reporting**.

    The selected service is added to Operational Resilience reporting.

5.  Verify that the entity is created for the service and it is listed in the Services \(OR\) entity type in the Entity types page.

    \[Omitted image "s-sam-ent-types.png"\] Alt text: Entity type.

    Verify that the entity is listed in the **Entities** tab and it is marked as Active in the **Details** tab.

    \[Omitted image "s-sam-ent.png"\] Alt text: Entity.

    **Note:** The following example illustrates how to use entity filters to generate entities. However, for actual entity creation, you should run the **GRC Profile Generation** scheduled job rather than using entity filters.

    For reference, the **GRC Profile Generation** job details are shown.

    \[Omitted image "profile-gen-sch-job.png"\] Alt text: GRC Profile Generation.

    1.  In the **Entity Filters** tab, verify the filter condition for the service that you want to include and fetch it in Operational Resilience.

    2.  Use either **Build your own conditions** or **Select from predefined queries** option in the Entity filter type and select **Save**.

        Entities are generated for the selected service.

6.  Navigate to **All** > **Data Relationships Framework** > **Main node configurations** and select the Main node configuration.

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.

    \[Omitted image "scheduled-jobs.png"\] Alt text: 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.

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

8.  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.

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

10. 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.

11. To view the dependencies of the service, select the **Open dependency view** option.

12. To access a comprehensive overview of the service record, select the **360º view** option.