List view with records not displayed due to ACL restriction - bad user experiance

[Zod]

Hi Experts,

when ACLs do not allow records to be listed, a message will show up at the botton telling how many records are not displayed. Ok so far ...

BUT .. in case there are only a view records to be visible and many are not ... it could lead to misunderstanding of the records available.

Example.

> List is set to show 200 Records > Picture 1

> List set to show only 15 records per page > Picture 2

Get my point?

The user does not know how to sort to see all records ... as the logic of which records are not displayed is not transparent for him.

I would expect the system to show all visible records in line with the sorting .. and independently show the message of how many records are not displayed due to security reasons ...

Any idea how to fix this to me more user friendly?

[John Diaz]

Thank you for asking this. I've been wondering this for a LONG time. Really curious to see if anyone has gotten around this.

Possibly a query business rule instead of ACL? Seems counter productive though...

[darlawolf · Accepted solution]

You will need to modify the OOB before query Business Rule below (my recommendation is to turn the OOB off and create a new one) to incorporate the changes done on the ACL side.

[Zod]

.. this would give a new message, but still not show all visible records at once ... at least I would not see why this should change due to the code provided.

[darlawolf]

If you impersonate a non-roled user and go to incident.list they do not get a Security constraint message. This is due to the OOB business rule above. Just sharing what I have done for other clients whenever they want extensive ACLs I also include a before query BR to hide that security constraint message.