- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-20-2014 12:11 PM
Hi all,
I have been trying to find a way to populate the RITM 'Assigned To' field with the Request's 'Assigned To' info. Basically when someone submits an order guide via the Service Catalog a request is created and the 'Assignment Group' field on the request gets populated via an assignment rule. When a person from that assignment group sees the request come in and they decides to work that request, they then assign that request to themselves. It is at this point in time, that I want the RITM's attached to that request to update its 'Assigned To' field automatically with the same user information that is in the Request's 'Assigned To' field.
Overall, I am trying to eliminate the need for the service desk person to assign both the request and the RITM's manually. If they can assign it to themselves once via the request and have that information trickle down to its child(ren) (RITM(s)) that would be awesome !
Is this even possible? I am not a developer, thus I cannot code. If this is possible via code can you please attach the necessary script I will need to use.
Thanks a bunch!
Solved! Go to Solution.
- Labels:
-
Ask the Expert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2014 09:50 AM
Hi Niccole,
My mistake, try this instead:
action.setRedirectURL(current);

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2014 12:05 AM
as suggested by Kenneth Pruitt using a Business rule approach automates the effort... and yes, if needed they can reassign the RITM back to someone...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2014 10:57 AM
Hi Nicole, since I'm not familiar with your request fulfillment process my first question would be do all request items get completed by the same team regardless of request? Or is this based on a specific type of request like an onboarding activity? If you go the business rule route it may apply to all requests which may not be the desired behavior.