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?

[kimberlynealy]

Let me restate the entire solution I am looking for. I apologize for not being clear the first time. 

I need a flow created in flow designer that will create 2 task when the request is open - each task is for a different team. However, there is a 3rd task that is create if the first 2 task are closed complete. If either one of the first 2 task are closed cancelled or closed skipped, the 3rd task will not be created. If both of the first 2 task are both closed complete the 3rd task is created. 

I tried this with creating 2 task in parallel but it didn't work. I even used a look up records action but still the ritm did not go to request cancelled. So then I created the 2 task individually with a wait condition to see if either task state was changed to closed cancelled or skipped and if not the 3rd task would be added to the RITM but when I tested and change the state of one of the 2 task to closed cancelled the RITM stage did not change to request cancelled as expected. Note: the 3rd task can only be created if both of the initial task are closed complete. 

[Shubham_90]

Hi  @kimberlynealy 
I'm Facing the same issue. If you are already implemented please help me out here.
Thank you!!

[kimberlynealy]

SN presented a workaround that removes the 'Do this in Parallel' flow logic and instead create separate task but DO NOT have Wait checked. I also used "Wait for conditions" for each assignment group assigned a task. However; when tested, I noticed the request is approved and the flow moves directly to request cancelled before any task are open. I then decided to remove the Request Cancelled stages and I added the update record action to update the stage. I tested a lot for each scenario (closed cancelled, approval rejected, 1 closed complete 1 closed cancelled; both closed complete) and stages updated appropriately. Although this may not be the case for you; but while testing often times I noticed the stage field might stay at fulfillment, but after waiting a short wait (less than a minute) the stage field goes blank, then after refreshing the browser the correct stage appears.  ...again, this was my experience and may not happen on your end. Also, a problem record was created - PRB1752255 and should be followed to track fix details.

Here is Flow Designer of one of my catalog items I used the work-around on. 

Let me know if this worked for you

[Mathew Hillyard]

Hi @kimberlynealy,

This is the Data Foundations CSDM Forum. You will get a wider audience if you post in the Developer forum.

[kimberlynealy]

How is that done when the question is here?