Specifying which records to promote

You indicate which records to promote by specifying a target on the Target tab of the Rule editor.

A target is a collection of one or more dimension values. These dimension values identify a set of records that are all candidates for promotion. Zone and style settings further control the specific records that are promoted to a user.

To specify which records to promote:

  1. In the Rule editor for the rule you want to configure, click the Targets tab.
  2. Click Add. The Select Dimension Value dialog box displays.
  3. Select a dimension value from the list and click OK.
    Note: You cannot add auto-generated dimension values until you first load and promote the dimension values.
  4. If necessary, repeat the above steps to add multiple dimension values to the target.
  5. Check Augment Navigation State to add target dimension values to the existing navigation state when evaluating the rule. If not checked, the MDEX Engine ignores all current navigation state filters when evaluating the rule. Navigation state filters include dimension value selections, record search, range filters, and so on. The one exception is custom catalog filters, which always apply regardless of this setting. For example, if checked, and a user navigates to Wine Type > Red and that triggers a rule that promotes wines under $10, then the rule results will include only red wines that are under $10. The rule results are always a subset of the standard query results. Conversely, if Augment Navigation State is not checked, and a user navigates to Wine Type > Red which triggers a rule that promotes wines under $10, then the rules results will include any wine type (red, white, sparkling) with wines under $10. The rule results are not a subset of the standard query results.
  6. At this point, you can either:
    • Promote custom properties or featured records, or
    • Click OK if you are finished configuring the rule.
Note: Fully implementing this feature requires additional work outside of Developer Studio. Please refer to the Endeca Advanced Development Guide as well as the Endeca Workbench Help for details.