- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2022 06:23 PM
We already have before query business rule for task table. if I write before query business rule for RITM/ catalog tasks, then does new rule overrides rule from task table. Appreciate input.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2022 07:06 PM
Hello,
The child table query business rule does NOT override the parent query business rule.
In fact, both the parent query business rule and the child query business rule will run. So it'll merge the two queries together, which could provide mixed results than what you want.
The best practice would be to not put a query business rule all the way up at the parent level, if you can avoid it. If you must do that, then you'd want to adjust the parent query business rule to not run on specific tables that are relevant to you (i.e., perhaps on a child table where you now have your own query BR).
To do this, you'd want to add this condition to the parent query BR, for example:
current.getTableName() != 'incident'
This would prevent the parent table query BR from executing on incident records and allow just the incident query BR to run and process.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2022 06:39 PM
Hi,
Business Rule are inherited, but if you write a new rule on your child table it should override the parent one.
Also you can put a filter on your Parent BR to ensure it does not run for that Child Table say a filter as Task Type is Not Requested Item Table
What is the issue you are facing?
Hope this helps. Please mark the answer as correct/helpful based on impact.
Regards,
Shloke
Regards,
Shloke

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-05-2022 07:06 PM
Hello,
The child table query business rule does NOT override the parent query business rule.
In fact, both the parent query business rule and the child query business rule will run. So it'll merge the two queries together, which could provide mixed results than what you want.
The best practice would be to not put a query business rule all the way up at the parent level, if you can avoid it. If you must do that, then you'd want to adjust the parent query business rule to not run on specific tables that are relevant to you (i.e., perhaps on a child table where you now have your own query BR).
To do this, you'd want to add this condition to the parent query BR, for example:
current.getTableName() != 'incident'
This would prevent the parent table query BR from executing on incident records and allow just the incident query BR to run and process.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-10-2022 06:47 AM
To identify the business rules and flows that run on a record when inserting, updating, deleting, displaying or querying the record the DevTools' WhatRuns button comes in handy.
As the name suggests it shows you what runs on a record (including business rules on parent tables).
DevTools contains a truckload of re-usable functions and features for developers.
Fork at will: