Siebel Product Administration Guide > Configuration Constraints >

Guidelines for Creating Configuration Constraints


Consider the following guidelines when creating constraints:

  • If constraints are needed, create at least one constraint early in the process of building a product. The presence of a configuration constraint, even if it is inactive, causes Siebel Configurator to check the product for errors more rigorously when you go to validate mode.
  • Avoid writing constraints that use large quantities until you have verified the logic of the constraint. For example, write a constraint that refers 10 items and check it before changing the constraint to refer to 10,000 items. This prevents needless solution searches if the basic logic of the constraint is incorrect.
  • Test each constraint after you create it. Consider inactivating constraints that are unrelated to the new constraint to facilitate troubleshooting. Test constraints by starting a configuration session and selecting the affected items. To start a configuration session, from the Constraints List menu, select Validate.
  • If you are using asset-based ordering, you can minimize order problems if you avoid creating require rules that add items that are not tracked as assets to a customizable product. For example, you write a require rule that adds a one-time charge for Installation to a customizable product. You do not set the Track as Asset flag for Installation in its product record. This means Installation does not display as a customer asset. Then the customer requests an addition to the service. The call center agent selects the service, clicks Modify, and starts a configuration session. the Siebel Configurator engine adds Installation, because it is required by configuration rules. Installation is transferred to the quote even though it is not required by the service modification.
Siebel Product Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.