Jul 20 2016 07:10 AM
Jul 20 2016 07:10 AM
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 away from Designer, there are a few critical features that I would be looking for:
Can anyone speak to these capabilities being part of the tool?
Jul 21 2016 07:09 AM
Jul 21 2016 07:58 AM
In addition to Michael's response, Flow is a new workflow tool that enables business users (through browser or mobile app) to create automation to receive notifications, synchronize files, and get data between your apps and services (twitter, dropbox, salesforce as well as SharePoint, OneDrive For Business and more), be it on premise or in the cloud.
SharePoint Designer still has its space in the SharePoint ecosystem!
Jul 21 2016 08:47 AM
Jul 21 2016 08:50 AM
With the sheer number of solutions that have been built on it, Microsoft would rue the day if they ever "removed" SPD workflows from SharePoint without accounting for all of the legacy functionality (which is my fear).
But you are right, with no more evolving capabilities, it has led us to supplement with tools like Nintex Workflows.
I think it definitely has a place though, I am still building new solutions in Designer almost every day.
Jul 21 2016 09:58 AM
Jul 28 2016 01:43 PM
Hi folks, Merwan here from the Microsoft Flow team. I think it's fair to say that Flow targets many of the same scenarios that Workflow designer did and we'd like your feedback to make sure that we truly succeed in doing so. However, Flow is not necessarily a "replacement" for SharePoint Designer, it is more of an "evolution." SharePoint Designer will be continued to be supported until 2026.
With Flow, our focus is on empowering business users to create workflows for their everyday business needs through connectivity to many services such as SharePoint, Dynamics CRM, O365 Email, Dropbox, Twittter, Trello, etc. @Brent Ellis - for the capabilities you mentioned, today we support HTTP actions and have workflow level logging, but we are working on identifying gaps such as variable types, item level permissions, etc. Brent and others, if you're available next week, I'd like to do a call with you to get a better understanding of the types of workflows you're building today with the Designer and how Flow can help.
Jul 29 2016 12:27 AM
Jul 29 2016 10:20 AM
Jul 30 2016 07:15 AM
Aug 01 2016 09:52 PM
Aug 04 2016 12:50 PM
Aug 13 2016 06:58 AM
Aug 28 2016 06:14 PM
Richard, since Flow is designed for business users, we don't expect to add the complete code view functionality that LogicApps offers (Flow is indeed built on top of Logic Apps). However, we will be enriching the experience in the coming months to make it easier to write the same expressions that Logic Apps offer today. We also plan to add a migration path in the future from Flow to LogicApps.
Aug 28 2016 06:25 PM
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.
Aug 29 2016 01:11 AM
Aug 30 2016 10:20 AM
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.
Aug 31 2016 04:12 AM
Sep 01 2016 08:48 PM - edited Sep 01 2016 09:41 PM
I think the flows we have now is based on user level whereas workflows will build by IT admins to build solutions for all users. In future do we see enterprise level solutions using Microsoft flows? I am building lot more workflows using sharePoint Designer in my current and previous projects in various scenarios as specified by @Brent Ellis. I have started exploring about Microsoft flows, f possible; I would love to talk to you.
Edit: I hope we will have more control on governance of these apps. Especially if all users started developing apps then IT support team need to have access all those apps to help them if they have any issues. I saw in few posts we will get an option at Tenant admin level to show/hide the flows. I hope we have this option at Tenant, Site collection, site, and List/Library level to provide more control for admins.
Sep 07 2016 01:22 AM
Microsoft flow has new features
1. Nested conditional branching