Closing a catalog task when another catalog task is closed in flow designer

[kimberlynealy]

I am trying to create a flow designer flow for a catalog item that creates 2 catalog task in parallel but if one of the task is closed cancelled or closed skipped, the other task is closed incomplete and the RITM stage changes to Request Cancelled. I've tried to create the task in parallel and also individually with wait as false. 

What is the best practice. Do I create each catalog task as a separate action or is it best to create them in parallel? I tried both but I can't seem to get the request to cancel if one of the task is closed cancelled. 

Any ideas to fix this problem?

[Ravi Peddineni]

@kimberlynealy 

The request stage depends on the Catalog tasks. OOTB, you don't have to set the state request. Once both the catalog tasks are set to closed complete or closed skipped or closed incomplete, request state will be set automatically. So take care of the catalog task state. 

For the flow, yes create the catalog tasks in parallel and wait until one of them are in one of them is set to closed states mentioned (make sure the wait is in main branch of the flow). Then if the OTTB rules are not setting the request state for some reason, you can just add a step to update the states of RITM and REQ.

[Sirri]

@Ravi Peddineni ,

please check if In RITM Below catalog task(sctask) any one is state in cancel the whole ritm set cancel is there any script running for that check that script.

[kimberlynealy]

Not using any script

[SebastianKunzke]

Hey,
That is an interesting question. The following should work:
1. Create both task without waiting

2. Do an in parallel

2.1 wait for condition task = skipped

2.2 update the other record

3. Update requested item and include the stage "cancelled"

The execution looks like that:

The stop variable is needed, that you do not update the record twice and that you can use the same flow for the successful execution. 

Kind regards
Sebastian