How to detect query_range ACL errors using ATF?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6 hours ago
Hi everyone,
I’m currently trying to detect query_range ACL issues using ATF.
What I observed:
- When using a non-admin user in the list view and applying certain filters (e.g. contains / LIKE), a query_range warning appears in the UI.
- However, when I try to simulate similar queries server-side using GlideRecord (e.g. addEncodedQuery), everything executes without errors.
So it seems like:
- The UI detects a restriction (query_range warning)
- Server-side scripts do not reflect this behavior
My questions:
- Is query_range only enforced or detectable in the list UI context?
- Is there any way to detect these restrictions server-side?
- How would you typically test this in ATF?
Thanks!
