Set up the Incident Management form

---
title: Set up the Incident Management form
description: Configure the Incident form to see the impact of an incident and then restore affected services. The CSDM framework enables you to view rich context for incidents: the CIs involved in the incident and the service offerings, business applications, and business services that the incident affects.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/it-service-management/incident-management/csdm-inc-mgt-form-configure.html
release: brazil
product: Incident Management
classification: incident-management
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 2
breadcrumb: [Applying CSDM guidelines to Incident Management, Configuring Incident Management, Incident Management, IT Service Management]
---

# Set up the Incident Management form

Configure the Incident form to see the impact of an incident and then restore affected services. The CSDM framework enables you to view rich context for incidents: the CIs involved in the incident and the service offerings, business applications, and business services that the incident affects.

## Before you begin

Role required: admin

## About this task

Incident Management uses the CSDM data structure to display information that assists in solving the incident.

[Go to the 1:00:00 mark on this video](https://www.youtube.com/watch?v=EbuHgr10P98&list=PLkGSnjw5y2U7QNr9jL6TAgwQvYBI_LEtK&index=57) to learn about setting up the Incident form to include the related lists that leverage the CSDM framework.

## Procedure

1.  Navigate to **All** > **Incident** > **Administration** > **Incident Properties**.

2.  In the Incident Related List Properties section, enable the following properties and then select **Save**.

    -   **Populate Impacted Services based on Affected CIs**. This property enables display and update of the **Impacted Services/CIs** related list when you perform the **Refresh Impacted Services** action.
    -   **Populate the Business Application related list for incidents**
    -   **Populate the Service Offering related list for incidents**
    The properties are fully described in [Incident Management properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/incident-management/incident-management-properties.md).

3.  Ensure that the **Principal Class** option is selected for the CI or CI class as described in [Create a CI class](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/t_CreateCIType.md) and [Update the list of classes in the Principal Class filter](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/update-principal-class-filter.md).

4.  Navigate to **All** > **Incident** > **Open** and fill in the following fields:

    **Note:** If the UI16 module link redirection feature is enabled in Service Operations Workspace \(SOW\) and the UI16 module supports the redirect configuration, navigating through UI16 paths automatically redirects you to the equivalent list or record pages in SOW instead of displaying the UI16 forms or lists. For more information, see [Redirect UI16 module links to Service Operations Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/service-operations-workspace/redirect-ui16-module-links-sow.md).

<table id="table_qyz_qjm_pwb"><thead><tr><th>

 

</th><th>

 

</th></tr></thead><tbody><tr><td>

Service

</td><td>

The business service or technical service associated with the incident. The value that you specify narrows the list of available CIs that appear for selection in the **Configuration Item** field.

 **Note:** Narrowing the list of available CIs isn't a feature of the base system. To narrow the list, you must specify values for **Service** and **Service Offering**.

</td></tr><tr><td>

Service Offering

</td><td>

The business service offering \(product\) or technology management offering associated with the incident. The value that you specify narrows the list of available CIs that appear for selection in the **Configuration Item** field.

 **Note:** Narrowing the list of available CIs isn't a feature of the base system. To narrow the list, you must specify values for **Service** and **Service Offering**.

</td></tr><tr><td>

Configuration Item

</td><td>

The CI or the affected service, such as hardware, application, and cloud CIs \(physical CIs\) or application services \(logical CIs\).

 You can then use the CI to identify details for incident routing. For example, you can use CI data, such as the support group, and provide information about the service impact by using dependency relationships.

</td></tr></tbody>
</table>5.  Review the information.

    -   The CIs that may have caused the incident appear in the **Affected CIs** related list \[task\_ci\].
    -   The services and service offerings that are related to the populated CI appear in the **Impacted Services/CIs** related list \[task\_cmdb\_ci\_service\].
    -   The services and CIs impacted by the incident appear in the **Impacted Services/CIs** related list \[task\_cmdb\_ci\_service\].

**Parent Topic:**[Applying CSDM guidelines to Incident Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/incident-management/itsm-incident-use-case-product-view.md)