Change Conflict Detection should cease execution as soon as the tracker is cancelled - Known Error

Change Conflict Detection should cease execution as soon as the tracker is cancelled Description Conflict Detection is managed by an Execution Tracker, when the tracker is canceled either manually or because another conflict detection job is being triggered, conflict detection does not stop immediately.

Steps to Reproduce

Create a Normal/Emergency change request Set the configuration item field Set the planned start/end date fields (to a Wednesday if you have demo data for blackout schedules installed) Save the record Wait until conflict detection has executed and you have entries in the conflict tab Now, for this step you have to be ready to cancel the dialog as soon as it appears Click the "Check Conflicts" button in the Conflict tab - then click cancel on the dialog - it should say Conflict detection has been canceled Note, that the conflicts list should be empty and that the Conflict status field should say Not Run, and that the Conflict last run field is now empty

This is the challenging part! As it can be time consuming to create and setup data to slow conflict detection down, it is recommended that the line "gs.sleep(15000)" is added to the "ChangeCheckConflictsSNC" script-include, in the "_checkComposed" function, before the line "var saveTime = new Date().getTime();" Now, with this change, follow these steps:

Navigate back to the same change created before, where the status field is still set to Not Run Now click the "Check Conflicts" button in the Conflict tab - then wait a few seconds and click cancel on the dialog - it should say Conflict detection has been canceled However, if you now wait 15 seconds on the form, you will see that the Conflict status, Conflict last run fields are now being populated, and if you refresh the conflict tab you will see conflicts

Expected: When conflict detection is canceled, conflicts should not then be saved to the database if we were able to cancel the tracker in-time.

Workaround Load the attached ChangeCheckConflicts script-include that will override the "_checkComposed" and "checkAndUpdate" functions in ChangeCheckConflictsSNC.