Query business rule is being executed multiple times

[sreedharkaliset]

Hi All,

I have written a query business to restrict record access based on few conditions. While testing, i found that business rule is being executed multiple times for a single incident record. Could you please help me understand why.

Regards,

Sreedhar

[Jim Coyne]

If the intention is to only run on Incidents, you should then set it to run on Incident and not on Task with a condition.  Otherwise the condition has to be evaluated for every single Task record, and there will be quite a few of those  🙂

Every single thing in the platform should be designed and built with performance in mind.

[The SN Nerd]

 If you really want to get to the bottom of this, check all display business rules on Task.

There will be one rule with a GlideRecord Query, which in turn is running the Query rule.

Every time you run .query() function on GlideRecord object, all Query Business Rules will are triggered to add or modify that query.

If you add this code below, you will likely see two different queries in your output:

gs.addInfoMessage( current.getEncodedQuery() );

I think you may misunderstand what a before Query rule is.

"current" in the context of a query rule does not have a sys_class_name populated. 

[The SN Nerd]

Example:

[sreedharkaliset]

Thanks Paul.

Add info message for encoded query is returning same as shown in above screenshot but I don't understand why these business rules are being executed when I open business rules and or any other module in the instance.

Please help.

Regards,

Sreedhar

[The SN Nerd]

This isn't actually an issue though, there is nothing wrong with a Query rule running more than once when any given page loads.

It just means there is another query on task happening when the page is loading.

It could be that a UI condition runs code that does a database query, or a display business rule. But it doesn't actually matter.