This behaviour is OOTB in 7.2 onwards where multiple workgroups can be supported for the same operator.

How can this be achieved (if at all) in 717?

Hello!

I found this SA-28015, When switching workgroup Team Members list not updated. Does that help you out?

Marissa | Community Moderator | Pegasystems Inc.

Hi Marissa,

Thanks for the reply!

I will provide a bit more details on what we are trying to achieve.

The business users in our Application stack will have access to 3 different applications. Each of this application needs to be mapped to different WorkGroups so that the portal shows the appropriate workbaskets when the user chooses to switch applications.

Essentially what this means is, we will have a business rule to track the application mapping to workgroups (this piece of info will be coming in from the client) and trigger this business rule when we use the Switch Apps functionality. How does this sound to you?

In case you need more inputs, I shall be more than happy to share more details. 

We have tried by adding an event to the Navigation rule (Run Data Transform) and tried to update the value OperatorID.pyWorkGroup depending on the name of the current application. But this appraoch not helping us much

Regards,

Bidyun

Hi Bidyun,

When exactly you are calling the data transform? are you able to get the current instance of Data-Admin-Operator-ID? since I am not sure you can that from a Data transform itself as you need to do an obj-open  for current instance of D-A-O-ID, atleast you need to have pzinskey of that operator to do obj-open-by-handle.

Thanks,

Habeeb Baig

There is a concept of Active Workgroup When the user logs in. In clipboard you can find a page called pyDisplayHarness and inside that Page the active workgroup of the user resides. This basically happens when the operator logs into Pega.

You can override this during login of your application. Save the pyDefault in Data-Portal (if i am not mistaking this is the class ) and change the active workgroup there. you will notice that this will override the workgroup that you have in your operator ID. This is runtime changing of workgroup when someone logs in.

You can also change the workgroup when you log in by introducing a gadget within your portal just force a refresh and the workgroup will be changed.

Honestly, Pega's workbasket and Workgroup still bothers me :) ...Let me know if this Helps.