- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-27-2024 01:26 PM
When I add a 'Requested for' variable to a form so that multiple 'requested for' users can be added to a single request (with separate RITMs for each requested for user), I receive the error below:
'Item is unavailable for this user'
I see this error only when I select a 'Requested for' user that doesn't have access to submit requests. However, we want to be able to submit requests for any active user, and not all users have privileges to submit all requests.
Has anyone else seen this issue? Were you able to find a fix?
Thanks in advance 🙂
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-28-2024 07:26 AM
Thank you for this info!
I dug through a lot of documentation on this, and finally found a solution:
If you follow the link above, and search for 'Requested for', there is a reference to the 'Access Type' field on catalog items:
- You can submit the request for a user based on access to a catalog item. The Access Type field of the catalog item can be used to specify if a request can be submitted for a user who does not have access to the catalog item.
When I added the 'Access Type' field to the catalog item I was working on, and set this variable value to 'Delegated' from 'Restricted', it enabled the ability to submit the request on behalf of users who don't have the ability to submit that request themselves.
I hope you have a wonderful week!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-27-2024 02:20 PM
did you try to replace your variable requested for type with variable requested for but reference type (to table sys_user) ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-27-2024 03:23 PM
Yes I have.
Doing this does allow me to select any user from the sys_user table, however there are a couple other issues with this process.
The first is that this does not update the 'requested_for' field tied to the service request. Our approvals, emails, and many references in task short descriptions, etc. all reference the 'Requested for' user tied to the RITM. We're wanting to update that field based on the field added to the form.
- I do believe it would be possible to create an 'onSubmit' catalog client script using GlideAjax to access the requested_for field on the RITM, and update it to match what is entered into the reference field we create. But I haven't done this before and might need a little guidance to get that to work correctly.
The second piece is that we are wanting to be able to submit a single request for multiple 'Requested for' users. The 'Requested For' field gives us the ability to submit a single request for multiple users, and then separate RITMs are created for each user selected. I don't believe we would be able to accomplish this with a reference field... at least not without some fancy customization.
Thank you for the help 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-27-2024 03:38 PM
yes, multiple users for requested for is a feature for requested for type 🙂
could you create user criteria for all active users and assign to your item?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-27-2024 03:52 PM
I did test this as well, and it works, but then non-requesters are able to submit this request. We have a standard to only allow certain people to submit requests, and don't want to open that up to people who we haven't granted those permissions to.
Thank you