We are looking for options to rollback a deployed product version which includes class instances, indivudual data instances (with/without history enabled), Post deployment actions etc. etc.
Any proven method for rolling back a deployed product version? what is the best solution and what are the list of things that we need to take care of manually (or systematically)?
@Vamsi.Thatavarthi To rollback a deployed product version in Pega you can use the rollback feature of Deployment Manager. Here are the steps and considerations for rolling back a deployment: 1. Using Restore Points: Rollback relies on restore points which are automatically generated every time an import happens. Any change implemented after the import but before the next restore point will be lost when the rollback action is triggered. 2. Manual Rollback Steps: If a successful deployment must be rolled back you can insert a manual step as the final task in the stage where rollback is required. Assign this manual step to a user who will make the decision to approve or reject the deployment. 3. Handling Class Instances and Data Instances: For individual rules or code changes you can use the PRPC delete rule option. Alternatively you can point your access group or requestor specific ruleset references to the correct rulesets. Deleting rules and rulesets from the database using SQLs is also an option but involves a significant risk. 4. Database Rollback: Another approach is to roll back your database with the help of a DBA to restore it to a state before the release started. This approach is more suitable for larger releases. 5. Schema Changes: Note that schema changes are not rolled back automatically. If required manual intervention is needed to prevent data loss. 6. Post Deployment Actions: Ensure that any post deployment actions are also considered during the rollback process. 7. Application Level Rollback: For Pega versions 8.4 and later with PegaDevOpsFoundation 4.8 and later the rollback will be application level and will not impact other applications. 8. Abort vs. Rollback: Decide whether to abort or rollback based on the deployment’s impact. Aborting is suitable if there is no harm in keeping the current state while rollback is necessary to revert to a previous stable state. By following these steps you can effectively manage the rollback of a deployed product version in Pega.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
How to Rollback an installed Product