- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2022 02:28 AM
Hi all,
We're trying to restrict certain Requested Items from being viewable by all, instead we want to lock the records down to users with a certain role.
We have the following ACL rule which works fine in hiding most of the variables on the RITM form. And there is an additional Catalog Client Script which will hide the variables from users that do not have the specific role.
However I'm having issues hiding the records from the Requested Items list view as you can see below
These fields are also still visible on the RITM record too. My thought was that perhaps these are pulled through from the REQ record but I can't see them on the XML for them (Item - cat_item at least).
My question really I guess is - Because these fields are not hidden that's why it's still showing in the list view? If I can hide these then it will disappear? Additionally, is there an alternative approach where I can ensure that these records are not returned for all users - Ideally without adding a filter to the list?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2022 02:48 AM
Hi,
The Precedence goes like this
Table (sc_req_item.none)
All fields (sc_req_item.*)
Specific fields(sc_req_item.item)
Now You have locked it at all fields level but there are other specific field levels that user is still passes.
Here you have to decide that the fields visible to user, is that critical enough to hide, if not you can let it be. Otherwise, you will have to edit those field level ACLs as well which will be a big job.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2022 02:41 AM
Hello,
Hiding Records on List View you need to use Before Query BR. Refer below thread.
if answer is helpful mark as helpful or correct.
Regards,
Vaishnavi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2022 02:48 AM
Hi,
The Precedence goes like this
Table (sc_req_item.none)
All fields (sc_req_item.*)
Specific fields(sc_req_item.item)
Now You have locked it at all fields level but there are other specific field levels that user is still passes.
Here you have to decide that the fields visible to user, is that critical enough to hide, if not you can let it be. Otherwise, you will have to edit those field level ACLs as well which will be a big job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2022 04:14 AM
Thank you Anurag - I followed your solution. Increasing the ACL to run on the table level (and then exclude the catalog item from already existing table-level ACL's) has done the job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2022 02:49 AM
Hello,
Do you want to hide certain RITM for the list view then you can use before query business rule.
Please check the below article for the same:-
Please mark my answer as correct based on Impact.