Dear Microsofties - let's talk about FLOW Approvals,
We were so glad when they first appeared - cause we could finally move away from the freaking SharePoint task lists, and all the problems we had with using them.
We finally had something cooler than Nintex, and it was out-of-the-box... and it worked... and it... And it's starting to be a huge disapointment and source of frustration.
To be very succint, for the Flow Approval to be really usable, I see three things that we need:
All these topics have been addressed on this forum multiple times.
and in many other posts.
For us to continue pushing these features in our organizations - we kinda need to know if these features are ever going to happen.
Them being flagged as under-review or planned for years - does not really help us.
1) If you go to the Sent tab in the Approvals section of the Flow site you can see all the approvals that you sent that are still pending. There are also ways to build a PowerApps app that pulls a list of ALL pending approvals in the Tenant form CDS.
2) You can use the Get Mail Tips action to check if a user has set their out of Office message and send the approval to someone else if they have. Do that and you won't need to reassign the approval.
3) Other than the PowerApp using CDS to get a list of Approvals that you didn't send these functions are all part of the basic package.
Hi @SPDaniel ,
About the new feature requests, the status of requests have been changed to Planned and Under Review, which means that these features will be taken into consideration and released in future releases.
Please check the doc on What’s new for more details:
@Pstork1 - (1) you can indeed view the approvals you sent out in the UI - but thats really not what I am after. We are talking about IT Admins here that work in organizations with hundreds - thousands of users. That is really not an option. The CDS approach comes closer - but again, building those apps is a pain, and it adds a new layer of complexity (and costs) on top of the platform. Managing the approvals should not be more complex than building the business tools we need.
Also - CDS is NOT a solution for better integration into our custom solutions. Graph API would fit perfectly in the bigger Microsoft productivity story.
(2) indeed, in a small organization, mail tips can be a solution - but in real life, people dont always set oof messages, they are caught up in unexpected absences, they leave the company.
When we have to manage thousands of users, we cannot really use the OOF as a delegation trigger. Its not realistic.
Plus, and this is a big thing, what happens with business flows when one of the approvers leaves the company?
(3) the licensing costs are part of the problem - but if we have to bring in a dynamics guy to build our solutions around CDS, thats also a cost factor - maintaining power apps, and all that together changes the parameters immensely.
And the big thing here - we need solutions, not hacks and workarounds.
@v-yamao-msft - don't get me wrong, we appreciate the openess and the readiness to collaborate on part of Microsoft. (full disclosure: i spent 10 years in microsoft)
But... when you flag a feature we need as Planned - we start to develop our solutions appropriately. All our custom solutions that use Approval are designed in such a manner that we can integrate GraphAPI approvals into them. When two years down the line these features are not yet present - we start to be unsecure about this strategy (and we post sad stuff on the support forums). I know we cannot get a definitive timeline - but still... yeards, months, decades...
Fill out a quick form to claim your user group badge now!
We've given our badges an overhaul and also added some brand new ones!
Learn how to build the business apps that you need.
Find out where you can attend!
Watch & learn from the Power Automate Community Video Gallery!