Skip to main content

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

Understanding business change management, revision management, and pipeline automation

Updated on August 4, 2022

With business change management, business users can respond to changing requirements by modifying and deploying your application's rules in a controlled manner.

Pega Customer Decision Hub

Business change management and revision management

Pega Platform provides business users with the means to implement and test modifications to their applications outside the enterprise release cycles. Revision management enables business users to respond quickly to changes in the external and internal factors that influence their business. Responses might include introducing new actions or propositions, imposing eligibility criteria, or modifying existing business strategies.

Use the revision management process to:

  • Give business users the ability to make, test, and implement changes to business rules.
  • Define the rules that are available to business users by creating an application overlay and managing revisions in the production environment.

Depending on the type of rule that you want to modify, business changes can be launched from the Pega Customer Decision Hub portal, or from a Pega 1:1 Operations Manager application. For more information, see Understanding the relationship between Pega 1:1 Operations Manager and revision management.

Business change management and pipeline automation

Although revision management packages can be manually created and deployed to the target environment, you can enhance your business change management process by using the automated deployment pipelines provided by Pega's Deployment Manager 5.1 or newer. Use Deployment Manager to increase the efficiency of business-as-usual application changes and automatize the deployment of revision packages.

Instead of manually deploying revision packages, you can 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.

Changes made in your business operations environment are merged to the system of records and deployed to each environment, as shown in the following figure:

  • Previous topic Managing business changes
  • Next topic Understanding the relationship between Pega 1:1 Operations Manager and revision management

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