We have an application, with the requirement to identify, open and work on cases from another application within the same system. Both these applications are built on top of the same base application but have been slightly modified for their individual use. We have managed to make this cross application functionality work, however we have an issue when an operator has the access group for both applications attached to it.
The issue is with identifying the application the operator is in as we use this to identify where to retrieve certain data from. When the operator only has Access group A we correctly identify the operator as being in Application A even tho they're working on the case from Application B. However when the operator has Both access group A and B, the system identifies the operator as being in Application B, even though we got to this point in the same way.
We are using the Application.pyLabel property to identify the application.
Has anyone else attempted similar cross application functionality and has advice on how to overcome this?
***Edited by Moderator Marissa to update platform capability tags****
I believe Application.pyLabel will tell you the name of the current application, but it won't give you a list of applications that the operator has access to. You might want to look at
OperatorID.pyAccessGroupsAdditional That will be the list of access groups they have access to. From there you could walk through the list of access groups to see which applications that unlocks for them.
In this scenario, the User will never leave Application A, but just access a case from Application B through Application A. When the user has only the an access group for Application A, our method of using the Application.pyLabel works fine. However, when the user has access groups for both Application A and Application B, then using the Application.pyLabel shows as Application B. Again, all of this is done from Application A and the only thing that has changed is the addition of the Access group for Application B.