Forum Discussion
Capabilities of Flow (as compared to SP Designer)
I think as I understand it Flow is the next evolution of SharePoint Designer Workflows? I have yet to have time to really dive into Flow, but in order to consider eventually upgrading solutions a...
Mmm...I think the discussion should be also around how Flow will eventually replace SharePoint Online Legacy Workflow and Windows Azure Workflow....any thing you can share? I would like also to know if there are plans to support "State machine" concept in Flow
Juan Carlos, apologies for the delay in response. Do you have some time this week to chat about how you use "state machines" and "SPO Legacy workflows"? Could you please email me directly with your availability? My email is mhade [at] microsoft [dot] com.
Merwan, I'd be curious to know how Flow will support any sort of realistic approval process if it doesn't support state machine workflows. That's the primary way these sorts of workflows have been built, that I've seen. Even in 2010 based workflows that didn't officially support "state machine" workflows, we'd build the workflow to mimic that functionality to support the requirements for a multi-level approval process.
- Already sent an e-mail to you :-)...by the way: To me, scenarios that involve the use of a state machine workflow vs. a sequential ones are those where depending on a condition, the user could be redirected to a previous stage a not the next one that is what typically happens in sequential workflows.
