The self-pivot feature controls business rules where the trigger and target of the business rule contain one or more identical dimension values.

When enabled, self-pivot allows a business rule to fire even if the user navigates to a location which explicitly contains a dimension value already in the rule target. For example, if a rule is defined as:

And a user navigates to Wine Type > Red, Region > Napa, the rule still fires, despite the fact that the user is already viewing a results list for wines from the Napa region.

When self-pivot is disabled for a rule, the rule does not fire if its targets contain the same dimension values as the user's navigation state. For example, if a rule is defined as:

And a user navigates to Wine Type > Red, Region > Napa, the rule does not fire because the user is already viewing a results list for wines from the Napa region.

Setting self-pivot to false does not necessarily remove all duplicates from search and merchandising results. For example, if a rule is defined as:

And a user navigates to Wine Type > Red, the user’s navigation state does not include a dimension value from the target and the rule fires. However, because the results list contains all red wines including those in the $10-$20 range, it is still possible to get duplicate results in the merchandising and search results list.

Self-pivot is enabled by default for each new rule created in Workbench, and the option is not displayed in Workbench. However, you can change the default and set the check box to display on the Triggers tab of the Rule Manager page in Oracle Commerce Workbench. Once the check box is available, you can change self-pivot settings separately for each rule. The option is still available for rules created or modified in Developer Studio; changing the default setting does not affect Developer Studio behavior.


Copyright © Legal Notices