By using revision management, you can make the process of updating business rules in your application faster and more robust.
When business requirements and objectives change, you can adjust your decision management application by modifying rules such as Strategy, Decision Table, Decision Data, and Scorecard.
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.
The revision management process is defined by the Revision and Change Request case types.
For more information, see the Pega Community article Revision management of decisioning rules in Pega Platform.
- Revision case type
The primary purpose of the Revision case type is to initiate the process of changing business rules in your application. This case type covers all aspects of the revision life cycle. A revision can have one or more change requests associated with it. You can modify the stages, steps, processes, or assignments that are part of the Revision case type to make it simpler or more complex, depending on the business needs.
- Change Request case type
By default, the Change Request case type is the subcase that is created in the first stage of the Revision case type life cycle.
- Managing revisions
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.