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.
@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
@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?
@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)