Support Article
Circumstanced skin is not picked on opening Interaction portal
SA-91199
Summary
Circumstanced skin is not picked when user logs in to the Interaction portal.Error Messages
Not Applicable
Steps to Reproduce
- Circumstance a skin rule based on a property
- Launch the Interaction portal from Designer Studio
- Verify if the circumstanced skin rule is picked when the required circumstance condition is met
- Log in to the Interaction portal
- Verify if the circumstanced skin rule is picked
Root Cause
A defect in Pegasystems’ code or rules. During the GetWorkStyle activity in which skin is resolved, pySecondaryPortalThread is not set on the pxRequestor page on the Case Manager portal. Hence, the local variable skinName at step 6 is set as empty string. When the Case Manager portal is launched from the Designer Studio, pySecondaryPortalThread is set as OpenPortal and it returns the configured skin name.
Skin circumstancing is supported as per the documentation. However, skin must not change within the same portal. Skin circumstancing still works on using different skins when different portals are launched. If the user loads the new circumstanced version of skin for a format change (performance hit), extra Cascading Style Sheets (CSS) are loaded from new skin instead of using the cached version of file.
Resolution
An enhancement request, FDBK-62561, is created for consideration by Pega Product Management.
Published October 18, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.