Skip to main content

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

Deploying revisions with Deployment Manager

Updated on May 17, 2024

As a best practice, you should use Deployment Manager 5.1 or newer to automate your business change management process, run CI/CD pipelines to merge a revision package to the development system of record (SOR), and subsequently deploy that package through to your production environment by using a deployment pipeline.

Before you begin: Configure Deployment Manager. For more information, see Using Deployment Manager for model-driven DevOps.
Important: Your Deployment Manager version must be 5.1 or newer. Previous versions of Deployment Manager do not support working with revision management packages. For information about upgrading Deployment Manager, see Installing or upgrading Deployment Manager 5.
After a revision manager submits a change request in the business operations environment and a strategy designer implements the required changes, the new revision must be deployed to production. To automatize the deployment process, use Deployment Manager pipelines. You can merge a revision to a deployment pipeline directly from the Pega Customer Decision Hub portal.
  1. Log in to the Pega Customer Decision Hub portal as an operator with the RevisionManager access role.
  2. In the left navigation panel, click Revision Management.
  3. On the Revision Management landing page, click Revisions.
  4. Click the revision that you want to deploy and review its contents.
  5. Click Deploy revision.
  6. In the Pipelines section, select a Deployment Manager pipeline to merge the package to the development system of record, as shown in the following figure:
  7. As a best practice, in the Comment field, enter a short description of the changes included in the revision, for example, Introduced a new business issue.
  8. Click Deploy.
    Result: Deployment Manager queues the revision to merge it into a pipeline. After a successful merge, the revision deploys automatically to all environments in the pipeline. You can monitor the status of the deployment process in the Pega Customer Decision Hub portal, as shown in the following figure:
  9. Optional: Depending on the configuration of your deployment pipeline, you may need to manually approve the revision for deployment to your production environment. If required, click the Deployment Manager portal link and approve the revision in Deployment Manager, as in the following figure:
  10. Optional: If the revision deployment fails at any stage, click Cancel to complete the revision with status Completed-Failed.
  11. When the revision reaches the Test & Activate stage, click Test and activate this revision to select the operators to test the revision before you activate it, as in the following figure:
    Tip: If you do not want to test the revision, select Activate for all operators instead. Selecting this option activates the revision directly.
  12. Click Complete revision to resolve the revision and allow the deployment of new revisions.

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