Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify / Override OOTB Approval in Power Automate #9629

Open
GeorgeLuther opened this issue Apr 9, 2024 · 0 comments
Open

Modify / Override OOTB Approval in Power Automate #9629

GeorgeLuther opened this issue Apr 9, 2024 · 0 comments

Comments

@GeorgeLuther
Copy link

The article focuses on the on create trigger, but more scenarios are common. Please include more information:

SharePoint Document Libraries have an out of the box approval flow. It is unclear in the documentation how this is handled 'behind the scenes' but it doesn't appear to be via power automate. You enable it navigating to the library settings > versioning settings >
image

Say you want set this up to be a multi-approver flow where any 3 members must approve and any may reject.
The information I've seen seems to suggest you could do this by a "When a file is created or modified (properties only)" trigger with a trigger condition of approval status "Pending" (@equals(triggerOutputs()?['body/{ModerationStatus}'],'Pending'))

In practice this generates (an) additional approval(s) on top of the OOTB approval flow, making canceling impossible and approval cards in teams never get handled like they should per https://learn.microsoft.com/en-us/business-applications-release-notes/april19/microsoft-flow/long-lived-approvals-other-approval-improvements

From a user interface perspective it would be ideal to use the OOTB ux for approvals by enabling the versioning setting. But it is unclear how it works under the hood, and what the best practice is for overriding/modifying the Out of the Box Approval.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant