Question
Bits In Glass
IN
Last activity: 3 Mar 2023 21:49 EST
Need to have a single mobile channel for our application where personas with different access groups should be login to the app.
we had an application ABC. This ABC application has different roles technician, Service Advisor. Service Manager and so on. These roles have different access groups associated with them. We need to build a single mobile channel and all the users corresponding to these roles should be able to log in.
Initially, we created a mobile channel for a technician role we observed that a portal got created and added in the technician access group. We used pega preview App and successfully logged in to the moble applicaiton.
Now we created a common access group and used this common access group to build the mobile channel. We thought that since the access group for bulilding the mobile channel gets changed technican will not be able to login to the applicaiton. But technician is able to login to mobile applicaiton.
We Tried to login using service advisor from mobile. we got insuffiient permissions error. when we looked into the common access group here agian the mobile portal got added to the access group.
we added the mobile portal to the other roles and tried to login to the application. Now when we tried to login to the mobile app using service advisor we were able to login.
Our question is what pega will check when an user tries to login to the mobile applicaiton. Is it the access group in the mobile configuration rule or the portal in the access group?
Note: we used pega preview to install mobile application.
we had an application ABC. This ABC application has different roles technician, Service Advisor. Service Manager and so on. These roles have different access groups associated with them. We need to build a single mobile channel and all the users corresponding to these roles should be able to log in.
Initially, we created a mobile channel for a technician role we observed that a portal got created and added in the technician access group. We used pega preview App and successfully logged in to the moble applicaiton.
Now we created a common access group and used this common access group to build the mobile channel. We thought that since the access group for bulilding the mobile channel gets changed technican will not be able to login to the applicaiton. But technician is able to login to mobile applicaiton.
We Tried to login using service advisor from mobile. we got insuffiient permissions error. when we looked into the common access group here agian the mobile portal got added to the access group.
we added the mobile portal to the other roles and tried to login to the application. Now when we tried to login to the mobile app using service advisor we were able to login.
Our question is what pega will check when an user tries to login to the mobile applicaiton. Is it the access group in the mobile configuration rule or the portal in the access group?
Note: we used pega preview to install mobile application.
whether the same behavior will be applicable for android and ios.
Wipro
US
Based on your description, it seems that you are trying to build a single mobile channel for your Pega application that allows users with different access groups to log in. However, you are facing some issues with user login and access permissions.
First, it's important to understand that in Pega, access to mobile channels is controlled by the access groups associated with the user's operator ID. When a user tries to log in to a mobile channel, Pega checks the access group associated with the user's operator ID to determine what portals and functionality are available to them.
In your case, you have different roles with different access groups associated with them. When you created a mobile channel for the technician role, a portal was created and added to the technician access group. However, when you created a common access group and used it to build the mobile channel, you observed that the technician role was still able to login to the mobile application. This is because the technician's operator ID is associated with the technician access group, which still has access to the mobile channel portal.
When you tried to login using the service advisor role, you receive an insufficient permissions error because the common access group did not have the mobile channel portal added to it. Adding the mobile channel portal to the common access group allowed users with the service advisor role to login to the mobile application.
Based on your description, it seems that you are trying to build a single mobile channel for your Pega application that allows users with different access groups to log in. However, you are facing some issues with user login and access permissions.
First, it's important to understand that in Pega, access to mobile channels is controlled by the access groups associated with the user's operator ID. When a user tries to log in to a mobile channel, Pega checks the access group associated with the user's operator ID to determine what portals and functionality are available to them.
In your case, you have different roles with different access groups associated with them. When you created a mobile channel for the technician role, a portal was created and added to the technician access group. However, when you created a common access group and used it to build the mobile channel, you observed that the technician role was still able to login to the mobile application. This is because the technician's operator ID is associated with the technician access group, which still has access to the mobile channel portal.
When you tried to login using the service advisor role, you receive an insufficient permissions error because the common access group did not have the mobile channel portal added to it. Adding the mobile channel portal to the common access group allowed users with the service advisor role to login to the mobile application.
To resolve this issue, you can follow these steps:
- Create a common access group that includes all the portals and functionality required for the mobile channel.
- Add the mobile channel portal to the common access group.
- Add all the roles that require access to the mobile channel to the common access group.
- Ensure that each user's operator ID is associated with the appropriate access group that has access to the common access group.
This approach will ensure that all users with the roles that require access to the mobile channel can login to the mobile application and have access to the appropriate portals and functionality.
Regarding your question about whether the same behavior will be applicable for Android and iOS, the answer is yes. Pega's mobile channel functionality is platform-agnostic, meaning that it works the same way on both Android and iOS devices.
I hope this helps! Let me know if you have any further questions or concerns.
Wipro
US
To reiterate, in Pega, access to mobile channels is controlled by the access groups associated with the user's operator ID. When a user tries to log in to a mobile channel, Pega checks the access group associated with the user's operator ID to determine what portals and functionality are available to them.
Therefore, when building a single mobile channel for an application with different roles and access groups, it's important to ensure that all required access groups are added to the common access group associated with the mobile channel. This includes adding the mobile channel portal to each access group as well.
Regarding the question of what Pega checks when a user tries to log in to the mobile application, it checks the access group associated with the user's operator ID to determine what portals and functionality are available to them.
The behavior for Pega's mobile channel functionality is platform-agnostic, meaning that it works the same way on both Android and iOS devices.
Updated: 3 Mar 2023 7:05 EST
Bits In Glass
IN
@RishabR16722312 Hi Rishab thanks for the reply. To summarize we can create a common access group and add associated AROs. we need to add the portal that gets created while building a new mobile channel to all the access groups that need access to this mobile application i.e, Service advisor AG, Technician AG, Service Manager AG and so on which may come in the future. Is my understanding correct? And the same behavior will be applicable to Android and IOS.
We didn't add the common access group in the operator ID rule. Instead, we included the mobile channel configured portal in the access groups we required.
Please refer to the attached document which has configuration details.
Bits in Glass
IN
@nagajagadeeshg You have created all the sections and other configurations using app studio and then created a mobile channel to enable mobile app right? Did you do any kind of customizations in skin rule or anything to make screens responsive? I believe if we are creating everything without any customizations pega will handle responsive part. In earlier versions we were supposed to do few changes in responsive breakpoints in skin rule to enable responsiveness in mobile app. Please confirm.
Wipro
US
Thank you for sharing the configuration details document with me, and I appreciate your efforts in properly configuring access groups and portals for a single mobile channel in Pega. To answer your question, I confirm that your understanding is correct.
Based on the information provided in the screenshots document, it appears that the configuration process has been properly followed and implemented.
To properly configure access groups and portals for a single mobile channel in Pega, it is important to create a common access group that includes all necessary portals and functionality for the mobile channel. This common access group should contain the necessary Access Role to Object (ARO) rules that define the level of access users with the relevant roles and access groups have to the mobile channel. The mobile channel portal that is created during the building of the mobile application should be added to all access groups that require access to it, including Service Advisor AG, Technician AG, Service Manager AG, and any additional access groups that may be added in the future.
Thank you for sharing the configuration details document with me, and I appreciate your efforts in properly configuring access groups and portals for a single mobile channel in Pega. To answer your question, I confirm that your understanding is correct.
Based on the information provided in the screenshots document, it appears that the configuration process has been properly followed and implemented.
To properly configure access groups and portals for a single mobile channel in Pega, it is important to create a common access group that includes all necessary portals and functionality for the mobile channel. This common access group should contain the necessary Access Role to Object (ARO) rules that define the level of access users with the relevant roles and access groups have to the mobile channel. The mobile channel portal that is created during the building of the mobile application should be added to all access groups that require access to it, including Service Advisor AG, Technician AG, Service Manager AG, and any additional access groups that may be added in the future.
It is important to thoroughly test any changes to access groups and portals before deploying to production to ensure that users have the appropriate level of access to the mobile channel and the necessary functionality. This includes testing access groups and portals for all relevant roles and access groups to ensure that they are working properly and meeting the requirements. Additionally, as new roles and access groups are added to the Pega application, it may require additional maintenance and configuration to ensure that the mobile channel continues to function properly.
Regarding your question about whether the same behavior will be applicable to Android and iOS, the approach to configuring access groups and portals for a single mobile channel in Pega is platform-independent. This means that the same behavior will be applicable to both Android and iOS.
Again, I have reviewed the screenshots and document you shared, and I believe that the configuration process you have followed is comprehensive and meets the requirements you outlined. However, I would like to emphasize the importance of thorough testing before deploying any changes to production. Testing should be done in a controlled environment to ensure that users have the appropriate level of access to the mobile channel and the necessary functionality. This includes testing access groups and portals for all relevant roles and user groups to ensure that they are working properly and meeting the requirements.
If you encounter any specific challenges or issues during the configuration process or after deployment, I recommend reaching out to the Pega support team for further assistance. They are equipped to provide additional guidance and support as needed.
I hope this helps and I am here for support for further clarification is needed.