SA-10547

Summary

After a long period of inactivity, an operator connected to PRPC through an url is losing the application custom styling (it revert to PRPC out of the box styling).

Note: When this problem occurs, the url is different:

URL with good styling (Css) :
http://xxxxx:8180/prweb/PRWebLDAP1/jKsTKcraO6jx_JWSXlUxXA%5B%5B*/!Prototype/$STANDARD?...

After 2 hours: The url is different
http://xxxxx:8180/prweb/PRWebLDAP1/jKsTKcraO6jx_JWSXlUxXA%5B%5B*/!STANDARD?....

Error Messages

No error message

Steps to Reproduce

1) Connect throught an url like this:
http://xxxxx:8180/prweb/PRWebLDAP1/9zvTd2IrEq4OB3a1lvOIlOBmudCwMWyF*/!STANDARD?pyActivity=....

2)Wait a long period (more than two hours) and drag an drop the same url in the same browser
3) a bad css is loaded

Root Cause

The root cause of this problem is software use/operation error.

During authentication, the url was set so that the word "Prototype" would be included. Due to the location of the word in the url, this caused PRPC to create a Pega thread with name "Prototype/$STANDARD" which would be populated with various information such as the portal skin in .pyPortal.pyPortalSkin.pyAppWorkStyle.

Later on, the generated url would never have the word  "Prototype". This means later on PRPC would always use a Pega thread with name "$STANDARD".

Initially, your Web page will be displayed fine as long as the CSS file is cached and the page is not being fully re-loaded.
However if the CSS file is removed from the cache or the web page fully reloaded then browser is retrieving the portal information based on the "$STANDARD" thread. But the "$STANDARD"  thread doesn't have the property .pyPortal.pyPortalSkin.pyAppWorkStyle populated, hence triggering the issue.

Resolution

This issue is resolved through the following local change: A property-set was removed which was adding the "prototype" word (in a custom activity.