Forum Discussion
Microsoft Flow and document lifecycle for approving major versions
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.
- I have noticed an issue with the Flow Approval process. I have a flow where two stage approval flow on a document. First step a manager has to approve the content. The next step a department manager has to approve. If an approver makes a small change to the document being submitted but still approves it, the workflow will error with the following...
"message": "The current state of the item is Draft and the following action Approve cannot be implemented"
How can you let the manager make a change but still continue on the flow? 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
