Skip to main content


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

Understanding Next-Best-Action Designer channels

Updated on August 4, 2022

Next-Best-Action Designer comes with a full set of channels and triggers which are part of the strategy framework.

Pega Customer Decision Hub
Channels, triggers and events on the Channels tab
Channels

Channels can be toggled on or off. If a channel is toggled off, its status is stored in a decision data rule (DDR) and the related part of the strategy framework is turned off. Setting the toggle to on reactivates the related part of the strategy framework.

To add additional channels, edit the ChannelSettings DDR, and then implement these channels in the channel extension strategies within the framework. These custom channels appear under Other on the Treatment landing page. When creating a new Other treatment, you can specify the custom channel, and then pick the direction (inbound or outbound). On an Action rule, to use a custom channel, add the Other channel, and then pick the appropriate treatment.

Triggers

The Next-Best-Action strategy framework can be invoked by real-time channels through our Container REST API and Kafka event stream, as well as on a scheduled basis.

As you define one of these triggers, Next-Best-Action Designer generates a dataflow with a strategy based on the specified business structure. These generated dataflows can be seen on the Dataflows landing page if the View system generated flows setting is enabled.

  • Previous topic Understanding Next-Best-Action Designer arbitration
  • Next topic Understanding the Next-Best-Action strategy framework

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us