Posted: 28 Jan 2016 7:07 EST Last activity: 4 Mar 2016 9:06 EST
Roll back single hotfixes
we are using Pega 7.1.7. With the functionality "Rollback All" it's possible to roll back all installed Hot Fixes. When having installed more than one Hot Fixes that are not committed yet, is it possible to roll back only a single Hot Fix? In our case, we have installed 2 Hot Fixes but only want to roll back a single one and not all. Is that somehow possible?
The process for installing hot fixes should be to install, test, and then either rollback or commit. You should not be keeping hot fixes in an uncommitted state for longer than testing is needed and you should not be installing new hot fixes on top of uncommitted ones for just this reason. Since you only have 2 your best option would be to rollback all and then just install, test, and commit the one that you want.
Additionally, if you have installed a DL item with multiple hotfixes, you should not be attempting to rollback some of them. This is due to the possibly complicated inter-dependencies present in many DL items with multiple hotfixes. Allowing this would result in an unsupported condition with unpredictable results!
Generally, prior to installing a new DL item, you should seriously consider committing any uncommitted hotfixes, provided your team has tested them sufficiently in your application. There are circumstances that that isn't needed, but then you will have to rollback or commit all the uncommitted hotfixes as a group. In other circumstances you may wish to delay installing a DL until testing can be completed.
Easiest would be to have split schema so that if you do a db restore to last week on the rules db, you wouldn't lose the last week's worth of work too.
However, I recall there is a backup-work wizard that packages the work on a zip, optionally deleting the work as well (it may be called the purge work wizard) , so if you don't have split schema you could test the following:
1) Back up db. Install hot fix.
2) Discover that hot fix isn't working properly after you "committed" it on update manager.
3) Use backup-work wizard to save work on a zip. Restore db. Restore work from the zip.