Skip to main content

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

Upgrading Pega 1:1 Operations Manager

Updated on December 20, 2021

This content applies only to On-premises and Client-managed cloud environments

After upgrading your Pega Customer Decision Hub application, update Pega 1:1 Operations Manager.

Pega Customer Decision Hub Update Guide
  1. In your Business Operations environment, create a new unlocked ruleset.
  2. Configure the operator access groups in your Business Operations environment to have the new ruleset as their destination ruleset.
  3. In Dev Studio, click the name of your application, and then click Definition.
  4. Make sure that the top rule in the Application ruleset section has a major and a minor version, for example, OpsOverlay:01-02. If required, update the ruleset version.
    Note: Do not include the patch number in the ruleset version.
  5. In App Studio, click SettingsApplication settingsCustomer Decision Hub.
  6. Select Enable NBA Designer Update.
  7. Upgrade your Next-Best-Action Designer.
  8. Validate that rules created during Next-Best-Action Designer upgrade are associated with the ruleset that you created in step 1.
  9. Lock the ruleset that you created in step 1.
  10. Log in as an operator with the OpsAdmin access group.
  11. In Dev Studio, edit the NBASpecialist access group, and remove the Feedback role from the group.

If your environment includes Deployment Manager 5.1, do the following additional steps:

  1. Create a Product rule that contains just the ruleset.
  2. Create the following deployment pipeline in the orchestration server: Business Operations environment > Development > Production.
  3. In the new pipeline, click Start deployment.
  4. Create a new Business Operations pipeline.
  5. If any merge conflicts occur on the new Business Operations pipeline, do the following steps:
    1. In your Development environment, in the Pega Customer Decision Hub portal, click Revision Management.
    2. Click ActionsMerge, and then click Conflicts.
    3. Solve each merge conflict, and then click Mark as resolved.
    4. In the orchestration server, retry the deployment.
  • Previous topic Removing withdrawn data sets from interaction history summaries
  • Next topic Upgrading the Next-Best-Action Designer

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