Have you seen that huge warning, when trying to add a newly created Power Automate flow as a child flow, saying: “The workflow with id '<ID>', name <NAME> cannot be used as a child workflow because child workflows only support embedded connections.“? Looks scary! What does it mean? How to fix it? Let me show you!
I was recently taking part in a Regarding365 hackathon where our goal was to build solutions for companies struggling with communications during the time of COVID-19 pandemic. Sometime after a friend of mine asked me a question about building the same solution I did during that hackathon. The solution was – QnA chatbot using QnA maker as a database. How to do it? Read on!
This functionality was first released in July 2019. It has a huge potential – it allows you to create Adaptive Card and then put inside placeholders, that will be replaced as the card is being generated with the actual data. Thanks to it you don’t need to hardcode any values inside a card, you make more dynamic content. And save time.
It’s been quite a long time since I last wrote anything around Nintex platform. Recently however I was involved in my first real project around Nintex RPA (formerly known as Foxtrot, RPA tool in Nintex suite, read its review here). One of the challenges I faced was how to get data out of a repeating section…
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.
This post is not as the others. It’s not going to be technical. It’s not going to be about specific products or functionalities. It is going to be about me and my journey to where I am today, as a Microsoft MVP.
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.