Customizing Conflict Detection Logic for Change Requests
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2025 07:35 AM
Hi everyone,
Currently, conflict detection in our ServiceNow instance for Change Requests is based on the following criteria:
Planned start date (start_date)
Planned end date (end_date)
Configuration Item (cmdb_ci)
I would like to know if it's possible to customize this logic so that conflict detection is based only on the planned start date and the CI, ignoring the planned end date.
If this is possible, could you please advise where and how to modify this logic (script, table, business rule, etc.) to achieve this behavior?
Thanks in advance for your help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2025 08:10 AM
Hi @Clement_V
Greetings!!
These settings are configured in Conflict Properties. You can check there. I doubt you can remove planned dates, but it’s better to review these properties.
https://INSTANCNAME.service-now.com/now/nav/ui/classic/params/target/system_properties_ui.do%3Fsysparm_title%3DChange%2520Management%2520Conflict%2520Analysis%2520Properties%26sysparm_category%3DChange%2520Collision
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
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
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************