Create a Requested Item for an existing Catalog Request using Flow Designer

John Tomko
Tera Expert

I can think of a couple of workarounds for the following issue, but wanted to know if I'm missing the "right way" to do things...

I am building a flow that needs to generate a number of Requested Items based on a condition.  Because the condition will produce different results depending on when the flow is run, I need to do a For Each loop to generate Requested Items.  Easy enough.

Early in my flow I am creating a shell Catalog Request.  When I generate each Requested Item using the OOTB "Submit Catalog Item Request" action, the Requested Item is created.  However, a separate Catalog Request is created for each, when I really want each Requested Item to be associated with that shell Catalog Request.

I'm sure I can build my own action based on the Cart API, or I can write an action to change the Request on each of the Requested Items to the Shell Catalog Request and then delete the Catalog Request that was generated automatically and is no longer associated with the Requested Item, but this seems like the kind of thing that should be supported out of the box.

Any thoughts?

Thanks

 

1 REPLY 1

OlaN
Giga Sage
Giga Sage

Hi,

I have seen questions like this one  couple of times before, but can't recall if there is a golden solution for this use case.

Consider how the process of a REQ/RITM is built OOB.
You might have approvals happening on the REQ, before starting any RITM.
You might have approvals happening on the RITM, because there might be costs connected to the RITM.

If you were to create additional RITM based on a variable, then you may have bypassed the approval process, because when the initial REQ is created the user approving it will see only the initial RITM connected and that requires approval.
Then, after the approval has been approved, suddenly there are additional RITMs connected to the REQ, with perhaps additional cost associated, which now has been approved without the approval taking place.

Is that an appropriate behaviour?

Might be that I'm missing something obvious here, but this is my understanding so far.