Microsoft Flow is no more (as a product) as it is now referred to as Power Automate. For those of you just getting on board with the Flow language, time to change again! However, rest assured there is no change but evolutionary improvement - individual scripts are still called 'Flows'. Sounds like the start of a plan to extend automation beyond the Flow tool set so look for more of this.
To this end, a few days ago, Microsoft released UI Flows which provides the ability to record and script interface behavior such as mouse clicks, keyboard, and data entry. This looks like a rebrand of the Selenium IDE tool - in fact this is exactly what is downloaded to capture UI Flows! Although this technology has been around for awhile, I gave it a shot recently with a 'all hands-in' approach with mixed results. Could it be a tool for solution validation? I am cautious. However, optimism can be gained after this reading this great
post by Al Sargent.
There is also the re-branding of Dynamics 365 Virtual Agent for Customer Service to Power Virtual Agents. Certainly less of a mouthful to say! From my perspective, the trend is clear - a move away from the traditional 'Dynamics/CRM' all-in-one-app to monetizing the tool set by breaking it into interoperable pieces. This is a good thing! But if there is one message to pass along to Microsoft is go easy on changing the language of the products and tools, it will get in the way if there is no substance other than brand regrouping.
It was great to hear that the original ADX Studio portal has made it as a tool independent of Dynamics 365. The Power Apps Portal is the same as it was but with the ability to connect to a CDS independent of Dynamics 365.
There were a few more bits and bobs. Have a
read and let me know what you think?
