Return to main navigation Page
Configuration is defined on the catalog hierarchy in CPQ Cloud. For more information on the catalog hierarchy, see Product Family Hierarchy.
Catalog items contain regular attributes that cannot be modified at run time and configurable attributes that can be modified at run time. Configurable attributes can be created at all levels of the catalog hierarchy.
Using Configuration, the buyer can customize the items they are buying by specifying the values of configurable attributes.
Situations Appropriate for Rules
- Guided Selection: This is the process
of guiding a user through a series of questions to help them search for
one or more product line(s) within a product family or search for one or
more model(s) within product line(s). This is similar to selecting a
notebook model from a list of available brands.
- Configuration: This is the process of
allowing users to customize a model to suit their needs. This is much
like configuring a basic notebook computer by adding extra RAM, more
hard disk space, warranty services, and so on. Some options may increase
cost (pricing rules) and others options may not be possible
(constraints) like getting a 3 month warranty with your model.
Types of Rules
user experience in configuration is controlled by the ability to fire
the appropriate rules based on user input. Different types of rules
enhance the selection and configuration experience:
- Recommendations: Inform the user about recommended choices--or mandatory selections--based on their selections.
- Constraints: Prevent the user from making certain choices.
- Recommended Items: Up-sell products to the user.
- Pricing: Pass on area discounts, customization costs, and other overhead to the user.
- Flows: Lay out attributes on the Configuration pages so users are able to easily navigate and configure the selected models.
- Avoid using case sensitive text for displayed information or rule conditions (for example, part numbers).
- Use Auto Updates sparingly.
- Combine Configuration Rules when possible; separate Rules are more difficult to maintain and debug.
- Keep Rules on the same level, so they are
easier to maintain and debug. Avoid overriding menu attributes at lower
levels in the product hierarchy.
- Add relevant comments to explain specific design decisions.
- Avoid using custom templates.
- Create folders to organize your Data Tables.
A user cannot create or add Quotes from Configuration to Commerce if mandatory items are missing.
NULL and blank Integer values are treated as separate values.
- NULL= 0
- Blank = ""
If you use logic that tests for NULL values in rule conditions or BML, this logic should be updated.
Using "null" as an attribute value is strongly discouraged.