Automated flow parity with classic CDS for Apps workflows
These release notes describe functionality that may not have been released yet. To see when this functionality is planned to release, please review What's new and planned for Microsoft Flow. Delivery timelines and projected functionality may change or may not ship (see Microsoft policy).
Automated flows will, over time, replace the existing Classic Common Data Service (CDS) for Apps workflows (formerly known as Dynamics workflow). With this release, it is now possible to accomplish all scenarios that asynchronous classic CDS for Apps workflows supported with automated flows. Several capabilities, including action support and batching support, are covered elsewhere in the release notes. Here's a list of the new features in automated flows:
- Provide filters to triggers: You can control exactly which records trigger your automated flows. By including triggers in the middle of flows, you can leverage them as Wait conditions inside of a flow.
- Run As capabilities: Automated flows that are triggered by CDS for Apps can run with either an account defined by the owner of the flow, or with the identity of the user who performed the change that caused the trigger.
- Resume flows from a failed action: If a flow fails on an action, makers can resume the flow right from that action once they’ve repaired the error.
- Support for multiple trigger types: Flows can now both be automated (triggered by events in the system), and instant (triggered on-demand) at the same time.
- Call other flows: Flows can now call other flows and pass parameters to them.
Finally, we are also providing migration guidance for our customers, although there is no automatic migration at this time.