|Bookshelf Home | Contents | Index | PDF|
When you define a relationship, you can specify a minimum, maximum, and default cardinality. Cardinality refers to the quantity of the products the user can select from a relationship. For example, you define a relationship called Hard Drives. It contains a 20 GB drive and a 30 GB drive. If you set the minimum cardinality to 2, the user must pick 2 items from this relationship. The user can do this in any of the following ways:
Table 18 describes several combinations for setting cardinality. The table shows what the user will see in the initial solution and what actions that the user can take. In the table, N is the quantity of the default product in the initial solution. In all the cases where the Min Card is greater than 0, the user can substitute other products for the default product.
Generics are notifications to the user from the engine that one or more items within a relationship needs to be selected for the customizable product to be correct. An example of generics is a red star displayed next to the relationship name and product title during a configuration session because some minimum cardinality requirements were not satisfied. The configurator gives users a warning when they try to save a configuration that has generics in it, but it allows users to save the configuration and also saves the fact that the configuration is incomplete to the quote or order.
When the user verifies a quote, the application checks for incomplete configurations as well as for other information. If the configuration saved was incomplete because of unsatisfied cardinalities on relationships, the application displays a message when the user verifies saying that the configuration of the item is not complete and the user should reconfigure the item.
|Product Administration Guide|