How to Auto Close Incomplete a Request if a Catalog Task is Closed Incomplete

[terrieb]

Back in Workflows, you could add conditions to all tasks of Closed Incomplete or Closed Complete state.  If the task was Closed Incomplete, then the Request/RITM would go to Closed Incomplete state.  If the task was Closed Complete, then it would move to the next task in the flow.  This was very useful if there were multiple tasks in a workflow, especially when using the Branch/Join function.

However, in the new Flow Design, the only option you have is the "Wait for" condition to put in that option.  And then you have to include an "If" action if the state is Closed Incomplete to make the state of the Request/RITM Closed Incomplete.

This is very cumbersome, especially if there are multiple tasks and it could be a task that is NOT the last task, that is marked Closed Incomplete, so now the admin has to go and either Cancel the Request to close both Request/RITM or manually change the state on both tables.

If there a way we can do this without the Flow Activities?  I have tried a BR and UI Policy but they don't work.

Thanks!

[terrieb]

Unfortunately, it's still now working.  However I may have missed something in the BR (see attachment).  I closed a task as Closed Incomplete, and the flow continued, creating the next task instead of closing the RITM.

[Ankur Bawiskar]

@terrieb 

you will still require your flow or workflow to wait and check the state of previous task so that you can move to next task

If you are using flow then that's the only option.

Why are you planning to use BR for this?

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

[terrieb]

Because the flow has a lot of tasks that open at the same time, but there is no definite "last task" to use the wait for condition.  We end up with "orphan" tasks that way, which is why I was asking for a BR as I heard that was the way to go in these types of situations.

Thank you.