change.conflict.allow_contiguous_changes
ServiceNow property description:
When conflict checking for similar change requests (by Affected CIs or Assigned to) find records that overlap with the current change request only. Old behavior did not allow change requests that start at the same time as the end time of the current change request or a change request that ends at the same time as the start time of the current change request. As an example the following change requests apply to the same configuration item. CHG01, start: 2019-01-01 03:00:00 end: 2019-01-01 04:00:00. CHG02, start: 2019-01-01 04:00:00 end: 2019-01-01 05:00:00. If this property is set to true these contiguous change requests will not conflict, if the property is set to false they will conflict.
Attributes
- Sys ID: 444f6869532333008ef67c2c0fc5876d
- Type: true | false
- Application: Global
- Default value: true
AI generated property description:
The ServiceNow property `change.conflict.allow_contiguous_changes` determines whether changes that are scheduled back-to-back (contiguous) are allowed without being flagged as conflicts. When this property is enabled, the system permits changes to be scheduled immediately after one another without considering them as conflicting. This can be useful in scenarios where sequential changes are necessary and do not interfere with each other. The property can be configured in the Change Management settings under conflict properties. Adjusting this setting helps in managing and scheduling changes more flexibly, especially in environments where continuous changes are common.
Source