Aug 21 2017 05:00 AM
Hi all,
I'm well experienced in SharePoint, but have never used workflow (don't ask me how). In my new role we have the following requirement so I was wondering if you have any advice as to whether SharePoint workflow or Microsoft Flow (or a combination / something else) would be best to use.
The requirement is a process flow around the creation, internal approval and signing of contracts for new consultants (or extending contracts for existing consultants):
This must be crying-out for some kind of workflow / approval automation, so if I can benefit from the Community's wealth of experience as to where to start that would really help. It's worth noting that I'm an advanced end user rather than developer so would like to solve this with 'out-of-the-box' functionality.
Hope you can help and thanks as always, Oz
Mar 22 2018 02:26 PM
Hey @Stephen Siciliano ,
I've got a question regarding the "Revisions Completed" link in the email sent out in the IF NO branch of the Check if Approved condition. How was this implemented? In what way does it notify flow to restart the approval loop?
Thanks!
Mar 22 2018 06:28 PM
Hello, if you want to make it repeat inside of the Flow until it's approved, then you add a "Do until" loop. This loop would check at the end if the request has been approved yet -- if not then it'll restart the loop.
Dec 03 2018 01:33 AM
Dec 03 2018 09:43 AM
Microsoft Forms is a great and simple way to get started. You can also use Microsoft PowerApps.
Mar 13 2019 01:44 PM
The costs will be rather insane for larger organizations (like mine) using Flow over SPD workflows for simple tasks. I my opinion something has to be adjusted how the plans work...
Oct 16 2019 07:56 AM
Oct 16 2019 08:45 AM
@Jlaws I'm not aware of a way to convert.
Oct 16 2019 10:45 AM
Oct 16 2019 10:56 AM - edited Oct 16 2019 11:00 AM
@Jlaws I think if Microsoft decides to retire the native workflows then they certainly should have a suitable alternate mechanism. Most likely whole world is hooked into native workflow and may have the same exact questions (I certainly worry about the same). So just curious if there is any pressing need at your site at this time to convert the native workflows into FLOW.
The approach I have taken is to define all the new requirements into FLOW and anything already in Workflows stays there for time-being. Even if a site template has a workflow already built into it, it does create a new workflow every time I create a site from that template. I don't discourage myself against that as FLOWs can not really be made part of the site templates. So I assume there is no real case for Microsoft to retire native workflows, and eventually FLOW will win over workflows with additional advancements over period.
FLOWs also might have additional pricing angel to it as it grows in future.
Oct 16 2019 12:14 PM
Jun 03 2020 06:15 PM
@Jlaws If you decided to do it, how is that going for you? Any particularly helpful resources or notable catches?
Jun 03 2020 11:42 PM
@Brian . two of the most helpful resources I found when I was first learning Flow (Power Automate) 2 years ago were the videos on YouTube by Shane Young and the assistance given by the Microsoft Power Automate Community where I'm now a super user (https://powerusers.microsoft.com/t5/Forums/ct-p/FL_Comm_Forums). Questions range from basic to very complex, it's a friendly community and questions get answered quickly. But you don't have to ask a question; you can learn a lot by just browsing the community.
Rob
Los Gallardos
Microsoft Power Automate Community Super User