Joel's SharePoint Architecture Blog

SharePoint Server, SharePoint Online and Office 365 Training, Architecture, Administration and Development

You are here: Home / SharePoint / SharePoint Thing a Day – 019 – Development. Flows, not Workflows.

SharePoint Thing a Day – 019 – Development. Flows, not Workflows.

by

Flows, not Workflows

View this post on Instagram

#spthingaday 019 – Development. Flows, not Workflows. #SharePoint, #Office365, #MicrosoftFlow.. If you are an old hand at building business processes for SharePoint, moving to Office 365, you might just reach for those trusted old tools of SharePoint Designer, or Visual Studio and start designing workflows. Well, it's time to put those tools away. Business processes and orchestrations are nowadays much better done in Microsoft Flow or Logic Apps. (http://1jj.uk/startingwithmsflow) For simple to medium complex scenarios, power users can use the browser to build a Flow directly on a SharePoint Online list or library. Flows can be saved as templates, to apply them to many more lists and libraries, and to share them with your teams. For developers, wishing to hide the implementation away from users, Logic Apps, in Microsoft Azure, is often a more suitable venue. Both use the same graphical design surfaces, and there are hundreds of connectors already, such as: SendGrid, Outlook, Dynamics and SalesForce. Some of these can be triggers, and some used only as actions. Flow and Logic Apps is an ecosystem of connected systems, including mobile apps for Android and iOS. Not only can you develop Flows directly on the mobile, but app users can participate in Flow Approval actions. (http://1jj.uk/flowapprovals) Tomorrow we'll take a look at more complex scenarios. #microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement

A post shared by JFDI Consulting #spthingaday (@jfdiconsulting) on

If you are an old hand at building business processes for SharePoint, moving to Office 365, you might just reach for those trusted old tools of SharePoint Designer, or Visual Studio and start designing workflows.

Well, it’s time to put those tools away.

Business processes and orchestrations are nowadays much better done in Microsoft Flow or Logic Apps. (http://1jj.uk/startingwithmsflow)

For simple to medium complex scenarios, power users can use the browser to build a Flow directly on a SharePoint Online list or library.

Flows can be saved as templates, to apply them to many more lists and libraries, and to share them with your teams.

For developers, wishing to hide the implementation away from users, Logic Apps, in Microsoft Azure, is often a more suitable venue.

Both use the same graphical design surfaces, and there are hundreds of connectors already, such as: SendGrid, Outlook, Dynamics and SalesForce.

Some of these can be triggers, and some used only as actions.

Flow and Logic Apps is an ecosystem of connected systems, including mobile apps for Android and iOS.

Not only can you develop Flows directly on the mobile, but app users can participate in Flow Approval actions. (http://1jj.uk/flowapprovals)

Tomorrow we’ll take a look at more complex scenarios.