Forum Discussion
Microsoft Flow and document lifecycle for approving major versions
Jeremy Thake the new "Set content approval status" action should do it. But only works partially. It works when you use "submit" to get from draft to pending, but it will not do anything when you try to approve or reject. This seems to be a bug.
Cheers
Christian
Jeremy Thake Christian Glessner
I got it working the other day and thanks for the comments.
Upon Item selected trigger, I set content approval status to submit.
After approval action, I set content approval status to 'approve', but the trick is to click on 'advanced' and you will see a field to enter ETag. So add the ETag that is the output of the first content approval status action.
Therefore, document becomes approved in the doc library.
There should be a new trigger when from the Doc Library, when a user submits a doc for content approval. Thank you again.
My situation is a little different. I am not looking at Content Approval. I simply want to publish a major version of my document. i.e. v1.0
Similar to Mark's question / situation.
I can do an approval based on the assumption the file is new or someone has edited it in the library so the approval status is reset to Pending.
But what about situations where the doc owner gives the file a surface review, makes no changes and simply wants to re-approve / reset the document review date. It would be great if I could wrap these teo scenarios into the same flow with a check against current approval status. But it looks like I'm going to have to build 2 flows for each, and work off another column, or automatically update a metadata column to force a Pending state then send for re-Approval.
Is my take on this still accurate? Still cannot look up the selected files approval state via a condition?
Cheers
