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

When switching workgroup Team Members list not updated



A manager portal is configured to use the sections -- pyWorkGroupMembers (Pega-EndUserUI:07-10-09) and pyWorkGroupBaskets (Pega-EndUserUI:07-10-11)

It also contains a drop-down to select different workgroups.

When switching from one workgroup to another one, the list of members of the workgroup in section pyWorkGroupMembers is not updated.

It is always showing the members of the workgroup opened.

On the other hand, the list of workbaskets in section pyWorkGroupBaskets is well updated with the workbaskets of the selected workgroup.


Error Messages

Not applicable

Steps to Reproduce

  1. Access a manager portal containing sections pyWorkGroupMembers and pyWorkGroupBaskets (for example, pyCaseManager7) with an operator managing several workgroups.
  2. Switch from one workgroup to another one.

Root Cause

An issue in the custom application code or rules where the extendable Pega OOTB rules is used for this functionality.
As per the Pega’s default design the report pyOperatorsByWorkGroup only considers the D_ManagerWorkGroups.pxResults(1) page.
Thus, it will always bring result from the same WorkGroup. 

This Data page is populated by a report definition pxGetOperatorWorkGroups of Index-Operator-WorkGroups class and it is based on filter criteria that points to the current operator. Hence, the result count is always one and explains why there is only pxResults(1).
In the said custom design a single operator login user will be switching to different workgroup the above underlying report will work in the same way to populate the Data page.


Following is the local-change step:

In the report pyOperatorsByWorkGroup used by section pyWorkGroupMembers replace the condition: 

.pyWorkGroup = D_ManagerWorkGroups.pxResults(1).pyWorkGroup 
.pyWorkGroup = pyDisplayHarness.pyActiveWorkGroup


Published September 20, 2016 - Updated October 8, 2020

Was this useful?

100% 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