Policy about 'Critical missing' hotfixes.
Hi, we found that there are several 'Critical missing' hotfixes from the Hotfix manager. what policy should take for these 'Critical missing' hotfixes? Install and pre-confirm/post-confirm the effect need extra cost and resource for client, and also risky to the stable applications.
***Edited by Moderator Rupashree S. to add Capability tags***
Accepted Solution
Updated: 8 May 2024 12:08 EDT
Pegasystems Inc.
US
@chend1 You could test them in a dev environment first, and confirm that everything is good before deploying the hotfixes to prod environments to reduce risk
More info for Security hotfixes is available here: Downloading Security hotfixes in My Pega | Support Center
Pegasystems Inc.
JP
@PhilipShannon Thank you for your reply. the situation is that my client do not have resource to install the test/confirm, even in the dev environment. Is it okay to leave the 'Critical missing' hotfixes without any action, or we have to persuade the client to get budget to do so?
Updated: 30 Apr 2024 7:51 EDT
Pegasystems Inc.
US
@chend1 If you install them in uncommitted mode, there is an option to roll back if/when encounter any issues with the hotfix. This may work for your client for critical security hotfixes, install them uncommitted Rolling back hotfixes (pega.com)