Skip to main content


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

Trigger strategy

Updated on August 4, 2022

A trigger strategy is generated after you define a trigger within Next-Best-Action Designer and specify the business structure to apply. This strategy is referenced by a data flow, which is also generated and managed by the system.

Pega Customer Decision Hub
A separate trigger strategy is generated for each business structure specified as part of a trigger configuration and the strategies are named based on the business structure as shown in the following table:
IssueGroupTrigger strategy nameExample
All issuesAll groupsTrigger_NBA_TopLevel
<Issue>All groupsTrigger_H_NBA_<issue>Trigger_H_NBA_Retention
<Issue><Group>Trigger_H_NBA_<issue>_<group>Trigger_H_NBA_Retention_Cards

The layout of the strategy depends on the configuration of the context dictionary. The following example shows an implementation of multiple Subscribers within an Account, for example, for a Communications application. Note that this example is for all issues and all groups.

The Trigger strategy

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