Enable automatic change conflict detection You can automate conflict detection to run at specific intervals or when a change request is updated. After automatic conflict detection is run, you can view conflict information in the Conflicts tab on the change request. Before you begin Prior to running conflict detection, you must consider the following scenarios unique to your organization. CMDB list size and relationship complexities If you are a large organization with a large CMDB, conflict detection can take longer to complete. Inactive changes are not evaluated Conflict detection does not evaluate inactive changes when determining conflicting changes. Advanced mode conflict checking is switched off by default When you upgrade, advanced mode conflict checking is switched off by default. Hence, affected CIs are not considered during conflict detection. To evaluate all the CIs, set the mode to Advanced. Role required: admin or change_manager Procedure Navigate to Change > Administration > Conflict Properties. Select only one of the following options. OptionDescription Run conflict detection automatically after changes to Configuration item, Planned start date, Planned end date, or State when a change request is updated When selected, runs conflict detection automatically when a change to one or more of the following fields is saved. Configuration item Planned start date Planned end date State Enable the scheduled change conflict checker When selected, runs the following conflict detection scheduled jobs at these intervals: Change Conflict Detection < 1 Week Away is scheduled every dayChange Conflict Detection < 1 Month Away is scheduled every two daysChange Conflict Detection >=1 Month Away is scheduled every seven days Click Save. You can view the conflicts in the Conflicts tab on the change request.
Enable automatic change conflict detection You can automate conflict detection to run at specific intervals or when a change request is updated. After automatic conflict detection is run, you can view conflict information in the Conflicts tab on the change request. Before you begin Prior to running conflict detection, you must consider the following scenarios unique to your organization. CMDB list size and relationship complexities If you are a large organization with a large CMDB, conflict detection can take longer to complete. Inactive changes are not evaluated Conflict detection does not evaluate inactive changes when determining conflicting changes. Advanced mode conflict checking is switched off by default When you upgrade, advanced mode conflict checking is switched off by default. Hence, affected CIs are not considered during conflict detection. To evaluate all the CIs, set the mode to Advanced. Role required: admin or change_manager Procedure Navigate to Change > Administration > Conflict Properties. Select only one of the following options. OptionDescription Run conflict detection automatically after changes to Configuration item, Planned start date, Planned end date, or State when a change request is updated When selected, runs conflict detection automatically when a change to one or more of the following fields is saved. Configuration item Planned start date Planned end date State Enable the scheduled change conflict checker When selected, runs the following conflict detection scheduled jobs at these intervals: Change Conflict Detection < 1 Week Away is scheduled every dayChange Conflict Detection < 1 Month Away is scheduled every two daysChange Conflict Detection >=1 Month Away is scheduled every seven days Click Save. You can view the conflicts in the Conflicts tab on the change request.
