Hi all,
We upgraded to Pega 8.7.4 version. After the upgrade, pages are not rendering properly.
Does anyone know the reason for this?
Any suggestions for this problem?
Do all users see this?
Can you confirm that there were no errors in your upgrade logs?
Which Pega Platform 8.7 Installation and Update Information Update Path did you follow? Did you go through all the update checklists?
This type of behavior can be related to customized CSS rules at your end.
I would suggest to look into the browser developer tools and also the Pega Logs for any errors while logging into the system, that might give you additional information to identify the root cause.
Yes, all users see pages like this. Activity pages, data types pages, case type pages, and more are not rendering properly
We followed the below link for the upgrade
We can view these rules properly from the Pega Platform application, but when we switch to the custom application, it does not appear properly.
We think it has to do with CSS too
Can you give a little more detail about the CSS?
@MerveS could you take a look at the articles I suggested, such as Debugging your UI?
There might be a CSS which if you remove the custom CSS from the browser developer tools then it may render as expected.
Also note that there are limitations with the ‘Switch application’ functionality.
When you are switching the application you have to switch it from primary portal, you cannot launch secondary portal , interaction portal and switching applications from launched portals. When we log into a primary portal, then it will establish the new session.
We should not use switching applications from secondary or child windows or launched portals because it can can have two instances of designer studio and we don’t support that. If we do switch applications ,UI AND SESSION will be out of context and sync.
Can you confirm that when users open the main portal it all works fine?
What happens if the User logs out and logs in - is the issue no longer reproducible? As a prerequisite you need to configure required access groups in the operator profile through designer studio.
Please compare the Network logs - you may be seeing CSS files showing 304 status code.