One of the very powerful features of Power Virtual Agent is the functionality called “Entities”. It’s main purpose is to let bot ask question to user, then let user answer to the question in natural language, using full sentence and finally to extract from that response key points, that will let the bot to move on in the conversation.
Today Audrie Gordon Senior Program Manager for Power Automate organized webinar where she announced new changes to the integration between Power Automate and Microsoft Teams when talking about Adaptive Cards.
Features she was presenting are a long awaited functionalities we all were missing very much and which really fill the gap in business processes that are being created using Adaptive Cards and a no-code approach.
With the fresh release of Power Virtual Agent and its general availability (2nd December 2019) a bunch of new features were added to the tool. One of them is the functionality that allows us to publish the bot and use it in Teams for example. Or Messenger. Or Slack. Or …
In my previous post you were able to learn how to authenticate user in Power Virtual Agent. This post is about getting and using context of the authenticated user.
Today Microsoft already released some of the features, which were planned to be released on 2nd of December 2019, in their “new” product: Power Virtual Agent. One of them is “Authentication”. In this post I will help you to set up Azure Active Directory as an oAuth2.0 authentication endpoint.
Having the opportunity to attend couple of conferences, meetups and even organizing one I found myself in a doubt regarding the meaning of the terms that are being used to name specific types’ of users/ attendees and therefore tracks. Today we have such names as “Citizen Developer”, “IT Pro”, “Power User”. What do they mean?
This post however is going to be much deeper analysis of the modern profiles of employees and tools they are using. I really tried to read what was available to get more familiar and to understand better who is who. During gathering of the content I also did my own survey to get even more insights about the today’s role of Citizen Development, it’s reach and meaning for companies. I hope my findings will be also valuable for you.
On 21st August 2019 Microsoft announced that actions in Microsoft Flow from Outlook stack, are going to be moved from using Outlook REST API v1.0 to Microsoft Graph v1.0. Along with that information there was also written, that current Outlook API 1.0 is going to be decommissioned in 1st of November 2019. So after that date all old actions in Microsoft Flow are going to be removed too.
It took me a little more time than I was expecting, but here it is! The post you are now reading is the last part of the 4-parts series of posts dedicated to Microsoft Adaptive Cards. Information in this post is valid for the September 2019. Because this technology is continuously changing, the knowledge from this post may in some parts get outdated, however I will do my best to update it accordingly.
This post extends what I wrote in a previous one about Try-Catch pattern in Microsoft Flow. In this writing I am focusing on how you can log errors that occurs in your Microsoft Flows in a single place, using Azure Application Insights.
Recently I had a pleasure to show my presentation during Microsoft Flow Online Conference 2019 about building errorless workflows in Microsoft Flow. Actually, it was more about logging and debugging to receive errorless workflows in the end.