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.
|Issue||Group||Trigger strategy name||Example|
|All issues||All groups||Trigger_NBA_TopLevel|
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.
- NBA TopLevel strategy
This strategy combines references to the sub-strategies for each business issue defined in the next-best-action taxonomy. It is generated by Next-Best-Action Designer and is not modifiable. The example below is for a configuration with three business issues: Selling, Retention and Acquisition.
- Issue-level strategies
A separate strategy is generated for each issue in the taxonomy, each of which is included in the NBA_TopLevel strategy. These strategies are not modifiable.
- Group-level strategy
A group-level strategy is generated by Next-Best-Action Designer for each active group within your business structure. If a trigger is defined for all groups or issues, multiple group strategies are invoked.
- NBA_AllIssues_AllGroups Strategy
This is similar to a group-level strategy, but with no action import and without the all issue and group processing (which is this strategy). In this strategy the proposition filters contain only default conditions.