Hello @Jason Rooney
In the Change Request module, conflict detection is based on three primary factors: Configuration Item (CI), Planned Start Date, and Planned End Date. If a change request falls within the Planned Start Date and Planned End Date of another request for the same CI, it will be flagged as a conflict. By default (Out-Of-The-Box or OOB functionality), the system displays the message "CI Already Scheduled" for such conflicts.
To further enhance conflict management, you can create Blackout Schedules for specific servers. A Blackout Schedule allows you to define periods when changes should not occur for a given CI (e.g., servers). This ensures that planned changes are restricted during critical times, such as maintenance windows or peak usage hours.
Additionally, if you need to customize the conflict detection logic, you can extend the OOB Script Includes provided by ServiceNow. These Script Includes already handle conflict detection for CIs, but you can modify them to incorporate additional business rules or server-specific checks as per your requirements. For example, you might adjust the logic to prioritize server-specific conditions or integrate other criteria unique to your organizational needs.
By leveraging Blackout Schedules and tailoring the Script Includes, you can ensure that conflict detection aligns with your operational processes while maintaining flexibility for specialized requirements.
If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
Thank You
