Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Skins do not get picked up randomly

SA-4086

Summary



When using circumstancing the pyCaseManager portal with different skins rules, the portal styles are not all refreshed to the new ones when switching portals by updating the circumstance and refreshing the screen.

Steps to Reproduce



Circumstance portals on a property value.  Each portal should have a different skin.
Switch portal by updating the property used for the circumstance and refresh the screen.
create new cases.
Not all styling is updated to the new styles.


Root Cause



The pyCaseManagerPortal uses multiple threads, and these are not reinitialized until the user logs off, and back in.

Resolution



Possible local change solutions.

- If implementing custom skin switching, force the user to log off when switching skins (i.e. updating the circumstance).


Create an access group and associate this with a separate portal which in turn contains a separate skin. The user would then have to list this access group to their Operator ID.

- Circumstance the harness rules instead. The circumstanced version of the harness rule would include the specific styles that would override that of the Skin rule. 
 
 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us