Rolling back hotfixes
If an uncommitted hotfix introduces unwanted changes to your system, you can remove it by rolling it back. You cannot roll back committed hotfixes. If you have more than one uncommitted hotfix, roll them all back and reinstall the hotfixes you want to keep.
- Database schema changes associated with a hotfix are not removed when rolling back.
- Rolling back hotfix packages is different from rolling back to a restore point. Restore points track rules and data that have been added, modified or deleted, regardless of how the rules or data were created. Rolling back a hotfix package affects only the hotfix artifacts.
- Rolling back hotfixes from the user interface
If an uncommitted hotfix introduces unwanted changes to your system, you can remove it by rolling it back.
- Rolling back hotfixes by submitting a request to an active instance
If an uncommitted hotfix introduces unwanted changes to your system, you can remove it by rolling it back. If you have an active instance of Pega Platform, you can roll back hotfixes by submitting a request to an active instance via a web service.
- Rolling back hotfixes by using a direct connection to the database
If an uncommitted hotfix introduces unwanted changes to your system, you can remove it by rolling it back using a direct connection to the database. This is most commonly done for a stopped instance.
- Applying hotfixes
Hotfixes are software updates that Pega creates to fine-tune the behavior of a release of Pega Platform.
- Installing hotfixes from the user interface
After you have obtained the hotfix and prepared to install it, you can install the hotfix package from the user interface to update your system with the new functionality.
- Committing hotfixes
Commit all uncommitted hotfixes to make the hotfixes a permanent part of the system.