Optional post-update tasks for default extension strategy rules
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.
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:
As different Subscriptions may have the same bundle, ensure any duplicate bundles are
filtered out, as in the following example:
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:
Connect the data join shape to the Prioritize Cart Members Set
Property shape, as in the following figure:
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:
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:
- Open the BusinessControlSettings decision data rule in the Data-Decision-Request-Customer class.
- In the BusinessControlSettings decision data rule, open the Outcome weighting record.
- Set the value of the Outcome weighting record to true.
- Save and check in your changes.
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