Hi Rob,

If i understand right ? you would like to have a different org structure per application.

so while creating a new application itself we can create a different org structure that we want.

Screen shot for reference

let me know if i missed something.

thank you for the response.  For whatever reason, I can't see the image clearly.

But yes, different org structure and potentially workgroups per application.  Now, granted the different org structure may or may not be a complete one from Organization level but probably more like a different leaf of the org structure (not sure if this correct view of it -- perhaps lack of knowlege on my part).  But at the same time, a different active workgroup may be required as well;  context could be a  HR-admin app vs HR finanance app vs Internal corporate app vs Business purpose-driven app.   And the [potential] "requirement" of switching between them...  Perhaps there is a better way of doing this besides switching apps/portals?

Hi Rob,

I have attached a word doc with the screen shots , please check the same as we can configure completely a new orgainsation structure using the advanced configuration settings.

@Avinash   Sorry for the slow response. 

I can now see the document, thank you.

Yes, two separate applications with separate org structure can be on the same Pega installation. 

An operator can switch between the apps.  But because the org structure and workgroup(s) are specific to the operator, then the org structure and/or workgroup(s) may have to updated.

I am just wondering what options are available to support this.  Does it mean we have implement specific logic as part of the switch apps menu choice?  Is there another / better way to implement this?

I wanted to follow up with trying to provide more details on the scenario.

Org structure and workgroup definition are assigned to the operator.  (as opposed to the application)

If we have two applications running on the same Pega installation, what's the best way to deal with switching apps but also ensuring the workgroup and org structure defined for the operator  remain appropriate for the requirements of the application.  The only solution I can think of is customizing the switch app (operator menu) to perform the adequate logic to setup the correct operator details.

App 1   has org structure     ORG-DIV1-Unit2  and   workgroup-A

App 2 has org structure  ORG-DEV2-Unit3 and workgroup-B

So when switching from App 1 to App2 (or vice-versa) , the operator details are updated to reflect the appopriate App requirements for org structure and workgroup.

Is there a better way of doing this?

We are currently using Pega 7.1.8 which limits the operator to only one (1) workgroup so switching is required

I know  Pega 7.2.1 has ability for multiple workgroups (question with that is how is the default/active workgroup defined)

Default work group can be set at user access group level by selecting the radio button.

let me know if i have answered it correctly .

Hmm.   @Avinash.    Not quite;   The default you are showing is the Access Group.  I am looking at default workgroup.  So, going with your example.  The Accounts:Administartors  has a default workgroup of   accountsWorkgroup. 

The DMSample:Administrators has a default workgroup of sampleWorkgroup.

When the user logs into the system, the default application would be the portal associated with the Accounts:Administrators access group (with default workgroup of accountsWorkgroup).  If user switches portals to DMSample:Administrators, I would like the default workgroup for the user to switch to sampleWorkgroup.

As we authenticate via Active Directory, the process of switching applications would need to re-authenticate (to ensure they are authorized for the application being switched to) and the default workgroup would need to be changed as well.   The only way that I can think of doing this is customizing the Switch Portal construct.  The other problem with this is switch to one app and back again, you have completely lost the context you were in with the initial application.  Is there any other way of doing this?  (I am just afraid I am missing a more elegant design/implementation)

Hello Rob,

Have you tried instead of switch portal, switchapplication script call to the targeted access group ?

Regards

Hi Rob,

                   Were you able to do this? If yes, can you please give the details.

Thanks!

Hi Rob,

The requirement is similar to one we have at hand!

Were you able to achieve this?

Regards,

 Bidyun

Hi,

sorry for the delay in response.  Haven't implemented the solution as I am not sure it's the right way to go.  I suspect there's other implementations possible, but not sure. 

or is FCM (Federated Case Management) the better direction?

Rob