top of page

Configuring the NBA_PostActionImportExtension Strategy for Next-Best-Action

In a Next-Best-Action (NBA) implementation, it is crucial to have the flexibility to modify or extend the behavior of the system in ways that suit specific business needs. One such mechanism is the use of extension points, which allow developers to introduce custom logic that can run at key points in the action selection process. The NBA_PostActionImportExtension strategy serves as a post-processing extension that ensures action data is prepared correctly before eligibility evaluations take place. This article will walk through the process of configuring this extension point strategy to work effectively with NBA systems.




Why Use the NBA_PostActionImportExtension?


In the NBA framework, there are predefined strategies like Trigger_NBA_TopLevel and Trigger_NBA__, which handle action selection based on engagement policies, decisioning logic, and user profiles. The NBA_PostActionImportExtension strategy is executed before these strategies, allowing custom data processing and additional logic to influence the engagement policies. This strategy ensures that post-import data is available and relevant for determining action eligibility.




Configuring the NBA_PostActionImportExtension Strategy


The configuration process for the NBA_PostActionImportExtension involves three main steps: creating and saving the extension point strategy, adding necessary properties, and passing those properties into the engagement policies for action eligibility.


Step 1: Save the NBA_PostActionImportExtension Strategy in the Application Ruleset


The first step is to define and save the NBA_PostActionImportExtension strategy in the application’s ruleset. This strategy should encapsulate any post-processing logic that is needed before the NBA engine evaluates action eligibility.


1. Open the Strategy Designer: In your application development environment, navigate to the strategy designer where you can define and edit decisioning strategies.


2. Define the Post-Processing Logic: Design the strategy to process the necessary data after an action import. For example, this could involve adjusting action parameters, calculating additional metrics, or preparing data for later use in engagement policies.


3. Save the Strategy: Ensure that the strategy is saved in the appropriate ruleset for your application. This makes the strategy reusable across the application.




Step 2: Add the Property in -SR Class


Once the post-processing strategy is in place, you need to ensure that the required properties are added to the application’s class structure. In this case, the property must be added to the -SR class, which is often a strategy result or action-related class.


1. Navigate to the SR Class: In your application, go to the class structure and find the -SR class. This is typically where context-specific properties are stored.


2. Create the Property: This property will store data generated by the post-action import process. For example, it might store a calculated score or additional metadata related to the action.


3. Set the added Property in the Strategy: Ensure that the added property is populated within the NBA_PostActionImportExtension strategy. This allows the data to be available when eligibility conditions are evaluated later.




Step 3: Pass the added Property to Eligibility Conditions


The final step is to make sure the added property is used as input to the action eligibility conditions. The NBA system evaluates actions based on a series of engagement policies, and the output from the post-action import process should influence this decision-making.


1. Open the Engagement Policies: In the NBA application, navigate to the engagement policies that govern action eligibility.


2. Use the added Property in Eligibility Conditions: Modify the eligibility conditions to include the plate property as an input. For example, if the adde property contains a calculated value that determines whether an action is relevant, it should be checked here.


3. Test the Integration: Ensure that the integration between the post-action import strategy and the engagement policies works correctly. This can be done by running tests and verifying that the added property’s value influences action selection as expected.




Execution Flow of the NBA_PostActionImportExtension Strategy


Here’s a summary of the execution flow when the NBA_PostActionImportExtension strategy is in place:


1. Action Import Occurs: Actions are imported into the NBA framework from external sources or are generated internally.


2. NBA_PostActionImportExtension Runs: The NBA_PostActionImportExtension strategy is triggered after the import. It processes the imported data and stores the result in the added property.


3. Engagement Policies Use Plate Property: The engagement policies evaluate the actions and determine their eligibility based on the property’s value


4. Trigger_NBA_TopLevel or Trigger_NBA__ Strategies Execute: These strategies evaluate the imported actions, using the data from the added property to make eligibility decisions.




Benefits of Using the NBA_PostActionImportExtension Strategy


The primary advantage of using the NBA_PostActionImportExtension strategy is the ability to introduce custom logic before eligibility conditions are evaluated. This flexibility can be critical in complex business environments where action selection must be finely tuned to business rules, customer data, or external factors.


- Customization: Introduce custom post-processing logic that tailors the action data to specific business needs.


- Data Preparation: Ensure that any data needed for engagement policies is ready before action eligibility is evaluated.


- Increased Control: Gain more control over how actions are evaluated and selected by incorporating custom properties and logic into the decision-making process.




Conclusion


Configuring the NBA_PostActionImportExtension strategy is a powerful way to extend and customize the action selection process in a Next-Best-Action framework. By implementing this extension point, adding necessary properties, and passing them to eligibility conditions, you ensure that the NBA system is well-equipped to handle complex business requirements. This configuration gives you the flexibility to tailor the NBA framework to your specific needs, providing more relevant and effective customer interactions.



--Team Enigma



0 views0 comments

Comments


bottom of page