Configuration Constraint Rules

Overview

What Are They?

Constraint rules are used to let the user know which values are and are not allowed to be selected in a particular configuration. While a constraint is active, the user can not advance to commerce.

How Do They Work?

A constraint rule has a condition and an action. You can choose attribute values for the condition, which will when true, will trigger an action to be performed. Similarly, you can select action attribute(s) values that can be constrained or allowed. You can also enter a message that alerts the user that the configuration cannot have the selected set-up. The rule becomes inactive when the buyer re-selects values that are appropriate for either the action or condition attribute(s). Constraint actions can be defined as simple-action or table-based actions.

ClosedMultiple Constraint Rules on the Same Action Attribute

In the case of multiple constraints defined on the same action attribute, the rules are first ordered using the following criteria (in sequence):

  1. Descending order by product hierarchy (model-level first and all-product family level last)
  2. Descending order by number of rule inputs (rules with single-inputs fire first)
  3. Ascending order by order number

The sorted rules are then applied on after the other to display the constraint messages in sequence.

ClosedConstraints and Recommendations

Constraints and recommendations can be applied together.

Constraints are applied to all the attributes, followed by recommendations and then constraints will be run again.

The constraints are applied in two passes. The first pass to apply constraints determines the constrained action attributes to which the application of recommendations (if any) is skipped.

The recommendations are applied to only non-constrained action attributes. Constraints are run a second time to determine if any new constraints may have been triggered as a result of running the recommendations. So when the end-user makes changes to the attributes which are constrained and updates the configuration, new recommendations which were not run earlier (due to the earlier constraints) will also run which might trigger new constraints which are caught by the second pass of constraint application.

ClosedAJAX Constraint Rules

Constraint rules can run through AJAX resulting in faster performance and a dynamic user experience in configuration.

AJAX can be enabled for any constraint or hiding configuration rule. Unlike other rules, that are evaluated only if the attributes are set to auto update or if a user clicks the Update action, AJAX rules are evaluated and the action is performed instantly when a user changes any rule input. Input can be condition and action attributes or action inputs. AJAX rules are re-run when a user clicks the Update button.

Notes:

  • Constraint rule functionality will remain the same with AJAX. AJAX rules will support advanced condition and actions, table-based rules, and reverse constraint behavior. The exception to this are rules that have arrays as condition/action attributes or action inputs. AJAX constraint rules do not automatically hide the Pricing and Recommended Item sections when the user selects a constrained value. If the user performs an Update action, then these additional sections will be hidden. Also, constraint messages that are displayed below the main content when constraints exist in some other tab are not removed via AJAX.
  • Recommendation messages will appear/disappear via AJAX for attributes that are inputs/action attributes of AJAX rules. It should be noted that this does not imply that recommendation rules are fired by AJAX. Recommendation rules will only be fired when the user performs an Update action. However, if a recommendation rule has already fired on an attribute and that attribute is a part of an AJAX rule, then the recommendation value setting and messages will occur via AJAX.
End-User Interaction

With AJAX rules, the end user will experience a faster, more dynamic Model Configuration page.

AVP (Attribute Value Pricing ) will not automatically update is the user selects a constrained value that is constrained through an AJAX rule. Users will see the correct pricing upon performing an Update action.

Administration

ClosedCreating a Constraint Rule

  1. ClosedNavigate to Admin > Catalog Definition.

  2. Select Product Families in the Navigation column, and click List.

  1. For the Product Family for which you want to create a Constraint rule, select Constraints in the Navigation column and click List.

  1. Click Add to create a new rule.

  2. Enter the rule ClosedProperties.

    This section is where you will enter basic details about the rule. For example, the name, status and where it will be applied.

    Configuration Rule Basic Details

  3. Select the rule ClosedConditions.

    Configuration rule Condition section

    The condition section allows you to select the logic that specifies when a rule should run. There are three options: Always True, Simple Condition and Advanced Condition.

    • Always True: The rule will fire automatically, every time, because a specific condition does not need to be met.
    • Simple Condition: The rule will fire based on define condition attribute values that you select from a menu.

    • Advanced Condition: The rule will fire based on an advanced function written with BML.

      Conditions are returned as Boolean.

    ClosedConfiguration Context Attribute

    Beginning in Oracle CPQ 24B the Config Operation Context (_config_operation_context) configuration system attribute can be used to identify the operation that initiated the current Configuration session. This read only system attribute will reflect unique values for new configurations, reconfigurations, search flows, and ABO Modify actions.

    The Config Operation Context system attribute is available for use in all Configuration Rule type conditions and in BML advanced conditions and/or actions. For example, when a Config Operation Context attribute is selected in a simple condition, the possible values (new, reconfigure, modify_asset, and search_flow) can be selected in the Values drop-down.

    Config Context Attributes

    The Config Operations Context attribute can be used in Configuration Rules to allow Administrators to better manage the configuration experience if necessary. For example, if an administrator would like to define a rule that should only execute for a new configuration, or resulting from a modify asset action, they can use this new attribute to control execution.

  4. Choose to apply the rule to either Configuration, Selection, or Both. Configuration is the default selection.
  5. Choose the Action Type: 
    1. Standard:  Use the UI to add attributes to constrain or allow.
    2. Table Lookup:  Select values to constrain or allow from a Data Table. See the topic Table-Based Rules for more information
  6. Click Add Attributes to open the Action Attribute window.

  7. Select attributes from the Attributes dialog box and click Add.

    Attributes dialog

  8.  Select the values to constrain:

    ClosedConstrain All

    1. Check Constrain All.

    2. Select the Override Constrained Values Display option.

      The Constrained Values Display Override is only available for the JET Configuration UI.

      • No Override: Constrained attribute values are define by the attribute options.

      • Disabled: Constrained attribute values will be disabled.

      • Removed: Constrained attribute values will be removed from the menu.

      • Normal: Constrained attribute values will appear in menus without being marked.

      • Strike Through: Constrained attribute values will be struck through (i.e. crossed out).

        The Strike Through option is not available for Image Menus.

    ClosedSelected Values

    • Leave Constrain All unchecked.

    •  Select the Constraint Behavior:
      • Do not allow selected values (constrain)
      • Only allow selected values (allow or reverse constraint)

    • Check the applicable menu items from the Select Values drop-down.

    • Select the Override Constrained Values Display option.

      The Constrained Values Display Override is only available for the JET Configuration UI.

      • No Override: Constrained attribute values are define by the attribute options.

      • Disabled: Constrained attribute values will be disabled.

      • Removed: Constrained attribute values will be removed from the menu.

      • Normal: Constrained attribute values will appear in menus without being marked.

      • Strike Through: Constrained attribute values will be struck through (i.e. crossed out).

        The Strike Through option is not available for Image Menus.

  9. Type a message in the Static Text box or click Define BML Function to create a dynamic message.

    This message displays to the users only when the rule is run.

  10. Click Update and Back to save and return to the Constraint: Rules List page.

 

Uses Case

ClosedOverride Constrained Value Display

Customers can constrain the same Configurable Attribute differently depending on different conditions. Administrators can override the "Constrained Value Display" option defined in single select and multi-select menu-type configurable attributes within the action area of a constraint rule. For example, a customer has two constraint rules that have different Override Constrained Values Display options. The first constraint rule has the Override Constrained Values Display set to Disabled for "Sports" and "Luxury" vehicle values when the "Outright SUV buy" option is selected.

Constraint Rule with Override

When a sales user chooses the "Outright SUV buy" option, the Sports and Luxury options are grayed out (i.e. disabled).

Disabled Menu Item Selections

The second constraint rule has the Override Constrained Values Display set to Normal and user message displayed for the "Luxury" vehicle value when the "SUV Lease" option is selected and the "Expense Limit" is less than $1000.

Constraint Rule with Override

When a sales user chooses the "SUV Lease" option, sets the "Expense Limit to $500, and selects the Luxury option, the option appears normal, but the vehicle options are outlined in red to indicate an error and the defined error message is displayed.

Menu Item Selection with Warning

The Constrained Value Display Override is applied from the last constraint rule executed on the attribute. The order is defined by the order of the rules on the Constraint: Rules List page.

 

Notes

Notes:

  • AJAX Rules are supported on Search Flow and Model Configuration pages.

  • AJAX Rule with fewer action attributes - AJAX rules update the page using JavaScript post page loads. Because of this, it is important to limit the number of attributes affected per AJAX call.

  • If an AJAX rule fails to evaluate properly, the action will be timed out for 2 minutes. The end user can continue to interact with the page after that.

  • AJAX Rule without SOAP/ Table Queries – AJAX rules are not recommended to be used on rules with a large amount of BML, SOAP calls, or table queries as it could adversely impact performance and hence, end user experience.

  • AJAX rules are not supported for the default wizard.

Related Topics

Related Topics Link IconSee Also