Posted: 13 Jul 2020 9:17 EDT Last activity: 11 Feb 2021 7:30 EST
Mobile channel configuration method for multiple applications
We have couple of applications running on production. Now, we are required to configure a mobile channel (ios and android) and provide it to our users. There are many operators who have multiple application access. What we are wondering is that do we have to create a mobile channel for each application? Can we just create one mobile channel in framework application like more generic and distribute that application to the users ? We have observed that when an operator logs in pega platform it is being redirected to it's primary application. In this case, we thought that we can create only one mobile channel. Also we have customized navigation menu and added a link to switch access group and that functionality is working fine. So, can we just proceed like this and create one mobile channel ? Would it be any problem for pega platform ?
You will need to create a mobile channel interface and build a mobile app for each application. You can obviously share assets and configurations between the apps by using a shared ruleset to hold certain assets.
Ok, let's assume that I have 2 applications, A and B. And X user has access to both applications. In that case, should X user download and install both applications ? We observed that if X user's primary application is A, X user logs in to A application even on different application's mobile channel. X user even logs in to A application on B's mobile channel. In that case, why do we need to build different mobile channels ? It is also very confusing for end user. What if someone has access to 5 different applications ?
Edit: Also we were using Pega Mobile Express on 7.4 and we had no issues. I mean, if a user has access to multiple application, he/she can switch to different application via switchApplication script. Can we follow same approach on mobile client?
@EngincanY We have a similar issue with Pega infinity client with PRPC 8.4.3. We tried switching the AccessGroup during login of the mobile user but no luck. The rule resolution still points the application defined on the Rule-Channel-Mobile.
@AnandrajT7685 In our scenario, we did not need to dynamically change the access group during login, thus we just customized the navigation menu and added an option which enables user to switch his access group. It works fine.
Actually, what I am trying to find out in this topic was different than your requirement.