Skip to main content

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

Extending the ActionTypeConfiguration and BudgetParameters decision data rules

Updated on October 7, 2021

The NBAAChannelProcessing strategy handles the processing of bundles by determining which actions make up the bundle, calculating the budget, and filtering out incompatible actions. The strategy is ready to use out of the box, but you can further extend it by configuring the available decision data rule extension points.

The NBAAChannelProcessing strategy contains the following extensible decision data rules:
  • ActionTypeConfiguration - Enables the selection of multiple actions from the same category.
  • BudgetParameters - Configures the budget parameters for Pega Next-Best-Action Advisor.

They are fully functional out of the box, but you can save the rule into your implementation layer and modify the logic if it is critically important to your business needs.

Note: In previous versions of Pega Customer Decision Hub, the ActionTypeConfiguration and BudgetParameters decision data rules were linked to the PegaComm-NBAMCFW-SR Strategy Result class. Starting from version 8.7, they reside in the Data-Decision-Request-Customer class. If you extended either of those rules in previous versions of your application, they are automatically migrated to the Data-Decision-Request-Customer class after the upgrade to version 8.7. Future updates to the decision data rules must be done in the version of the rule linked to the Data-Decision-Request-Customer class.
  • Previous topic Applying the Pega Next-Best-Action Advisor component
  • Next topic Configuring the maximum duration setting for Pega Next-Best-Action Advisor

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