Not so long ago I wrote a post where I was describing how to integrate WinAutomation with UI flows (here). It didn’t take much time for Microsoft to release a dedicated connector, that does the same thing, but well… Is much easier to use!
With this new trigger you can add create a new level of governance for your Microsoft Teams. Especially when speaking about the on-boarding users or other automated processes for newly added Teams members.
Power Virtual Agents has just been equipped with the new functionality called “global variables”. With it we are now able to chain topics’ conversation and still be able to know the context from previous topics. Also – bots can be given the context from external applications using those variables. How to do it? Let me show you.
Having the trigger in Power Automate called “When a file is deleted” many asks if there is a possibility to restore that removed file or delete it permanently? Yes it is. Let me show you how.
In my previous post First steps to start using WinAutomation with UI flows I have guided you through installation and troubleshooting of WinAutomation. However, since this tool became a part of the Microsoft’s RPA landscape, the important question is: how to integrate it with UI flows and existing Power Automate processes? Let me show you my approach.
On May 19th Microsoft announced they have acquired company Softomotive, the maker of the WinAutomation RPA tool (source: https://flow.microsoft.com/en-us/blog/microsoft-acquires-softomotive-to-expand-low-code-robotic-process-automation-capabilities-in-microsoft-power-automate/). Let me walk you through first steps so that you can start using it as well.
Ever been there? You know what question you want to ask to a chatbot, but it is not trained to understand it, so instead telling you, it doesn’t know the answer, it’s just constantly asking you to rephrase the question?
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.