Power Platform Community Forum Thread Details

Hi,

I have the app & flow that submits the request and approvers approve/reject.

I have 4 stages of approval process, and in Stage 1 there are 11 approvers, and 2 approvers in Stage 3.

The reason that there are so many approvers in stage 1 is that based on the specific column's value, it sends the notification to one of those approvers. And for stage 3, it doesn't matter who approves it.

Until now I had a flow that sends a task to the Teams where approvers click 'approve' or 'reject' after looking through the submitted request's details.

But now they want to be able to approve/reject in the app.

I was thinking of making a button [Approve/Reject] in the app that initiates the flow of notifying approvers.

However, as I mentioned, I have 4 stages of approval and don't want to make approvers confused in this process.

Making each button such as [Approve as A], [Approve as B], etc. will result in 8 buttons including rejection.

But I want to avoid a situation where someone clicks the wrong button.

Here is what I think:

Just make 8 buttons - APPROVE and REJECT

Set the visibility of the buttons as If user email = one of the stage 1 approvers' emails, true.

Then onselect, run the flow.

However, how can I achieve this? I become so confused since there are so many approvers in stage 1.

ALSO: Do you think I have to make 8 separate flows of each approval process when clicking the button? But I am 100% sure this is not a good idea. I also have to handle rejection case: if rejected, the requestor should resubmit the form and it should send the notification back to the one who rejected regardless of the stage, no need of going through all the way back to the stage 1 and getting prior approvals again.

I would genuinely appreciate any input!

Categories:

Building Power Apps

Hi @pinball2

I've created something similar recently and managed to achieve it with no flows.

When an approver selects an outcome in the app, this patches the status/comments/date etc and it uses the outlook connector to automatically send an email directly from the app, including approval details/status etc and a deep link to take the next approver or the original requestor straight into the approval item in the app.

With regards the 8 buttons, you should be able to get away with two buttons. Assuming you have a main Approval Item list (one), Approval Record (to many i.e. one row for each of the 4 approval stages for each main approval item); and you then have an Approvers list, with the approvers somehow categorised. You should then be able to control the visibility and/or displaymode of the buttons based on the current approval stage and a lookup to the Approvers list to check if the current user has the right to approve the currently open approval item.

If you do want to have a crack at this, I would recommend trying to compile one generic template email which you can re-use for all potential approval outcomes, with specifics being added dynamically into the subject and the body.

I hope this helps a bit