"Restricted by Access Control" in Mobile Agent list - only on one instance

Davor Matijasev
Tera Expert

Hello!

 

We are building a scoped mobile app that runs in Mobile Agent. It worked fine on our Dev instance but once we moved it to the Test instance, we are seeing "Restricted by Access Control" "records" in the list view. The list is filtered by assignment - it should only show items assigned to the user that is logged in - and those records are displayed correctly, but the app seems to show a "Restricted" block for every other record in the table that doesn't fit the filtering criteria. The users generally have access to these records and can normally see them (and self-assign them) in the backend but in the mobile app they are seeing these messages instead of the records.

 

Clearing the cache seems to help for a bit but after a while the issue is back. We are very reluctant to ask users to clear the app cache, as we are not sure that half-filled forms won't lose the data. Also, for admin users nothing seems to help - not even sure how is that possible since we should be able to see everything.

 

I've seen some old posts related to this issue but they are out of date and don't seem to help. There are also no before query BRs on this table, as some KB articles seem to indicate might cause the issue. We are opening a case with ServiceNow but are not holding our breath ...

 

Thank you all for your answers!

1 ACCEPTED SOLUTION

Davor Matijasev
Tera Expert

Turns out the solution was a bit of a letdown. We configured condition filter in the List item config instead of in the Data item. Once this was moved, the issue was resolved. Still doesn't explain why it only happened on one instance but all's well that ends well, I guess.

View solution in original post

1 REPLY 1

Davor Matijasev
Tera Expert

Turns out the solution was a bit of a letdown. We configured condition filter in the List item config instead of in the Data item. Once this was moved, the issue was resolved. Still doesn't explain why it only happened on one instance but all's well that ends well, I guess.