|Bookshelf Home | Contents | Index | PDF|
When you set the value of an attribute for a product, it cannot be changed by either the user, a configuration rule, or the eConfigurator engine. One example, is when you want to set an attribute value so that provide and consume rules can use it to add or subtract from a defined resource.
For example, you create an attribute called Slots Required for a product class containing expansion cards. Some cards take up one expansion slot; some take up two. You could define a list of values containing the integers 1 and 2 and make it the domain for Slots Required. For each expansion card you would then set the value of this attribute at 1 or 2. Users cannot change this value when configuring the product, and configuration rules cannot change this value.
You would then write a provide rule that increases a Slots Available resource when the user picks a chassis. For the expansion card class, you would write a consume rule that reduces Slots Available by the value of Slots Required, each time the user picks an expansion card. In this fashion, you use attribute values as constants that interact with a defined resource to manage a consumable configuration variable.
|Product Administration Guide|