Blackout schedule should be detected with change request source without selection of CI

[Kajal Ahire]

Currently, conflict detection in our ServiceNow instance for Change Requests is based on the following criteria: 1. Planned start date (start_date)
2. Planned end date (end_date)
3. 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 planned end date, ignoring the CI . If this is possible, could you please advise where and how to modify this logic (script, system property , business rule, etc.) to achieve this behavior?

The blackout and maintenance schedules are ultimately based on the Configuration Item. however I want that it should work without the selection of CI on change request.

[Tanushree Maiti]

Hi @Kajal Ahire , 

It is not feasible to modify the existing attributes of the change request conflict detector.

Refer this community post : Modify Change Conflict Detection Configuration 

where ServiceNow support has confirmed the same.