Future of SharePoint Designer Workflows

[SylvieLet17]

I'd like to know how sustainable workflows built in SharePoint Designer 2013 will be now that Flow has been introduced. 

I have tried to recreate my workflows in Flow but there are just some functionalities that either do not exist properly yet in Flow, or are causing performance issues. For example, getting a document link based on a document title, which I used to be able to do with a workflow variable in SPD, but now I have to do an "Apply to Each" which seems to be taking literally days to complete. 

This is just one example of where the new tech does not meet my needs yet. 

But at the same time, I'm trying to build these workflows to be usable for several years, and I don't want to build on legacy programs if they will be obsolete and there will be no way to migrate the flows in future. 

Does anyone know the roadmap/support for SPD 2013 workflows?

Thanks,

Sylvie

[v-xida-msft]

Hi @SylvieLet17,

Thanks for your feedback, if you would these features of SharePoint workflows to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

More details about the roadmap/support of SharePoint 2013 workflows, please check the following article:

https://technet.microsoft.com/library/cc73be76-a329-449f-90ab-86822b1c2ee8(v=office.16).aspx

Best regards,

Kris

[Anonymous]

Would it be possible to be more precise because unfortunately Flows does not answer or hurt complex business scenarios like the 2010/2013 designer flows.

Microsoft seems to want to support Infopath + SharePoint designer until 2026 (see more because these two components are present on SharePoint server 2019), is this the case for SharePoint Online? It would be really interesting to get visibility

Thank you for your return

[DevendraV]

@Anonymous, yes it will be supported in SP Online till 2026.

You can read more about Infopath forms support here 

https://techcommunity.microsoft.com/t5/SharePoint/InfoPath-support-in-SharePoint-Online/td-p/96994

and  (Hint check FAQ)

https://www.microsoft.com/en-us/microsoft-365/blog/2016/01/20/sharepoint-server-2016-and-project-server-2016-release-candidate-available/

Hope this helps.

[GabrielStJohn]

Hello, @SylvieLet17!

Have you had an opportunity to apply @DevendraV‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify! Thank you for being an active member of the Flow Community!

-Gabriel

Flow Community Manager

[AlbertoSP]

After about a month of playing with MS Flow and Power Apps, I can say with certainty that 95% of the tools I created using InfoPath / SPD 2010/13 workflow, can NOT be move or replicated using the new tools. They are simply not meant to deal with, or even stable enough any complex business solution. Without an easy ability to set item level permission, most of my business apps wouldn't even pass an audit. I just wonder what is the intended use of Flow and Power Apps as I just don't get it?

[Anonymous]

I confirm, Flow remains very limited against the old engine of Workflows 2010 and 2013 (soon 10 years), I never really understood this back on the part of Microsoft, 9 years later, we still find ourselves doing workflows 2010...