Skip to main content

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

Optional: Managing revisions manually

Updated on July 5, 2022

As a best practice, you should always use Deployment Manager 5.1 to automate your business change management process. However, if necessary, you can also manually import, activate, discard, or roll back revisions in the production environment.

Each operation that you complete causes changes in the system, such as changes to application version numbers or to access groups.
  • Importing revisions

    A revision manager creates the revision package in the business sandbox, in the context of an application overlay. You can import that package to Pega Platform to propagate rule changes to the production environment or first test the changes with a selected group of application users.

  • Activating revisions

    Activate a revision in test to propagate the changes included in the revision to all operators. Activate only those revisions that have been approved by testers. You can have only one active revision in the system at a time.

  • Discarding revisions

    When test users finish testing a revision and find that it is not working as expected, you can discard the revision from the production system.

  • Rolling back revisions

    You can roll back revisions that are already in production. You might do this when you find serious issues with the new application version that were not discovered during testing.

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