Separate conflict detection

Bartek0301
Tera Contributor

Hello,

 

Can we build in ServiceNow a separate conflict detection engine?

 

For example:

Let's say I have four change requests - CR1, CR2, CR3, CR4.

CR1 and CR2 are created from custom model 1, CR3 and CR4 are created from custom model 2.

All changes are related to the same CI and their planned dates are the same.

However if I check the conflicts I want to see that CR1 is conflicting only with CR2 and CR3 is conflicting only with CR4.

I'm looking only for a technical solution, I know this is incorrect from the process side.

1 ACCEPTED SOLUTION

Dr Atul G- LNG
Tera Patron

Hi @Bartek0301 

 

There isn't an OOTB way to build a custom conflict check like the one you're describing. Out of the box, ServiceNow checks conflicts based on the CI, planned start date, planned end date, and other related change criteria.

What's new is that, starting with the Australia release  ServiceNow introduced a flag that lets you control whether a particular change should be considered during conflict detection or not. That feature might address your use case.

However, there is no OOTB capability to build the exact behavior you're looking for. It would require significant customization, which would introduce additional technical debt and increase long-term maintenance.

 

https://www.linkedin.com/posts/dratulgrover_this-scenario-has-come-up-multiple-times-share-745417305...

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG

****************************************************************************************************************

View solution in original post

2 REPLIES 2

Dr Atul G- LNG
Tera Patron

Hi @Bartek0301 

 

There isn't an OOTB way to build a custom conflict check like the one you're describing. Out of the box, ServiceNow checks conflicts based on the CI, planned start date, planned end date, and other related change criteria.

What's new is that, starting with the Australia release  ServiceNow introduced a flag that lets you control whether a particular change should be considered during conflict detection or not. That feature might address your use case.

However, there is no OOTB capability to build the exact behavior you're looking for. It would require significant customization, which would introduce additional technical debt and increase long-term maintenance.

 

https://www.linkedin.com/posts/dratulgrover_this-scenario-has-come-up-multiple-times-share-745417305...

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG

****************************************************************************************************************

I'm aware of this feature however it's entirely excluding change request from conflict analyze so it doesn't fully cover the scenario. But thank you for confirmation.