Return to main navigation Page
Configuration Rule Overview
Rules enable you to set specific configuration information
for your products. For example, you can suggest configured values to
buyers using recommendation rules or hide some configurable attributes
from certain user types. Rules can also be used to recommend items to
buyers, prevent them from selecting opposite values of configurable
attributes and display additional price information.
Types of Configuration Rules
|Bill of Material (BOM)
||Builds a BOM string based on Configuration.
a user selects crust type = deep dish, a BOM string with sauce, cheese,
butter and type of dough is generated and returned to an
||Calculates a price based on how a product is configured.
||When a user configures a Model, the price is displayed based on the crust type, pizza size and topping selected.
||Hides attributes when a pre-defined condition is met.
||When a user selects pizza type = specialty, the toppings attribute is hidden.
||Sets items you would like the users to select OR items the users must select.
||When a user selects specialty pizza = Meat Lovers, the application recommends only pepperoni and sausage as toppings.
||Determines attributes values users cannot select within a Configuration.
||When a user selects pizza size = small, they cannot select Deep Dish as the crust type.
||Assigns parts and pricing to the Configuration, based on certain selections.
||When a user selects sandwich type = Hot, the application will return 4 recommended sandwich options.
Rules should always be created at the highest
level possible in the hierarchy, though they are available for creation
at any level.
Common Rule Elements
- Rules are created individually, at any level
in the system. (Except for search flows, which can only be created at
the Product Line level)
- Rules evaluate a certain condition and perform some action.
- Rules can be made active or inactive
- Rules abide by the principles of inheritance,
so rules created at a high level are automatically inherited by lower
levels. Usually, rules created at a lower level are given precedence
over rules created at a higher level.
- When more than one of the same rule type can
be triggered at the same time, the Configuration system evaluates which
rule to trigger based on rules precedence.
The values of the attributes selected as the
condition attribute(s) determines the results of the condition. If the
condition is evaluated as true, then the action is performed. The
action may involved action attributes.
The condition takes Configurable Attributes, Regular
Attributes, User Attributes and Account Attributes. The action uses
Ordering Configuration Attributes
Order the configuration attributes to set how they will appear in the document.
- Navigate to the Configurable Attributes Administration List page.
Click Admin to go to the Admin Home Page.
Click Catalog Definition in the Products section.
The Supported Products page appears.
In the Navigation column, select Configurable Attribute and then click List.
The Configurable Attributes Administration List page appears.
- Change the Order Number on the attribute you want to reorder.
- Click Update to save your changes.
The new attribute order displays on the Configurable Attributes Administration Listpage.
You can reorder individual attributes, including the individual attributes contained within an attribute set.
Order changes take effect after the
Configuration Product Family is deployed (or re-deployed). For more
information about deployment, see Setting Up Product Families.
Order of Operations: Rule Precedence
- Config Flow Rules
- Constraint Rules
- Recommendation Rules
- Constraint Rules (again)
- Hiding Rules
- Recommended Item Rules
- BOM Rules
Attribute Order & Rule Precedence
The attribute order affects rule order in the following ways:
- Config rules with "True" conditions are reviewed.
- The rules that reference the first Configurable attribute are run.
- The rules that reference the second Configurable attributes are run. Rules on subsequent attributes are run.
Order becomes important when there are dependent Recommendation Rules that need to be calculated in a specific sequence.
D is the sum of B and C; C = A*2. If C appears after D within the
Attribute List, D's calculation will use a stale value for C, resulting
in an incorrect value for D.
data entered on the Configuration page will be read before any rules
are run. The order of Configuration hierarchy inside of each of the
- Product Line
- Product Family
- All Product Families
Editing a Rule
- Navigate to the Rules List page for the required rule type at the appropriate level in the product hierarchy.
- Click the desired rule name on the Rules List page to launch the Rule Editor.
- Use the Rule Editor to change the Name, Description, Status and Condition Reference Type. You can also:
- Re-select condition and/or action attributes
- Specify different values for the condition attributes
- Edit actions
Deleting a Rule
- Navigate to the Rules List page for the appropriate rule type at the correct level in the product hierarchy.
- Select the rule to be deleted.
- Click Delete.
- Navigate to the Rules List page of the appropriate rule type at the desired level in the product hierarchy.
- Enter the desired order number in the Order column of the rule.
- Click Update. This will reorder the
rules list. The rule that occupied the selected position before the
reordering will now appear in the erstwhile position of the selected
Configuration Rules Default Row Grouping to "1"
When a user selects a “Simple Condition”
Configuration Rule Condition Type, a red error is not automatically
placed around the Row Grouping when the “Add Row” button” is clicked.
The red error appears when an Attribute value is entered into the row and a Row Grouping is not entered.
This occurs because the Row Grouping must default to 1.
- Once the user is finished implementing the row for a Simple Condition, the Conditional Summary will update.
If more rows are added, the user must manually edit the Row Grouping or use the “and all/or all” Quick Actions.
After creating rules, you can test their usage with a tool called the Pipeline Viewer.
you system has Configuration cache enabled, you must deploy the
Configuration in order to update the cache and enable your changes.
If you want to create and frequently test
Configuration rules without having to deploy the changes, contact your
System FullAccess user to temporarily disable the Configuration cache.