Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Optional post-update tasks for default extension strategy rules

Updated on January 5, 2022

If you use the out-of-the-box extension strategy rules and supporting decisions in your application, review the below optional post-upgrade tasks and perform the ones that apply to your application.

Pega Next-Best-Action Advisor Update Guide

Changes to static (advertised) bundles

Pega Next-Best-Action Advisor 8.7 calls the static (advertised) bundle strategy logic only once, for the Account context. Previous versions called it multiple times, for each Subscription context.

If your Pega Next-Best-Action Advisor application displays the advertised bundles in the Refine or Compare screen, and you have defined a multilevel customer context structure (for example, multiple Subscriptions for an Account context), you must modify your static bundle logic to process all the Subscriptions on the Account, as shown in the following figure:

Sample multilevel configuration for static bundle logic
Screenshot of a sample multilevel configuration for static bundle logic

As different Subscriptions may have the same bundle, ensure any duplicate bundles are filtered out, as in the following example:

Filtering out duplicate bundles
Screenshot of the group by properties to filter out duplicate bundles

Changes to channel processing in Pega Next-Best-Action Advisor

Pega Next-Best-Action Advisor 8.7 requires the Subscriptions cart items to be considered in the prioritization of the retention offers shown. If you have defined a multilevel customer context structure for your Pega Next-Best-Action Advisor application, in the Bundling channel processing strategy, add the following data join to determine the right Subscription for the Account when selecting the cart items:

Properties of the Join Cart Members data join
Screenshot of the data join required to join the component with cart members

Connect the data join shape to the Prioritize Cart Members Set Property shape, as in the following figure:

Join Cart Members data join on the strategy canvas
Screenshot of the strategy canvas with the new data join shape

Finally, in the Prioritize Cart Members Set Property shape, set the .CartMembers property to @if(.TempString1 == "", .CartMembers, .TempString1), and set the .Priority property to @String.contains(.CartMembers, .pyName)?100:.Priority.

Changes to Q&A weighting

In Pega Next-Best-Action Advisor 8.7, the influence of the Offer weighting is weighted differently than in version 8.6. If your Pega Next-Best-Action Advisor application uses the Refine screen to influence the offers, in the ApplyQnAWeightage strategy, multiply the .OfferWeightage property by 1000, as in the following figure:

Setting the .OfferWeightage property
A screenshot showing the OfferWeightage property multiplied by 1000

Changes to time-bound decay levers

The time-bound decay levers functionality of Pega Next-Best-Action Advisor is disabled by default in Pega Next-Best-Action Advisor. To re-enable the functionality, do the following steps:

  1. Open the BusinessControlSettings decision data rule in the Data-Decision-Request-Customer class.
  2. In the BusinessControlSettings decision data rule, open the Outcome weighting record.
  3. Set the value of the Outcome weighting record to true.
  4. Save and check in your changes.
Note: The priority calculation formula has been changed to include business value of the action. If the business value is empty, it defaults to a value of 1. Ensure that the business value for the action is set appropriately.
    • Previous topic Optional: Enabling generic operator accounts for the Pega Next-Best-Action Advisor sample application
    • Next topic Setting the version number of your built-on application

    Have a question? Get answers now.

    Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us