Corrutped UI and Icons lost after upgrading to 8.2.1
After upgrading to 8.2.1 from 7.3.1, the designer studio and the application has a corrupted UI in all its icons.
Some icons does not appear at all
Some icons are replaced by weird letter
Some icons are squares, or three dots
Contacted Support they suggest to delete some jars in the DB, but without any success. We cleared servers caches on all nodes, with no success. The only solution to fix it is to clear BROWSER cache. This is extremely problematic, as imagine asking 10000+ end users to do this step, in-acceptable and we need a server side solution.
Since Support have no solution yet, Anyone faced the problem on their upgrade and managed to fix it?
***Edited by Moderator: Lochan to update platform capability tags***
Looking at the screenshot, I can say that content for the icons are not properly applied.
Generally, these are defined in px-pega-default-icons css file. Specifically to understand the issue for down arrow icon change, can you check the content attribute value for pi-caret-down:before class in the css file. Or inspect the element using developer tools and check what is the content value that is applied and from where it is referred.
To diagnose rules assembly and caching issues, read the Rules Assembly (RA) statistics. To view the RA statistics for an individual, run the My Performance Details tool in Designer Studio (Designer Studio > System > My Performance) and enter the user ID in the User ID is Equal field. To view the RA statistics for an application, run the Performance AnaLyzer (PAL) tool in Designer Studio (Designer Studio > System > Performance > PAL) .
The statistics presented by the My Performance Details and PAL tools are the same. The difference is that you can look at statistics for individual users with the My Performance tool.
If the RA statistics are high, then an issue exists in rules assembly or caching.
Consider the Rule I/O Elapsed and RA Elapsed readings. Rule I/O Elapsed indicates time spent retrieving resolved rules from the database, and RA Elapsed indicates time spent on rules assembly and caching. High rule I/O or rules assembly readings indicate that the system is assembling rules unnecessarily.
SR linked, SME has suggested more than one solution. But none fixed the issue for all people. all the solutions suggested are provided as trial and error, and none shows that there is an understanding of the root cause