Value Exclusion Conflict

Definition

A conflict that results from the exclusion of a characteristic with a set value. Both the setting and the exclusion of a characteristic for which a value has already been set can have been made manually or by a dependency.

Information

By determining and analyzing the configuration conflict, the Configuration Engine can provide information about the conflict and possible actions you can take to resolve it.

Conflict Explanation

  • Delivery of the technical name for identifying the characteristic exclusion conflict: CONFLICT_EXCLUDED_VALUE

  • Name of the excluded characteristic value and the origin of the set value

  • Provided that a dependency set the value, delivery of the explanation text maintained for the dependency

  • Provided that the dependency caused the value exclusion, delivery of the explanation text maintained for the dependency

Conflict Solution

Creation of a list of the characteristic values that were set by the user and caused the conflict.

Example

A configurable computer (see Typical Product Model ).

The conflict is caused by an unfulfilled precondition for a characteristic value: The application software Standard can be used only in connection with an operating system of type A (A1-A3) .

Causing the Conflict

  1. User selection: Start of the navigation path Application Software Next navigation step Standard End of the navigation path

  2. User selection: Start of the navigation path Operating System Next navigation step Operating System B End of the navigation path

  3. The dependency pre_not_OpSys_B excludes the previously set value Application Software: Standard .

Conflict Explanation

  • Technical name: CONFLICT_ EXCLUDED_VALUE

  • Long text that is maintained for the dependency pre_not_OpSys_B : The standard software is not compatible with the operating system B.

Conflict Solution
Name of the characteristic value that was set by the user but was excluded during the subsequent configuration process:Application SoftwareStandard.
Constraints

The Configuration Engine does not deliver the characteristic value Start of the navigation path Operating System Next navigation step Operating System B End of the navigation path . The reason for this is that the conflict is based on a classical precondition. In this case, only the characteristic to which the precondition is assigned is taken into consideration.