Skip to main content

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

NBA Strategy framework components: External Input through to Constraints

Updated on August 4, 2022

External input includes imported active actions that have already had individual group-level and All Group level engagement policies applied.

Pega Customer Decision Hub
Strategy components: external input, pre-processing, customer states, constraints

The figure below shows the whole strategy framework. The following sections describe individual components of the framework in more detail.

Pre-processing extension point

The first component within the strategy framework is an extension point named NBAPreProcessExtension that is used for any action pre-processing which you might need to perform.

Customer states

The CustomerStates strategy filters actions based on the customer's current journeys. This capability is a placeholder and will be implemented in a future release of Next-Best-Action Designer.


The Constraints strategy enforces any actions which need to be suppressed based on the associated contact policies. The strategy imports the suppression records, known as Action Insights, and filters out any groups or actions which have matching suppression records.

These constraints are only applied to non-transactional actions. Transactional actions are passed straight through.

Strategy components: external input, pre-processing, customer states, constraints
  • Previous topic NBA Strategy framework
  • Next topic NBA Strategy framework components: Action scoring through to control group handling

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