Could not load the document - MOBILE APP CONFIG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2023 01:55 AM - edited ‎11-09-2023 01:58 AM
In the Mobile Agent Incident section added a new launcher section to show All P1 and P2 incidents restricting access using role. The new section is working properly and users are able to view all data.
For Group Incidents all existing list screen having had multiple screen segments started showing errors for users that have records to be displayed.If user did not have any record no error displayed.
Any insight into the issue will be helpful.
Error receiving:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-20-2023 09:03 AM
hello Ayushi,
I see the error because of the new lau ncher section for p1, p2 incidents. looks like new section restricitng the role, whcih is causing the issues fir users have records to be displayed in existing list screen for gorup incidents,
When a user tries to access the list screen for group incidents, they are being granted access through the new launcher section, which is restricting access based on their role. However, the existing list screens are not aware of this role-based restriction and are still trying to display all records to all users. This is causing the errors you're seeing.
To resolve this issue, you will need to modify the existing list screens for group incidents so that they are aware of the role-based restriction. You can do this by adding a filter to the list screens that restricts the records to those that the user has access to.
PaulSylo
Kindly mark "helpful", if this helps, or Mark as "Accepted " if it solves your issues !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-21-2023 10:26 PM - edited ‎12-21-2023 10:31 PM
For future reference, the error was not due to the introduction of new section. The error received in Group Incident section was due to the two Steam M2M segments attached in screens. When only one Steam M2M segment is attached to screens the error is resolved.