Has anyone used Decision tables for access restriction like we do for a query BR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2024 01:12 PM
I am exploring Decision tables to see if we can use them for restricting visibility access. We usually write a query BR or a display BR to filter out some records based on assignment group or Category. Wanted to see if anyone has handled this through Decision tables?
Use Case:
For the incident table, display records for the user to show only when Category = IT and the assignment group = IT Service Desk and not show any of the other category or assignment group data.
Has anyone tried it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-13-2024 06:49 AM
Hi @Varun Sai,
Decision Tables are primarily used for evaluating conditions and determining outcomes, such as routing workflows or managing approvals, rather than controlling record visibility.
In summary, Decision Tables are not intended for restricting user access to records.
Access Control (ACLs) is the most suitable and effective method to manage which records users can view. As you mentioned, Query Business Rules can also be utilized to control record visibility.
If this resolves your issue, kindly mark it as Correct If you find my response
helpful, please mark it as Helpful based on its impact.
Best regards,
Moin