Catalog item secured to a group. Need requested by variable to see all users

[ryan_kelly]

I have a catalog item that is secured to one of our teams via the 'Available For' tab on the catalog item.

Since the item is secured, the 'Requested For' variable doesn't see all users and you get an error 'item is unavailable for this user' when selecting users outside the group.  Is there any way to allow the Requested For variable to see all users and resolve the error I mentioned while the CI is secured?  When I remove the security via the 'Available For' tab, the issue goes away.

[Community Alums]

Hi @ryan_kelly ,

If you are restricting catalog item via "Available for" then only those who are allowed will be able to see that catalog item. For remaining users that catalog item won't be visible & it will give that error.

Ex: Here I am saying this catalog item should be visible & accessible only to "Analytics Settings Managers" group. 

If someone from "Analytics Settings Managers" tries to access catalog item, there won't be any issue.

If anyone apart from "Analytics Settings Managers" group tries to access this catalog item it will give the below error.

Please elaborate your requirement if my response isn't helpful.

I started answering community questions recently. If my answer helped you in any way, please mark it as helpful or correct. It would be a great boost.

[jMarshal]

I have experienced this with User Criteria on Catalog Items as well, and the only solution I have been able to come up with is to use an intermediate field (specific to this catalog item) and a UI Policy (to hide the other "requested for" variable and show the intermediate field) and a BR to update the "real field" with the value from the intermediate variable that I created on the item, along with the associated "requested_for" and "request.requested_for" field(s), if appropriate, depending on your Service Catalog model (sometimes the RITM requestor is different from the REQ requestor, intentionally). The intermediate variable is just a reference to sys_user with no conditions or ref qualifiers. The BR triggers on create of a new RITM and executes before insert.

[Luiz Lucena]

I was about to mention that as well, when I saw your reply.

User criteria would be better in the scenario described.

[jMarshal]

They say "great minds think alike" 😉 😎