Create multiple RITM's at once in Service Portal using list of emails

[stanty]

Is there a way to create multiple RITM's under one REQ at once in Service Portal using a list of emails.

Please note that we have 'Enable also request for' in the Requested For variable and that is allowing us to submit multiple RITM's at once however we have to select each user at one time. We want to search multiple users using a list of emails and then submit one RITM per user under one REQ similar to what 'Also Request For' feature does.

[Matthew Green2]

Out of the box, “Also request for” cannot take a bulk email list—you’ll need a small customization.
Typical pattern: add a multi-line “email list” variable, then use a server-side catalog script / Flow / BR to parse the emails, look up users, and programmatically create one RITM per user under the same REQ.

[Ankur Bawiskar]

@stanty 

no out of the box way available

in your main flow configured on your catalog item you can iterate and use "Submit Catalog Item Request" flow action

see this link where I shared solution for something similar and enhance it

Create multiple RITM based on data in MRVS using Flow Designer 

OR

check my blog and enhance

Multiple RITMs in same Request Using CartAPI 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Ankur Bawiskar]

@stanty 

Thank you for marking my response as helpful.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[stanty]

So the scenario with me is I cant create a new flow for this. I have a generic flow for all the catalog items and then two subflows are calling script includes where the logic is written that what approvals (defined in a custom table) and tasks (defined in another custom table) need to be generated if a particular cat item is submitted so all the cat items have this same flow as the process engine. We have designed this to avoid customizing flows individually for each cat item. So while creating any new item, we create the cat item, add the flow, and then create records for approval and task in the above mentioned table.