cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Parallel Approvers Unaware of Approval

Does anyone have a method for getting around parrallel approvers not knowing if the request has already been approved by a colleague?

 

Since the Teams Adaptive Card is not dynamically checking this at any time an Approver can respond to something that's either been approved or rejected previously. The only options we can think of are to:

- Post messages that it's been approved to other approvers.

- Prevent approval if the approval status is already set

 

We'd really like to remove the request once approved by another but don't think this is possible with the current set of approval features.

 

If anyone's figured out a good approach to this problem it would be much appreciated. Anything where we don't have to pollute their Flow Bot messages with updates would be ideal.

1 ACCEPTED SOLUTION

Accepted Solutions
Super User II
Super User II


@Anonymous wrote:

Does anyone have a method for getting around parrallel approvers not knowing if the request has already been approved by a colleague?

 

Since the Teams Adaptive Card is not dynamically checking this at any time an Approver can respond to something that's either been approved or rejected previously. The only options we can think of are to:

- Post messages that it's been approved to other approvers.

- Prevent approval if the approval status is already set

 

We'd really like to remove the request once approved by another but don't think this is possible with the current set of approval features.

 

If anyone's figured out a good approach to this problem it would be much appreciated. Anything where we don't have to pollute their Flow Bot messages with updates would be ideal.


Cards are static content, up to date only up until the time the card was generated. I simply have an updated Teams Adaptive Card sent when the status is changed or an approval is updated. 


@Anonymous wrote:

Anything where we don't have to pollute their Flow Bot messages with updates would be ideal.


That's the point of the bot, to provide updates. When an approval has been updated, it notifies all approvers so that they know. Even if someone isn't the one who approved it, they are an approver and they should know that one of the approvals assigned to them, has been approved by someone else. 

I guess if you want to have this single pain of glass that is always updated rather than utilizing cards and updates as the items are approved or updated, you could create a viewable/sortable SharePoint list or Planner buckets with all approvals that the approvers can monitor.

That just seems unnecessary to me, though. Otherwise you may want to rethink your parallel approvers design, and go to a more escalated approvers design. So only update other approvers if the inital approver doesn't update it in a set amount of time.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

View solution in original post

1 REPLY 1
Super User II
Super User II


@Anonymous wrote:

Does anyone have a method for getting around parrallel approvers not knowing if the request has already been approved by a colleague?

 

Since the Teams Adaptive Card is not dynamically checking this at any time an Approver can respond to something that's either been approved or rejected previously. The only options we can think of are to:

- Post messages that it's been approved to other approvers.

- Prevent approval if the approval status is already set

 

We'd really like to remove the request once approved by another but don't think this is possible with the current set of approval features.

 

If anyone's figured out a good approach to this problem it would be much appreciated. Anything where we don't have to pollute their Flow Bot messages with updates would be ideal.


Cards are static content, up to date only up until the time the card was generated. I simply have an updated Teams Adaptive Card sent when the status is changed or an approval is updated. 


@Anonymous wrote:

Anything where we don't have to pollute their Flow Bot messages with updates would be ideal.


That's the point of the bot, to provide updates. When an approval has been updated, it notifies all approvers so that they know. Even if someone isn't the one who approved it, they are an approver and they should know that one of the approvals assigned to them, has been approved by someone else. 

I guess if you want to have this single pain of glass that is always updated rather than utilizing cards and updates as the items are approved or updated, you could create a viewable/sortable SharePoint list or Planner buckets with all approvals that the approvers can monitor.

That just seems unnecessary to me, though. Otherwise you may want to rethink your parallel approvers design, and go to a more escalated approvers design. So only update other approvers if the inital approver doesn't update it in a set amount of time.

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

View solution in original post

Helpful resources

Announcements
Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Microsoft Ignite

Microsoft Power Platform: 2021 Release Wave 1 Plan

Power Platform release plan for the 2021 release wave 1 describes all new features releasing from April through September 2021.

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (71,725)