Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property determines whether conflicts are consolidated based on unique combinations of conflict type and schedule, reducing redundancy in conflict registration. |
| What area does it affect? |
Change Management |
| What does the default mean? |
The default value is "true", which means this behavior is enabled by default. |
| When should you review it? |
Review this property when adjusting conflict handling strategies or during major change process updates. |
Out of the box property record
Raw metadata from the property record.
| Property name |
change.conflict.consolidated_conflicts |
| Sys ID |
895853b7737200108ef62d2b04f6a7c8 |
| Type |
boolean |
| Application |
Global |
| Default value |
true |
| Description |
Consolidate conflicts so a conflict is only registered for each unique combination of conflict type and schedule or conflicting-change. |
| Updated |
2024-05-25 03:53:58 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... the conflict message. • Never: Conflict messages are not displayed. By default, User Preference is selected. change.conflict.allow_contiguous_changes Handles contiguous change requests with overlapping schedules. This property is active by default. change.conflict.consolidated_conflicts Displays only conflicts that result from a combination of the conflict type and schedule or conflict type and conflicting change. This property is active by default. change.conflict.max_count The maximum number ...
Related properties