Skip to main content

Table of Contents

Trigger strategy


Only available versions of this content are shown in the dropdown

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

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:
Issue Group Trigger strategy name Example
All issues All groups Trigger_NBA_TopLevel
<Issue> All groups Trigger_H_NBA_<Issue> Trigger_H_NBA_Acquisition
<Issue> <Group> Trigger_NBA_<Issue>_<Group> Trigger_H_NBA_Acquisition_Bundle

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, where each Subscriber may have multiple Devices, for example, for a Communications application. Note that this example is for all issues and all groups.

The Trigger strategy
Three context levels is the most complex configuration available for the Context Dictionary. Most NBA Trigger strategies are simpler than the above example.

The high-level logic flow is as follows:

  • Import actions
  • Evaluate All Actions engagement policies for all action contexts
  • Identify Authorized Contacts
  • Split actions into a separate stream for each action context
  • Evaluate the context level engagement policies
  • Execute the NBA Strategy Framework separately for each context
  • Merge all context streams
  • Apply final action limits and bundling options

The arrangement of Switch rules around the All Actions engagement policy sub-strategies immediately after the action import is only required if the primary context is not the top-level context. Its purpose is to execute the engagement policy within the primary context if the Trigger strategy is being executed as part of a simulation, otherwise it is executed in the top-level context.

The Set Primary Contact shape sets the following properties:

  • IsPrimaryContact - set to true if the contact is identified as an Authorized Contact
  • OriginalSubjectID - set to pySubjectID
  • OriginalContactID - set to pySubjectID
  • Import Actions strategy

    The actual strategy used for importing actions depends on the trigger strategy as described in the table below.

  • Authorized Contact strategy

    This strategy is provided as an empty canvas as shown below. In an implementation where there is a concept of an authorized or primary contact where some actions may only be delivered to such a contact (for example, head of household or primary account holder), it should be modified to include logic to identify such contacts.

  • Engagement Policy strategies

    Engagement policies are implemented through a series of Proposition Filters, one for each of the Eligibility, Applicability and Suitability conditions - in that order - contained in a sub-strategy.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us