How do I prevent the "Rows removed by security constraint: x" Message from being displayed?

[cybernetic_crab]

In this Knowledgebase article, the author recommends to build an On Before Query Business Rule to filter the records that should not be displayed, so the list renderer would not have to decide wether the record should be displayed. Now I don't fully understand how to code the script for this rule, as any Queries on the current GlideRecord object would trigger the Script to be run again.

The problem that I am facing is that we have to separate groups working on Security Incidents, and neither should have access to the other's data. After implementing the access restriction, the users now see the message "Rows removed by security constraint: x". What I would like them to see is their own data, without the message and any hidden rows. The current implementation is not user friendly:

[Chuck Tomasi]

Hi Leon,

Try a before query BR that simply does this...

current.canRead();

[cybernetic_crab]

Hi Chuck,

I tried the solution you proposed, it didn't change the behavior.

Won't this simply return a true into the ether? I thought you'd have to use at least something like .addQuery() to modify what is returned by the query.

[Chuck Tomasi]

You are right. Let me think on this a bit more.

[cybernetic_crab]

I tried to filter by adding .addQuery("assignment_group", "value"), but it did not work as expected, returns an empty list..

[Chuck Tomasi]

Hi Leon,

I'm still working on this. I just had another thought. You may want to be aware that this has performance risks...

For every row you want to display, your before/query BR is going to read the group membership table and that's a lot of queries for every row to display, multiplied times the number of rows. See where this is going?

My question - how imperative is this to remove the message?