Looking for:
Create an approval from the approvals app - Power Automate | Microsoft Docs |
Ms teams approvals -
If the approver has chosen to send an approval with custom responses, the actions at the bottom can differ. For example:. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Table of contents Exit focus mode. Yes No. Sorry this didn't help. Thanks for your feedback.
Threats include any threat of suicide, violence, or harm to another. Any content of an adult theme or inappropriate to a community web site. Any image, link, or discussion of nudity. Any behavior that is insulting, rude, vulgar, desecrating, or showing disrespect. Any behavior that appears to violate End user license agreements, including providing product keys or links to pirated software. Unsolicited bulk mail or bulk advertising.
Any link to or advocacy of virus, spyware, malware, or phishing sites. Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct. Any image, link, or discussion related to child pornography, child nudity, or other child abuse or exploitation.
Details required : characters remaining Cancel Submit. Choose where you want to search below Search Search the Community. Search the community and support articles Microsoft Teams Teams for business Search Community member. This thread is locked. This can be particularly useful in the case of rejection: you might want to let the person know why their request was rejected, and if they need to make any changes before it can be approved.
The last fundamental piece you need in your approval flow is a condition which directs the execution to the correct branch based on the response. You decide what you want to do based on the approval result. The result options are Approve and Reject. The above method used to be the only option in the past. These days we also have the Post an adaptive card to a Teams channel and wait for a response action. Why do we have two different ways of doing the same thing?
How do these methods differ from one another? In summary, the beautiful thing about creating an approval with the post and wait for a response action is having more control over the adaptive cards you want to display.
On the other hand, creating an approval first, sending it and pausing to wait for it all separately offers you more control over the other features related to the approval. You can do other things between the actions, such as update a SharePoint list item, enable notifications, narrow down the approvers, and wait for everyone to respond if desired. As I previously mentioned, the action offers you more control over the adaptive card, and what kind of message you want to display after someone submits a response.
However, this also requires more effort on your behalf. You need to create the adaptive card JSON yourself by, e. If you want, it is possible to self-create a very similar appearing card to what the Create an approval action does for you.
However, it can be made much more compact without the Power Automate logo at the top and requiring fewer clicks to submit a response with comments. Only the owners, perhaps? And prefer not have the team members even see the approval requests?
This is where it starts to become more problematic. When you use the Create an approval action in Power Automate, you are required to specify the users who have permission to take part in the approval. When you then post the approval card on a channel, everyone in that team can see it, not just the approvers.
Worst of all, the approvers will no longer have the buttons available to handle the approval. Luckily, the owners can still click on the approval link that appears on the card, get directed to the Power Automate approvals page, and handle the approval there.
What about the newer Post an adaptive card to a Teams channel and wait for a response action? Does that have the same problem? Everyone who can see the card can do it. It means that if you send the card on a team channel, all team members can do the approval. What if we sent the adaptive card to a private channel? Could we create a private channel, give only the approvers access, and have the approval cards sent there? No one else would be able even to see the approvals, not to mention, click on the buttons except for the approvers, i.
But that would just be too good to be true, right? Unfortunately, it is not possible to send approval requests to a private channel. The same applies to all custom bots and other types of apps as well. Please, cast your vote for the cause! I can see not being able to add Teams apps to private channels being very limiting in many situations. Regardless of which activity you decide to use, the bottom line is this: There is no neat way of having only a subset of team members to handle approvals on a team channel.
The best option we have is creating the approval separately and specifying which users are allowed to approve. Still, everyone can see the approval information and click on the buttons. No sensitive information can be handled this way, and the approvers might need to navigate away from Teams for managing some of the tasks other members might accidentally click.
So, are we really out of options, or could we still approach this problem some other way? This way, everyone would be easily kept on track about the approval state. But alas, with the Send your own adaptive card as the Flow bot to a user and Post an adaptive card to a user and wait for a response actions we can only send it to a single recipient. Luckily, we can still create the approval first, and then send the adaptive card tied to that approval to all of the approvers individually within a loop.
When any of the approvers responds, the flow will proceed, as all of the separately sent adaptive cards are tied to that single approval. The downside of this approach is that when someone responds to the approval request, the adaptive card only gets updated for that person. None of the other approvers knows that the approval request has already been handled. What about the post and wait for a response action? That does allow updating the card, but again, it only does it for the person who responds.
Besides, the action is not suitable for having multiple people taking part in the same approval simultaneously as it creates a separate approval on each action execution, and stops to wait immediately after sending the card. It works in a loop by sending the approval first to one person, waiting for that person to respond, and then it proceeding to send the approval request to the next person.
It can be useful for sequential approvals, but for having multiple people taking part in one approval simultaneously, it simply does not work.
No comments:
Post a Comment