Skip to main content

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

Creating an External Input strategy to test the framework

Updated on September 15, 2022

Once the actions source is available, you can use this to replace the External Input in the NBA Strategy Framework.

Pega Customer Decision Hub
  1. In the Customer Decision Hub portal, click IntelligenceStrategies.
  2. Open the NBA Strategy Framework strategy.
  3. Click Save As and change the label to be the name of a new test strategy, for example, External Input Test.
  4. Ensure that [No branch] is selected in the Development branch field.
  5. Click Create and open.
  6. Right-click on an empty area of the canvas, and then click Disable external input.
  7. In the Input Disable Warning message, click Submit.
  8. Right-click to the left of the leftmost component in the strategy.
  9. Select Sub-strategyExternal.
  10. Double click on the new component.
  11. In the External strategy field, enter ExternalInputTest.
  12. Select Specify a single component within the strategy.
    Note: You may need to do this twice, since the first check is used to verify the strategy name.
  13. From the Component list, select the action context that you want to use for testing.
    Note: Because the framework is only ever executed for a single context at a time, it is highly recommended to use a single context when testing the framework. Select the context where you are seeing issues that you need to test. If required, you can change your selection later.
  14. Connect the new External Input Test shape to the Pre-processing extension point shape.
  15. Save and check in your changes.
Result: You have created a test strategy that can be used to test sub-strategies within the NBA Strategy Framework using a specific action context. If you need to test using a different context, you can either use the Save as option to create an alternative version, or you can check out the strategy, change the component referenced in the call to the External Input Test sub-strategy, and then save the changes for use during your tests.
Tip: It is recommended that you use the second method while you may still be making changes to the strategy. When the strategy is stable and you have no further changes to make, you can safely make one or more copies without having to keep updating the copies.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us