As a system architect, you control how your enterprise application changes when business users introduce modifications through revision management. To do this, you 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.
- Addressing changing business requirements
With revision management, business users can respond to changing requirements by modifying and deploying your application’s rules in a controlled manner.