---
sourceDocument: Brazil Proactive Service Experience Workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/proactive-service-exp-workflows

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Proactive Service Experience Workflows

ft:clusterId :

    - psew

bundleId :

    - psew

workflow :

    - Customer and Industry


---

# Identify the impact of network issues and create cases from an incident record

# Resolve an incident record in Proactive Service Experience Workflows {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Resolve an incident record by creating cases from
record so that you can identify and solve network issues for your enterprise customers.

## Before you begin

This task assumes that a workflow has already been triggered and an assignment group has been assigned.
Role required: sn_ind_tsm_sdwan.PSEW_USER

## About this task

After a workflow in Proactive Service Experience Workflows triggers, you can
identify the customers and systems that are affected by the network issue. You can
then either automatically create the individual cases for the impacted customers or
create a major case and child cases for a larger number of affected customers.

## Procedure

1. Navigate to the Service Operations Workspace, and select ListIncidentsOpen.
2. Select an incident from the list.
3. **Optional:** In an existing incident, assign the incident.
4. See the affected configuration items (CIs) by selecting the Affected CIs card.
5. See the impacted services by selecting the Impacted Services/CIs card and selecting Refresh Impacted Services.
6. See the affected accounts by selecting the Customer impact tab.  
   To learn more about the Customer impact tab, see [Enhancing customer impact visibility for PSEW processes](https://www.servicenow.com/docs/G144s8qC1fRk9xjoTTG~nQ "Use the customer impact tab to reduce navigation time, and enhance tracking and management of PSEW processes. This visibility enables you to quickly assess business impact and take informed actions.").
7. Look for the names of the customers who are affected by selecting the Affected accounts section and checking the Account column.  
   Typically, the network coordinator creates cases so that the impacted customers are proactively notified of the network-initiated issues.
8. Generate proactive cases for the affected customers.  
   To learn more see, [Generate a proactive case for a customer issue](https://www.servicenow.com/docs/_R5zSGXRnl54jJF9xJsn_w "Generate a proactive case record for a customer issue in an incident, problem, or change. Inform the customer or consumer about the proactive case for the service issue.").
9. Notify a customer about the creation of case record.  
   To learn more, see [Communicate with customer about proactive case](https://www.servicenow.com/docs/3~mi_eqPJdyiElvD9MCNRg "Communicate with the customer about the proactive case that is generated for service issue. Address the issue promptly and maintain clear, effective communication with the customer.").
10. Update the case record about the resolution progress.  
    To learn more, see [Update the proactive case with the resolution progress notes](https://www.servicenow.com/docs/ghAiY4jJagRtM6Z0T0ic4w "Send notes to the proactive case record about the resolution progress. Update the proactive case record using insights from the customer impact tab.").
11. Create reactive case record.  
    To learn more, see [Create a reactive case from the incident record](https://www.servicenow.com/docs/l7u3WIPzZleh5jagENxUzA "Create a reactive case record from in an incident, problem, or change record. Analyze the impact and generate cases for service issues.").
12. If you want to update the probable cause of the incident, select the Cause tab and save your message.
13. Resolve an incident by selecting Resolve on the incident record.  
    In the Resolve pop-up window, enter the resolution code and resolution notes and select Resolve.  
    Note:  
    Only minor cases are automatically closed. For major cases, you must manually close all the related cases.

## Result

When the incident is resolved, it triggers the auto-closure of related cases.

* If there's no major case, all the related individual cases are resolved and are updated with the work notes. The following field values from the parent incident record are also populated in the related cases:
  * Resolution Notes
  * Resolution Code
  * Probable Cause
  {#aw-impact-analysis__ul_rpd_j4t_hvb}
* If there's a major case, the related cases don't get auto-resolved and a message is added to the work notes of the incident record, "There is a major case associated with this incident."The following field values from the parent incident record are populated in all the related major and child cases:
  * Resolution Notes
  * Resolution Code
  * Probable Cause
  {#aw-impact-analysis__ul_cjc_rpt_hvb}
{#aw-impact-analysis__ul_gyb_b4t_hvb}

*[\>]: and then