When Creating Multiple RITMs through flow designer after submittal, how to deal with original RITM

[Mark Brogna]

When I use flow designer to create additional RITMs from a list collector variable found on my catalog item, I still have the original RITM that is created out of the box. How do I deal with this?

In my example I want a ritm for each business service.

However, upon submittal i have the original ritm (RITM0010028), plus the two defined (RITM0010029, RITM0010030) in the list collector. Is there a way to suppress the original ritm from being created or would I have to delete it?

[Collin Romeijn]

Hi Mark,

why are you making RITM's for these "sub tasks" and not just using sc_task records to perform the needed processteps?

OOTB logic is request -> requested item -> Service Catalog tasks.

Because before you even trigger the flow a RITM will be created when you submit a Catalog item.

[Mark Brogna]

I want each item to operate independently as three tasks will be assigned.

If task 1 is finished for the first business service, it should move to task 2. Whereas the second business service will still be at task 1.

If for any reason a task is rejected, it would only affect one business service and not the other.

[Ankur Bawiskar]

@Mark Brogna 

you can close that RITM and REQ after the new RITMs are created.

If my response helped please mark it correct and close the thread so that it benefits future readers.