Configuration Conflict
When products are configured using the Configuration Engine, configuration conflicts are reported if inconsistencies occur – for example, if during configuration of a car, the sunroof option is selected for a cabriolet. Certain configuration conflicts can be displayed together with further information with varying levels of detail.
You apply the configuration conflict tool to display inconsistencies in the configuration of a product.
Certain conflict types allow you to explain to the user the cause of the inconsistency and to propose solutions. For example, you can specifically allow configuration conflicts in the model structure to streamline the model and promote an understanding of the context together with more detailed information about the product.
If you want to use the configuration conflict as a modeling tool, you must observe the prerequisites for the application in which the Configuration Engine is used.
The Configuration Engine is always part of an application for product configuration and provides the application with certain information about a configuration conflict. On the screen, the application determines which conflict information is passed on to the user and how the information is displayed.
The function for analyzing conflicts and proposing solutions must be activated on the user interface of the application.
When a product is configured, the Configuration Engine recognizes different types of configuration conflicts.All types of configuration conflicts are designed to generate corresponding conflict explanations. These explanations must be created during the modeling process.
For tips and more information about using configuration conflicts, the analysis functions, and creating solution information, see
The product model must be a product that is easy to configure to ensure that the Configuration Engine is able to analyze the configuration conflicts and generate proposed solutions effectively.
The dependency used must relate to the root object of the product model only.