OOB Change request conflict detection for affected/impacted cis is not working

[RC19]

Hi All,

OOB change request conflict detection for Affected CIs/Impacted CIs is not working even when relevant/all properties in conflict properties page are enabled. After i add some cis into affected cis and impacted services related lists and even if they have maintenance windows, I don't see conflict is getting detected. it is only getting detected for configuration item field. can you please help. 

[Dr Atul G- LNG]

Hi @RC19 

Please check the conflict properties:

[RC19]

Hi Atul,

I did check by enabling relevant properties and also by enabling all properties but no luck. it is not detecting the conflicts for the cis on affected cis/impacted services related lists.

[Dr Atul G- LNG]

I found something that could help. Could you please check the property change.conflict.mode and set it to Advanced? also Check that change.conflict.populateimpactedcis and change.refresh_impacted.include_affected_cis are active

If it is already set to Advanced and it is still not working, we may need to log a case with ServiceNow Support, as this is an OOTB functionality.

 else try Manual Refresh Action: Use the form context menu to select Refresh Impacted Services or re-trigger Check Conflicts after adding rows, as manual inserts into related lists do not always auto-spawn records in the change_conflict table until explicitly evaluated