Skip to main content


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

Updating Pega 1:1 Operations Manager

Updated on June 20, 2022

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

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

Pega Customer Decision Hub Update Guide
  1. In Dev Studio, click the name of your application, and then click Definition.
  2. 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.
  3. Log in as an operator with the OpsMgrAdmin access group and make sure that the overlay ruleset is pointing to the latest version.

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. Log in as an operator with the OpsMgrAdmin access group.
    2. From the application definition, open the associated revision branch.
    3. Click ActionsMerge, and then click Conflicts.
    4. Solve each merge conflict, and then click Mark as resolved.
    5. Submit your changes.
    6. On the Merge Branches screen, click Cancel.
    7. In the orchestration server, retry the deployment.
  • Previous topic Removing withdrawn data sets from interaction history summaries
  • Next topic Updating 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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us