Forum Discussion
Microsoft Flow and document lifecycle for approving major versions
Hi All,
Assuming the Flow Approval solution from https://www.chakkaradeep.com/2018/03/12/require-approval-of-documents-in-sharepoint-using-microsoft-flow/ works, how would you then connect the File approval background and the Flow(s) used to approve that file ?
I am asking this for Auditing purpose, whether there would be an easy way open the approval flow directly from the Document Library file ?
Or vice-versa, to find the file scenario in the Flow interface ?
So far, it doesn't possible to have an overview on all cases with customized column(s) where you could search on your file name, but please correct me if I am wrong, thanks!
Hi,
I'm joining in on this thread, we have a scenario where we need content approval on all our Quality Documents and so far I have to this with a SharePoint 2010 approval workflow as we need the autostart option when approve major version.. The SharePoint 2010 WF seems rather old now and I would like to move over to MS Flow, however as I understand I am not able to autostart an approval flow when publish major version? If anyone knows or has some tips that would be awesome. Without this our organization can not move over to MS Flow.
regards
Martin
- Richard BurdesOct 18, 2018Brass Contributor
Hi Martin,
I may have read your question wrong - so forgive me - but generally is a document has a published major version, you would assume that the approval has occurred to enable the publishing? So I see it as document sent for approval, gets approved, major version published - is this what you are trying to achieve via flow?
You can approve the file, which if you have major and minor versioning enabled will then create a new major version on approval - check out this walk through - https://blog.leitwolf.io/approve-a-sharepoint-document-with-flow-set-content-approval/ we have something similar to this enabled and running well for a client now - we just had to enable custom permissions for a file in a secure library for reviewers to let then edit, then once done send for approval and roll back the permissions. Hope the link helps.
- jimmywinbergApr 26, 2019Copper ContributorSame issue as Martin says, how do we trigger the flow to start when user wants to publish a major version?
- Martin SagerstrandApr 29, 2019Brass Contributor
Hey Guys,
I still have not found any good information regarding the autostart of a flow when approving, I would guess this to basic functionality for when using Major versions. Good work around there jimmywinberg however I dont see our users are going to even push a button approve something. this has to be automated. I have not had so much time to look into this anymore, however found this could give some pointers in the right direction for a work around.
regards
Martin
- Martin SagerstrandOct 18, 2018Brass Contributor
Hi Richard,
thanks for your reply and yes you have understood what we are trying to achieve, however it seem that we are not able to autostart the workflow on publish major workflow. And that is the important feature our organization is after, without the autostart of the workflow we are not able to move over to Flow. :(
And that was my biggest questions if anyone has actually found a way to autostart a Flow on when user wants to publish a major version? Or this for now can not be done with Flow
best regards
Martin
- jimmywinbergApr 26, 2019Copper Contributor
I have the same issue, i dont know how to autostart the flow when a user wants to publish a major version.
Right now i created a button next to the item in the list by column formating. Text on the button say Publish Major Version, when user clicks the button the flow starts and sends approval and so on.
But im waiting on microsoft to release something to auto trigger flow when user wants to publish major version