Today in automation workflows you can only and conditions to flows that pass previous conditions. It would be helpful to be able to add conditions to the flows that stem from failing previous conditions.
Scenario:
I want automation to change the status of a task based on it's Target (completion) Date and it's Actual Completion Date not being filled in (i.e. the task is still open). I want it to change the status to one of two values, or leave the status alone depending on the values in these fields. Today I use two separate automations to complete this but they're all based on the same fields.
Workflow 1 changes the status if the Actual Completion Date is blank and if the Target Date is today or in the past.
Workflow 2 changes the status if the Actual Completion Date is blank and if the Target Date is not today, but is in the next 4 days.
I'd like the ability to combine these into one automation workflow since the context is related and all the fields being referenced are the same.
If the values in the fields lead to a failed result for if the Actual Completion Date is blank and if the Target Date is today or in the past, then I would like to put a condition in the flow that branches off due to the failed result. That condition would be if the Actual Completion Date is blank and if the Target Date is not today, but is in the next 4 days, then change status to the second state.
This would save time when reviewing and troubleshooting. It prevents having to go in and out of workflows to look at other workflows to confirm:
- Do I have the second state accounted for in another workflow?
- Do I have all the same fields included in both and corresponding condition set correctly?
- Have I accounted for the same thing twice?
