Microsoft Flow ist ein Online-Service von Microsoft, der Ihnen die Möglichkeit gibt, Workflows über verschiedene webbasierte Dienste aufzubauen. Seit der Veröffentlichung von Microsoft Flow Mitte 2016, wuchs die Anzahl der Konnektoren stetig an. Derzeit sind über 150 Konnektoren verfügbar. Microsoft Flow ist mit Diensten wie Dynamics 365, SharePoint, Office 365, OneDrive, OneNote, als auch mit Diensten von Drittanbietern wie Dropbox, Google Drive, Gmail, GoToMeeting und sogar SalesForce kombinierbar. Die Einführung von Microsoft Flow hat viele Menschen vor die Frage gestellt: „Wann sollte der Dynamics Worklfow und wann Microsoft Flow genutzt werden?“ Auf den ersten Blick sehen beide Werkzeuge sehr ähnlich aus. Es gibt jedoch einige wesentliche Unterschiede, die wir unseren Lesern näher bringen möchten.
Microsoft Dynamics 365 Workflow
In which cases the Dynamics Workflow should be used
- The entire process takes place in Dynamics 365 Customer Engagement
Typically, Dynamics Workflow is a better choice if the entire process takes place within Dynamics 365 Customer Engagement (but there are exceptions). The processes can be managed centrally and the performance for each individual workflow can also be seen.
- Real-Time Workflows
Ein Dynamics Workflow kann synchron (real-time) oder asynchron (background) ausgeführt werden. Real-Time bedeutet, dass der Workflow sofort oder kurz danach ausgelöst wird. Der Hintergrund-Workflow wird ausgelöst, wenn die Kapazität verfügbar ist, ohne das System zu verlangsamen. Umgekehrt bedeutet dies, dass der Echtzeit-Workflow das System für einige Sekunden verlangsamen könnte. Verwenden Sie den Dynamics 365 Workflow, wenn Sie möchten, dass der Workflow sofort ausgelöst wird.
- Email Notifications
Probably one of the most commonly used workflows is that of an automatic email notification. With the Dynamics 365 Workflow Creator, it’s easy to create a workflow that sends a notification to a support agent, such as when a ticket has been sitting around for too long. The email notification can include the link directly to the CRM record. With one click, the support agent can start working on the record right away.
- On-Demand Workflows
If you want to give the user the opportunity to initiate the workflow manually, the Dynamics Worklfow is without question the right one. The user can trigger the workflow from a button on an entity, provided that the user has the rights to trigger workflows.
Microsoft Flow
A Microsoft Flow workflow can be triggered by almost any Dynamics 365 event. It is now also possible to create a Microsoft Flow within Dynamics 365 and initiate it manually. Before the Dynamics 365 v9 update, the page had to be visited http://flow.microsoft.com.
In which cases Microsoft Flow comes out on top
Flow can be used for things that are not easy to do with Dynamics Workflow. The following are processes or scenarios in which we believe Microsoft Flow has the edge.
- Multi-channel notifications
As mentioned earlier, the Dynamics workflow is great for notifications via email. With Microsoft Flow, it is also possible to receive notifications via SMS. With the Twilio Connector for Flow, it’s easy to send SMS for any type of Dynamics 365 event. If the Flow app is also installed on the smartphone or tablet, it is possible to receive push notifications on the mobile device.
- Visualized workflows
The user interface when creating a Dynamics 365 workflow is not exactly intuitive and nice to look at. This can be especially problematic for users who are creating Dynamics 365 workflows for the first time or only rarely. Flow, on the other hand, is visuel a feast for the eyes and the operation is more intuitive.
- Granting of authorizations
With Microsoft Flow, permissions can be granted via email, push notifications, or the Flow app. The permissions are always granted according to the same pattern. Whether it’s PowerPoint, SharePoint or Dynamics 365. Although it is possible to grant permissions with a Dynamics 365 workflow, this is not implemented particularly elegantly. The person granting permission must be an active Dynamics 365 user and log in to the CRM for each permission.
- Delete records
There is no standard option in the Dynamics workflow that allows you to delete records in the CRM. Of course, this option should be handled carefully. The user’s security role determines whether or not records are ultimately deleted.
- Workflows at fixed times or intervals
Although there is the possibility to trigger Dynamics workflows late, this can in no way be compared to the possibilities of Microsoft Flow. Microsoft Flow offers a scheduler where the exact time can be set or at which intervals a workflow should be triggered.
- Eine bessere Office 365 Integration
With Flow and Office documents in SharePoint, OneDrive, OneDrive for Business, or Dropbox, the integration between Dynamics 365 and Office 365 can be streamlined. For example, an Excel can be automatically exported to Dropbox or OneDrive as soon as a new contact has been created.
- Workflows across multiple applications
Many users share Microsoft products with other third-party applications. Flow has a lot of connectors for third-party providers and thus makes it possible to link applications outside the Microsoft world with each other.
In general, every workflow should be considered from start to finish. Do all processes take place within Dynamics 365 Customer Engagement? Then the Dynamics Workflow is without question the right choice. But if you want to include services outside of Dynamics, or even third-party services, Microsoft Flow is the tool for you.
