Different RITMs in same Request using a Flow

[FSTA]

I need to create an RITM for a different item under the same REQ.

We have created two catalog items. Let's call them Item A and Item B. They are both available separately, and have their own flow, trigger by a service catalog request. However, when requesting Item A, the user can request Item B at the same time.

In the flow for Item A, I tried creating an RITM record for Item B and passed the REQ to the new RITM. That also triggered the flow for Item B, creating an unwanted REQ.

I tried the "Submit Catalog Item Request" action instead, which triggers the flow for item B, which is what I want, but it still creates an unwanted REQ.

Is there any way to trigger the catalog item from Item A's flow without creating an REQ?

[Ankur Bawiskar]

@FSTA 

it will create that unwanted REQ as you are using "Submit Catalog Item Request" flow action

You can do this

1) cancel that unwanted REQ

2) link the new RITM with the existing REQ

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

[Bidduam]

This post might assist:

Solved: Issues with Flow update and delete record actions - ServiceNow Community

[FSTA · Accepted solution]

Thank you @Ankur Bawiskar and @Bidduam for your replies. However, theses solutions do not prevent the creation of a request. This would pollute the data, which is unacceptable in our case.

Instead, I created a third item called "Item B (via Item A)". It is identical to Item B, without a flow. In the flow for Item A, I create an RITM record for "Item B (via Item A)" and link it to the REQ for Item A. The downside of this solution is the duplication of some code, but most of it can be put in a subflow that can be called in this case as well as for standalone Item B.

[Bidduam]

@FSTA 

You could create an order guide, ultimately, they are used for exactly what you are doing.

You create both catalog items separately, with their own separate flows if wanted/needed.

They can still be made available in your service catalog individually if you want, or you can choose to 'hide' the individual options and only make the order guide available.

In the order guide you can share variables and therefore share the data the user enters between the two forms (meaning if the user wants to submit both, they only have to enter the information once in those shared fields)

They can still use the order guide to just make one of the requests if they don't need both at the time.

When they request both at the same time through the order guide, you will get a single request with both RITM's underneath and sc_tasks and approvals under the respective RITM's based on the flows they have.

Only the one Request ticket is created in this circumstance.

So under Service Catalog >> Catalog Definitions >> Order Guides, select New

This is how they can end up looking:

Service Portal / Employee Center

The order guide:

Items can be selected or unselected if not wanting to request all

When both are selected and Next has been clicked:

Once submitted, two RITMs are created under the one Request: