Synchronization between incident and problem records
Summarize
Summary of Synchronization between Incident and Problem Records
This document outlines the synchronization process between incident and problem records in ServiceNow, particularly focusing on how changes in a problem record affect associated incident records. When the Problem Management Best Practice plugins are activated, notifications are sent to users regarding updates to incidents linked to a problem.
Show less
Key Features
- Plugin Activation: Activate the Problem Management Best Practice — Madrid and State Model plugins to enable synchronization.
- Notification System: Users receive notifications for updates on incidents when their state is New, On Hold, or In Progress.
- Workaround Communication: Changes to a problem record allow for communication of workarounds and fixes directly to incident records, ensuring relevant information is shared.
- Incident State Changes: Specific incident states trigger automatic updates and notifications, such as when a problem is resolved or a fix is applied.
Key Outcomes
- When a workaround is communicated, it is added to both the Work Notes and Additional Comments fields of the incident, with notifications sent to relevant users.
- If a problem is marked as resolved with a fix applied, the incident state is updated to Resolved, and a notification is sent to the caller.
- For incidents on hold awaiting problem resolution, additional notes are provided to clarify the status and any risks accepted, maintaining clear communication with users.
Change in a Problem record impacts related Incident records. Notification is sent to the user for each such update.
When you activate the Problem Management Best Practice — Madrid (com.snc.best_practice.problem.madrid) and the Problem Management Best Practice — Madrid — State Model (com.snc.best_practice.problem.madrid.state_model) plugin, the changes in a Problem record impact incidents that are associated to that Problem.
| Plugin | Incident state | Problem state | Action on Problem | Action on Incident |
|---|---|---|---|---|
Problem Management Best Practice — Madrid plugin
|
Any incident state other than resolved, closed, or canceled. | Any | Click the Communicate workaround related link |
|
Problem Management Best Practice — Madrid plugin
|
Any incident state other than resolved, closed, or canceled. | Any | Click the Communicate Fix related link |
|
Problem Management Best Practice — Madrid — State Model plugin
|
On Hold and On hold reason is Awaiting Problem | Problem state is Closed or Resolved and the problem Resolution code is Fix Applied | NA |
|
Problem Management Best Practice — Madrid — State Model plugin
|
On Hold and On hold reason is Awaiting Problem | Problem state is Closed or Resolved and the problem Resolution code is Risk Accepted | NA |
|