- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2021 08:06 AM
We have a catalog item that can be requested for any user but only a subset of users (user criteria = Group A) can fill out/submit. When a member of Group A fills out the form they want to enter a user into the Requested For variable a user who is not a member of Group A but they receive an error "Item is unavailable for this user". Is there a way to limit who can submit a catalog item without affecting the ability to list users for the Requested For field?
I did see one posting here but assumes the business process can be changed, which ours can't.
Solved! Go to Solution.
- Labels:
-
Service Catalog
- 5,608 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-06-2021 06:54 AM
You are correct that I am using the Requested For field type, however, the issue appears to have been anticipated by SN so they included an OOB workaround for it; I exposed the Access Type field on my catalog item record and updated the value from Restricted to Delegated. Now my ESS user can't see the item (via browse or search) but they can have their user record entered into the Requested For field, which was the goal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2021 10:31 AM
Hi Tim,
It sounds like your Requested For variable has the type of Requested For? This is one of the 'features' of this variable type that would be tough to circumvent, if it's even possible. The best thing to do in this scenario is use a variable with the Reference type and sys_user as the reference table, then put whatever reference qualifier you need on it, if any - probably at least active is true. If you want it to default to the current user, but this in the Default Value.
javascript: gs.getUserID()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-05-2021 04:23 PM
Were you able to test this solution to see if it meets your requirements?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-06-2021 06:54 AM
You are correct that I am using the Requested For field type, however, the issue appears to have been anticipated by SN so they included an OOB workaround for it; I exposed the Access Type field on my catalog item record and updated the value from Restricted to Delegated. Now my ESS user can't see the item (via browse or search) but they can have their user record entered into the Requested For field, which was the goal.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2021 11:22 AM
Awesome solution, was having the same issue. For anyone looking into this, there is a field on the catalog item called "access type" that is set by default to "restricted" (which you don't see on the default form view). I added this field to the form so I can edit it. Change the field value shown below to "delegated" and it should work as intended.