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.
The primary path in the Revision case type is represented by the following stages:
|Provide revision details.
|Create a revision through the designated activity.
|Add Change Request
|Create one or more change requests through the designated activity.
|View the revision. Optionally, update revision details, add change requests, withdraw or submit revision.
|Monitor the progress of the revision simulation and review the performance trend.
|Create a RAP file that contains the modified rules.
|View DD Revision
|Activate or withdraw a revision, independently from application administrators. Available if direct deployment of revisions is enabled.
|Make a revision available for testing or in the production environment.
|Withdraw a revision from the test or production environment.
The Revision case type can also have the following alternate stages:
|Withdraw a revision if in Open or Direct Deployment stage.
|Roll Back Revision
|Withdraw an active revision through a designated activity.
- Simulating your revision changes
As part of the revision life cycle, you can verify the performance impact of your changes within the revision package. To enable this capability, configure the pySetRevisionSimulationSettings data transform.