Support Article
Wrong requestor work pool when using UI-Kit-7:09-01-01
SA-41832
Summary
When the pyCaseWorker portal is launched, the pxRequestor.pxCurrentWorkPool property defaults to the wrong work pool. The issue does not occur when using the UI-Kit-7:08-01-01 ruleset instead of UI-Kit-7:09-01-01.
Error Messages
Not Applicable
Steps to Reproduce
- In the Cases and Data tab of the application rule, specify a class belonging to a different work pool than the one specified in the access group.
- Log in to the developer portal and verify in the clipboard viewer that the pxRequestor.pxCurrentWorkPool property matches the work pool given in the access group. This is the desired result.
- Launch the pyCaseWorker portal. Then go back to the developer portal tab and look again at the clipboard viewer and observe that, when the UI-Kit-7:09-01-01 ruleset is being used, the pxRequestor.pxCurrentWorkPool property has been changed to no longer match the work pool given in the access group. When the UI-Kit-7:08-01-01 ruleset is used instead, then the property will show the work pool still matching the one in the access group.
Root Cause
The issue is resolved by setting the pyDesktopType property to "User".
Resolution
Install HFix-36250. An alternate solution is to copy the UI-Kit-7:08-01-01 version of the pyCaseWorker portal rule to a user ruleset.
Published August 26, 2017 - 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.