- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hello All,
I am looking for a solution, where the requirement is to add multiple RITM's under same REQ for the same Catalog Item. For example, User want to request for various Softwares (like Adobe, iTunes) in a single Request. Like, the user wants to select multiple from a list, and the respective approvals should trigger and follow their own flow.
Order guide didn't work for us, as it can collect different RITM's under one REQ, like request for emailID, software and Hardware. But Our requirement is to add same Catalog Item, multiple times under same REQ.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago - last edited 4 weeks ago
Hi @Vijaya_Mnpram ,
Yes, your understanding is correct.....
When a Catalog Item is used as the trigger, ServiceNow will always create one default RITM for that item (for example: Software Request).
So if, inside the flow, you also create RITMs for Adobe and iTunes, then you will end up with:
1 RITM → Software Request (auto-created)
1 RITM → Adobe
1 RITM → iTunes
All of them will be under the same REQ.
If you found my solution helpful, please mark it as Helpful or Accepted Solution...!
thanks,
tejas
Email: adhalraotejas1018@gmail.com
LinkedIn: https://www.linkedin.com/in/tejas1018
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hi @Vijaya_Mnpram ,
1) Create one Catalog Item (example: Software Request) .Add a List Collector variable to select multiple softwares
2) create the flow -> Trigger: service catalogue and attach flow to catalogue item
3) In the flow, read the catalog variables . Store the selected software list
4) Use For Each loop -> Loop through each selected software
Inside the loop: configure the flow like this
If software = Adobe → Send approval to Adobe approver group
- Else if software = iTunes → Send approval to iTunes approver group
Same logic can be extended for other softwares
aslo
(if you want to create the separate RTIM's then
in loop if software = adobe then using the create record flow action you can create RITM record under that REQ )
If you want, I can give youu the Flow logic in more details
If you found my solution helpful, please mark it as Helpful or Accepted Solution...!
thanks,
tejas
Email: adhalraotejas1018@gmail.com
LinkedIn: https://www.linkedin.com/in/tejas1018
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
@Tejas Adhalrao Thanks for suggesting these approaches.
First approach is clear.
For the second approach of creating RITMs, there will be an automatic RITM created when the Catalog Item is used as a trigger. So, if we create different RITM's under same Request, then there will be one for 'Software', another for 'Adobe' and another for 'iTunes'.
Is my understanding correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago - last edited 4 weeks ago
Hi @Vijaya_Mnpram ,
Yes, your understanding is correct.....
When a Catalog Item is used as the trigger, ServiceNow will always create one default RITM for that item (for example: Software Request).
So if, inside the flow, you also create RITMs for Adobe and iTunes, then you will end up with:
1 RITM → Software Request (auto-created)
1 RITM → Adobe
1 RITM → iTunes
All of them will be under the same REQ.
If you found my solution helpful, please mark it as Helpful or Accepted Solution...!
thanks,
tejas
Email: adhalraotejas1018@gmail.com
LinkedIn: https://www.linkedin.com/in/tejas1018
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@Tejas Adhalrao Thanks for your thoughts. Only problem is that there is no relationship between default RITM and created one. There is a chance that, the default RITM might be left out -> might make the REQ left out in open.
I am going with the first approach, where the workflow flows for each one of the list of softwares, triggering respective approvals.
Appreciate your effort in suggesting all these.
