Posted: 3 Apr 2016 23:54 EDT Last activity: 17 May 2016 20:35 EDT
Pega 7.2 - UI Issue after upgrade from Pega 7.1.9
The below issue is specific to Google Chrome browser and our users are using Google Chrome as their default browser to access pega applications.
Our application was built on Pega 7.1.9 and we have been upgraded to pega 7.2 a month ago.
Once we have upgraded the environment, we tested all the UI screens and couldn't see any issues.The test was successful.
But after two weeks of upgrade, we started facing issues with UI in user portal in Dev environment.
The user portal is launched with no styles picked up from Skin and the entire UI was broken. The links were not working, no borders or colors.
While debugging we found that in 7.2 the latest version of UI Kit is UI-Kit-7:06-01.
Our applications were pointing to UI-Kit-7:02-01. Hence, we removed the older version of UI Kit and added the latest version of UI Kit in the Application Rulesets.
This has solved the issue and the UIs are back to normal. All seemed to have worked as expected.
But now, we are again facing the same problem with UI. The user portal is broken again , no styles from skin is reflected, the UI looks like a plain HTML screen.
But If we access the same application in Internet Explorer, the screens are rendered properly.
We just tried by reverting the UI kit version to the older version which is UI-Kit-7:02-01 from the latest and the screen is rendering properly again with older version itself. But if we point the application back to new UI-Kit its broken.
Have anyone else faced similar issue?
Can anyone give us some pointers on why this kind of UI Issue is happening?
Is there a cache in the server that holds UI related details and somehow the cache is cleared? Although I doubt it, as the issue is browser specific.
We could not see any failures in tracer, no errors in logs as well.
We have had customers report to us skin corruption issues in the past, however reasons can be several. Your scenario where it is ok in IE but not in chrome does seem a little odd.
Let's see if we can help you get to the bottom of this.
Is it possible for you to do the following -
Test#1: Point your app to use UI-Kit-7:06-01-01, delete browser cache, run Fiddler and load your portal in IE. Repeat the above steps test in Chrome. Do you see HTTP 404 errors in the Fiddler capture in Chrome? Please share the fiddler session file here.
Test#2: Reproduce your issue with the UI-Kit-7:06-01-01 in Chrome. At this point check your DB,
run the below query select * from pr_sysgen_static_content where pybasefilename like 'pzskinv2_<param1>_<param2>%' where param1 is the name of the skin rule in use on the portal and param2 is the auto-generated hash You can get the exact file name by doing a view source on your UI portal/screen and looking for 'pzskinv2'
Do you see any entries in the table that match the exact pybasefilename? If no - then you may be suffering from a CSS purging issue. If yes - then verify if you see files with matching names in your Pega temp directory on your PRPC server. . If no - then you may be running into a disk space issue
Test#3: Can you please bring up your SMA and check if DeleteUnusedStaticContentFiles agent is running or not?
Test#4: Restart PRPC server, point your app to use UI-Kit-7:06-01-01, delete your browser cache, then test in Chrome. Do you still see the issue?