Change Conflict detection workflow

[RC19]

Hi All,

If there are open conflicts on a change request because of maintenance or blackout schedules, then will the change request be stopped from transitioning to next state? are there any extra approvals and changes in workflow? or does ServiceNow just notifies that there is a conflict and it has be handled offline ?

[RC19]

hi @Tanushree Maiti will the risk/impacted be updated based on these conflicts or is there no impact ?

[Tanushree Maiti]

Hi @RC19 

Risk and Impact are directly associated with the Configuration Item (CI) selected on a change request.

By default, Conflict Detection in ServiceNow does not automatically update the Risk or Impact fields on the change request.

The purpose of Conflict Detection is to identify whether another change is already scheduled for the same CI (or related CIs) during the same implementation window. For example, if a change is created for the CI  e.g ServiceNow1, Conflict Detection checks whether another active change already exists for ServiceNow1 at the same time.

If a conflicting change is found, the change manager or implementer must review the existing change, including its Risk and Impact assessment, to determine whether both changes can be deployed simultaneously or whether one of them should be rescheduled. This evaluation is a manual decision; Conflict Detection only identifies the scheduling conflict and does not calculate or modify the Risk or Impact values automatically.