Having: 2 groups of Users (UserGroupA & UserGroupB)
2 portals (OldPortal & NewPortal)
2 datamodels (OldCases & NewCases)
1. Any Operator from UserGroupA should be able to access old OldPortal and OldCases within the portal.
2. Any Operator from UserGroupB should be able to access NewPortal and migrated OldCases and NewCases within the portal.
3. Set my operator dinamically to UserGroupA or UserGroupB depending in some values coming from a nightly background agent.
Then we are mainly considering 2 approaches:
A) Separate AccessGroups: The agent sets all access groups in the operator. The login process select the default access group depending on information coming from an external system (External system will provide several profiles for this user and depending on these profiles we will select 1 AccessGroup or another).
In this way we can point different applications.
B) Separate Portals: The agent sets a common access group for the operators. The login process switched the portal in the requestor of the user depending on the information coming from an external system. (External system will provide several profiles for this user and depending on these profiles we will select 1 portal or another).
This solutions seems to be simpler, but more difficult to maintain since rules from OldModel & NewModel cant be separated.
Client is asking for advice in which approach to take or to provide new ideas on how Pega did this in other projects.
Can someone give any recommendation on which approach to take? I think A will be easier to extend and reuse, but this is the first time I am working on that so any idea / comment from your experience previous project will be highly appreciated.
I have tried switching of the access groups using LDAP authentication. Where in the access group can be changed in the LDAP for a specific operator. Once when the operator logs in to the system, the access group will get changed to new access group mentioned in the LDAP and open the correct portal.