Customer would like to get a list of critical Hotfixes for 7.4. I don't believe Pegasystems provides such thing at official website over the Internet like Microsoft Windows and only way to know is to scan the Pega Platform thru Hotfix Manager using the latest Catalog.zip file (ftp://catalog:firstname.lastname@example.org/hfix/CATALOG/61/CATALOG.ZIP). My expectation was Hotfix Manager would just tell you what critical Hotfixes are missing, but actually it did not behave like that - it installed 10 Hotfixes without even asking or before showing anything. And it even committed it (see below screenshot). The committed Hotfixes don't say if they are critical missing category or not and I am not sure why these 10 are selected. Are all these a correct behavior?
What is the standard practice just to know the list of Critical hotfixes for 7.4?
Question #1: It has been more than half year since Pega 7.4 is released. If there are no Critical hotfixes in a half year, does that mean usually it is one or two a year in general? If so, I would consider it as SUPER Critical, and not recommended ones.
Question #2: Are you saying this behavior (install it automatically without even asking) is a correct behavior? What should I do if I only want to see a list of critical ones but no installation?
I think this is more likely to be due to the information in the hotfix Catalog.
I don't have an exact knowledge of how this is designed, but a working knowledge.
From what I've understood the Catalog will contain the details of all the hotfixes (engine code, rule changes, extra jars, etc...) and when you perform a System Scan this will go through the various components of your system and compare this to the catalog to determine what you have installed.
If all versions of the components of a hotfix in that catalog match the versions of the rules, engine code, etc... then that hotfix is deemed to be installed.
If all version of the components of a hotfix in the catalog are lower than the versions that you have then the hotfix is deemed to be superseded.
However, if some of the components are the same or it cannot determine the version then it may be deemed to be partially installed.
So in this instance if you haven't installed those hotfixes I guess one of the components of the hotfix is a match to the version that you already have. Or the component is not versioned, so it's unable to determine this.
Can you please try scan? I tried three times and every time it installed 10 Hotfixes. My teammate also tested it and it installed Hotfixes automatically. I assume this issue happens in any 7.4 environment.
Thanks for testing. I feel like you are saying correct things, but this is complex to understand. When I install individual hotfix, it is shown Uncommitted. If I install it with Commit, it moves from Uncommitted to Committed. But I don't understand when I scan it some of Hotfixes are shown as "partially installed" without installing anything. If this tool is designed more intuitively, it should have two categories; Installed (Uncommitted / Committed) and Missing (Critical / Non critical). When scanned against the latest catalog, list of all Hotfixes should be shown in Missing category. When selected and installed, they should move to Installed category.
Otherwise this interface is confusing and I don't think many people could explain what this list means at a glance.
This Maintenance Pack bundles a number of bug and security fixes on the Pega 7.4 release into a single package which has gone through our quality assurance process. Deploying this on your Pega 7.4 platform system will apply these fixes, ensuring that you have the highest quality experience.
I don't think anything was installed when you scanned the system. Most likely your installation package came with a few pre-installed hotfixes. These hotfixes weren't 'exposed' earlier because there wasn't a catalog present to identify them. When you uploaded the catalog, the scan identified the pre-installed hotfixes and reported them.