Characteristic Exclusion Conflict 

Definition

A conflict that results from the exclusion of a characteristic with a set value. This applies to characteristics that can receive a value only under certain conditions (defined by the dependency). If such a characteristic first receives a value and is subsequently excluded during configuration, a characteristic exclusion conflict occurs.

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_NIL_VALUE

·        Creation of a list of all set values involved in the conflict and their origin

·        Provided that the dependency set the value involved in the conflict, delivery of the explanation text maintained for the dependency

·        Provided that the dependency caused the characteristic 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).

If you select the option for configuring a printer together with the computer, a characteristic is available that you can use to define the printer type. Once you have selected a printer type, you undo the printer option during configuration, thereby causing the conflict.

Causing the Conflict

       1.      Default setting: The characteristic Printer is set to value No. Therefore, the value Printer Type is made invisible by the dependency vis_printer_type and cannot be set to any value.

       2.      User selection: Printer → Yes

       3.      The dependencies pre_printer and sel_printer make the characteristic Printer Type visible and a value can be set for it.

       4.      User selection: Printer Type → Laser Printer (Color)

       5.      User selection: Printer → No

       6.      The dependency vis_printer_type makes the characteristic Printer Typeinvisible and allows no values to be set for it.

       7.      A conflict occurs for the Printer Typecharacteristic: A value has been set for a characteristic during configuration although this procedure is currently locked.

Conflict Explanation

·        Technical name: CONFLICT_NIL_VALUE

·         Long text that is maintained for the dependency pre_printer: You can select a printer type only after you set a printer.

Conflict Solution

Assignment of a name for the characteristic value that the user set for the characteristic Printer Type that can receive a value only under certain circumstances – a characteristic that was excluded during further configuration: Laser Printer (Color)

Constraints

The Configuration Engine does not deliver the characteristic value Printer → No. The reason for this is that the conflict is based on a classical precondition. Only that characteristic is displayed, to which the precondition is assigned.