Customizing Conflict Detection Logic for Change Requests

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!