Skin Changes are not reflecting at runtime in the end user portal.
Hi Team,
We've been upgraded from PRPC6.3 SP1 to Pega 7.1.7. After successful upgrade, Whatever the changes done in the skin rules are not reflecting in the portal at runtime. However, the same changes are reflected in the preview section of the skin.
Below are the different approaches we tried to find the root cause,
1) "save as" of the skin rule to new ruleset version
2) Revalidate and Save of the Rule-PortalSkin type instances
3) Clearing the browser cache
4) Referred "pyEndUser71" skin rule instead of our sikn and observed that the changes are REFLECTING IN PORTALS.
After doing the above steps, it is very clear that only application skins have the problem where as ootb skins does not have the problem.
We are thinking that the Skin generation and cache could be the problem of not reflecting the skin at runtime. Is our assumption correct ?, if yes, what are the different cache tables that needs to be truncated and Is it also required to remove Pega Temp directory ?
Please let us know further steps to investigate.
Thank you.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
IN
No, There is no such skin configuration at operator profile..
Could you please share the steps to clear the cache in Pega 7.1.7
Thank you,
Pegasystems Inc.
IN
Not sure whether you are directly logging to the application which launches end user portals or navigating from designer studio. Please check the following.
1) There is no different skin is defined in Operator preferences ( if you are launching end user portals from designer studio)
2) make sure that your portal level skin is configured with the correct skin rule
Sopra Steria Group
FR
Hi everyone,
I have the same problem, running PRPC 7.3.1 in the Pega Cloud, the skin is not showing up at all on the end user side.
It would be very helpful to have a clear procedure on how to set it up, and get it working.
Regards.
Techmahindra
GB
Give a try of below steps where there is high chances of fixing the issue:
Stop the server.
Remove the file PegaRULES_Extract_Marker.txt file
Start the server. It forces system to reload all files.
Sopra Steria Group
FR
Hi Sateesh,
Thanks for your suggestion, I don't have access to that file being in the Cloud though, but I will try to raise an S/R to get it removed.
Regards.