Skip to main content

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

Updating Next-Best-Action Designer version 2 to support multilevel configurations

Updated on August 4, 2022

If you already used Next-Best-Action Designer version 2 in versions of Pega Customer Decision Hub earlier than 8.5, after upgrading to Pega Customer Decision Hub 8.5, you must update your Next-Best-Action Designer configuration to support multilevel decisioning.

Pega Customer Decision Hub
When planning the update, consider the various environments that you may have in your pipeline. First do the update in a single environment, in a dedicated, unlocked upgrade ruleset version, and then migrate all the rule changes to other environments in the pipeline.
  1. Ensure that no next-best-action outbound runs are active at moment and that no runs are planned for the same time frame as the Next-Best-Action Designer upgrade.
    Note: The upgrade can take 30-45 minutes.
  2. Ensure that no inbound requests, such as real-time event and real-time container requests, are planned for the same time frame as the Next-Best-Action Designer upgrade.
  3. Ensure that the Context Dictionary configuration is saved and valid.
  4. Ensure that the ruleset and version used by your access group are unlocked, or create an unlocked version of the ruleset. By default, the ruleset used to store the configuration is Artifacts.
  5. Optional: Check in all checked-out artifacts related to Next-Best-Action Designer to avoid potential issues during the upgrade.
  6. Optional: Lock and roll the Artifacts ruleset version. For more information, see
  7. Click Update now.
What to do next: After the update, when viewing an engagement policy in Next-Best-Action Designer, you may see a message stating that the backing strategy has been updated manually, as in the following figure:
Example engagement policy message
Example engagement policy message

The message does not indicate an error and can be safely ignored. To remove the message, you can edit the engagement policy and save it without making any changes.

  • Previous topic Migrating Next-Best-Action Designer from version 1 to version 2
  • Next topic Importing Next-Best-Action settings from a template

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