Conflict Handling
A configuration conflict is an inconsistency in the configuration process of a configurable product; a contradiction that arises during the configuration process. For more information, see Configuration Conflict and Conflict Types.
Example
When configuring a car for example, a conflict arises if you select a sunroof for a convertible.
As a rule, configuration models should be constructed with no conflicts. However, this may be difficult or even impossible to do. Sometimes, it may even be advantageous to allow a conflict and use it to explain to the user of the interactive configuration in detail, why certain product options (characteristic values) are incompatible, and thus provide the user with more information about the configurable product.
You have activated conflict handling in Extended Configuration Management (XCM), using the parameter conflicthandling.show
.
The product in the available product model must be of type product that is easy to configure.
The dependency that is used here relates exclusively to the header product. You may use dependencies that copy characteristics to class node components.
Selection of components via dependencies and procedural dependencies is not used.
If there is a conflict during interactive configuration, the characteristic values and characteristics that lead to the conflict are selected. You can:
Manually change values; this is meant for experienced users who know the product model and therefore know which values must be set differently to result in a consistent configuration.
Reset the whole configuration to its initial status
Search for product variants, that is, for consistently pre-configured products with a similar but consistent rating
Cancel configuration, without saving
Save the current configuration status (including inconsistencies). In this case, the conflict must be resolved at a later time.
Use the offered conflict handling shortcut, a recommendation of how to quickly resolve the conflict (see below)
Navigate to detailed conflict handling (see below)
Note
The availability of these options depends on whether the corresponding functions have been activated in Extended Configuration Management (XCM).
In certain conflicts, the configuration screen can offer a conflict handling shortcut, which recommends that the user accepts an automatically set characteristic value instead of a characteristic value selected by the user. If the user accepts this proposal, the conflict is immediately resolved and the configuration can proceed without a screen change.
The conflict handling shortcut contains the following information:
Name of the conflicting characteristic
Characteristic values that caused the existing conflict
Recommendation for resolving the conflict (allowing the characteristic inferred by the system)
Link to a fast solution of the conflict
Link to detailed conflict handling
The conflicts that occur are analyzed in two different ways: syntactically and semantically. For this reason, the screen consists of multiple parts that display the current evaluation, as well as the results from the two conflict analyses.
Conflict explanation
This area displays the result from the syntactical analysis. Conflicts can occur simultaneously for several characteristics. For each conflicting characteristic, the following information is displayed:
Name of the conflicting characteristic
Static text for the type of conflict that occurred and additional information, if there is any:
Explanations that were entered for the dependency involved. These explanations can be switched on and off.
The characteristic values involved in the conflict, or their descriptions
The structure of this area depends on the respective conflict type.
One characteristic may cause several conflicts simultaneously. The conflict descriptions for a characteristic are grouped by conflict type.
Conflict resolution
This area displays the result from the semantic analysis. You can use one or more deselection lists to deselect the characteristic values (user selection or default values) that cause a conflict. Solution probabilities help you with the decision.
After deselecting a characteristic value, the configuration is automatically rechecked.
If other characteristic values are in conflict, they are displayed and you are prompted to reset other entries.
If the conflict is resolved, you automatically return to the configuration screen.