Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring next-best-action strategies for Pega Sales Automation 8.2

Updated on September 10, 2021

Pega Sales Automation™ uses Pega's Customer Decision Hub and Decision Management capabilities to identify the next best action for every sales opportunity.


Before you begin your configuration, ensure that the following conditions are met:

  • Pega Sales Automation is installed
  • Adaptive Decision Manager (ADM) and Decision Strategy Manager (DSM) services are running
  • The following services are running in the normal status:
    • Decision Data Store
    • Adaptive Decision Manager
    • Data Flow
    • Visual Business Director

Configuring next-best-action strategies

To configure next-best-action strategies for your Pega Sales Automation implementation, log in to the application and complete the following steps:

Creating propositions

  1. In the header of Dev Studio, click Configure > Decisioning > Decisions > Proposition Management.
  2. Click an existing issue, and then create a group that matches the scope of the next best action by clicking New Group.
  3. On the Decision Management form, create a new proposition for the issue by clicking New.
  4. On the Create proposition form, enter a name and description for the proposition, and then specify the DefaultRank.
  5. Click Create.
  6. Click Save as.

Creating data models

Any data model that is required for a new next best action must be created in the GivenSAOpp primary step page.
  1. In the navigation panel of Dev Studio, click Records > Data Model > Data Page, and then open the D_NBASalesRepOpp data page.
  2. On the Definition tab, in the Data Sources section, verify that the Source field is set to Activity and the Activity name field is set to NBASalesRepOpp.
  3. In the header of Dev Studio, search for and select the NBASalesRepOpp activity.

    The GivenSAOpp clipboard page is the primary step page that holds the required model data.

  4. Verify that the NBASalesRepOpp activity is set to call the NBASalesRepOpp data flow with the GivenSAOpp clipboard page.

    This ensures that the NBASalesRepOpp data flow calls the NextBestActionsForSalesRep strategy.

Creating strategies

  1. In the header of Dev Studio, click Crete menu > Decision > Strategy.
  2. Enter a label for the strategy.
  3. In the Strategy Results class section, select the business issue and group that you created for the proposition.
    The class of the strategy is the same as the class of the PageListProperty created for the GivenSAOpp clipboard page in the data model.
  4. Click Create and open.

To import components and define your strategy, complete the following steps:

Importing a Proposition Data component

  1. On the new Strategy form, in the toolbar, click the Strategy Shapes icon, and then click Import > Proposition Data.
  2. Open the Proposition Data component.
  3. In the Proposition data properties pop-up window, enter the name for the proposition.
  4. On the Interaction history tab, perform the following steps:
    1. Select the Enable interaction history check box.
    2. Set the Fetch interaction history for the lastvalue to 31 days.
    3. In the Fetch when the conditions below are metsection, click Add item.
    4. Set the Property field to .pyOutcome and the Value field to Clicked.
    5. In the Define which properties to use section, click Add item.
    6. Set the target to .pyOutcome and the interaction data to .pyOutcome.
    7. Click Submit.

Importing a Filter component

  1. On the new Strategy form, in the toolbar, click the Strategy Shapes icon, and then click Arbitration > Filter.
  2. Connect the Filter component to the Proposition Data component.
  3. Open the Filter component.
    1. In the Filter Properties pop-up window, enter the name for the filter.
    2. In the Filter condition field, enter .pyOutcome!="Clicked".
    3. Click Submit.
  4. Optional: To add a second component, perform steps 1-3 and connect this Filter component to the first Filter component that you created.
  5. Open the second Filter component and perform the following:
    1. In the Filter Properties dialog box, enter a name for the filter component.
    2. Select the Proposition filter check box and click Add.
    3. Complete the fields on the Create Proposition Filter form and click Create and open.
    4. To create a when rule to meet your requirements, on the Edit Proposition Filter form, in the Proposition evaluation section, select specific filter criteria and click Add when rule.
    5. Based on your requirements, add the next-best-action qualification filter conditions.
    6. Click Save.
  6. Click Submit.

Importing a Set Property component

  1. On the Strategy form, on the toolbar, click the + icon.
  2. To add a Set Property component, click Enrichment > Set Property.
  3. Connect the Set Property component to the Filter component that you created in the previous procedure.

    This component is now used to set the needed properties.

  4. Open the new Set Property component.
  5. In the Set Property Properties dialog box, enter a name for the property.
    The .pyLabel property has the text of the next-best-action (by default, it is the proposition description). If required, you can concatenate or modify the content of the .pyLabel property to create custom text for the next-best-action.
  6. Optional: Configure other properties, as needed.
  7. Click Submit.
  8. Add a result shape to the strategy rule and connect the Set Properties component with the Results component.
  9. Click Save.

Strategy Flow

A completed strategy flow

Configuring substrategies

  1. In the Dev Studio header search text field, search for and select the NextBestActionsForSalesRep strategy.
    This strategy is called from the data flow in the NBASalesRepOpp activity that is referred to in the data model setup step.
  2. To add a substrategy, on the toolbar, click the + icon, and then Sub strategy.
  3. Open the substrategy component and perform the following steps:
    1. Enter a name for the substrategy.
    2. Click External strategy and select Another page as a run strategy.
    3. In the Page field, enter the page list populated on the GivenSAOpp clipboard page.
    4. In the External strategy field, enter the strategy name.
  4. Click Submit.
  5. Optional: If the new next best action should be displayed only when an opportunity is open, then connect the new substrategy to the appropriate opportunities Filter component.
  6. Click Save.

Clearing interaction history

  1. Log in to Pega Sales Automation by using the credentials sfasamplesysadmin / install.
  2. Click Launch web interface > SFA for Sales Ops.
  3. In the navigation menu, click Tools.
  4. Click Reset NBAM Quadrant.
  5. Repeat steps 2 through 4 for the SFA for Sales Rep portal.

Troubleshooting configuration

  • You click an action to close it but the action is not removed from the Next Best Actions dashboard widget.
    • .pyOutcome is not mapped or it is missing from the Import component of the strategy.
    • The filter is not configured to remove the items that have an interaction history.
  • The Next Best Action dashboard widget displays only a few actions or no actions.
    • Clear the interaction history.
  • An exception occurs when using the strategy.
    • Verify that the properties you are using in the Proposition Filter and the when rules are set up to handle null values.
  • Previous topic Configuring next-best-action strategies for Pega Sales Automation 8.3
  • Next topic Configuring lead routing in Pega Sales Automation (8.3-8.4)

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