Power Automate for desktop - Build 2307
This article describes the new features, improvements and fixes to existing functionality that are included in this build.
Visit the Power Automate Blog to stay up-to-date on the latest news!
Office 365 Outlook is yet another connector that comes down to Power Automate for desktop, with multiple operations now being available out of the box as native actions for desktop flows.
The action Run .NET script has been introduced under the Scripting group of actions, allowing users to invoke C#/VB.net code.
The action Add work queue item has also been introduced in preview under the Work queues group of actions, to enable the respective functionality out of the box in desktop flows.
A new tool to inspect UI elements has now been added in the flow designer in preview, providing the option to explore the hierarchy tree of all UI elements on the screen, check their attributes and values, and capture them for use in the desktop flow.
A troubleshooter for Power Automate for desktop is now introduced in preview, allowing users to diagnose or troubleshoot potential issues on the application. The first two available diagnostics in the troubleshooter can help users:
Diagnose connectivity issues with certain public endpoints, which are required for the desktop application to work normally.
Troubleshoot issues on UI and Web automation, especially around RDP/Citrix and Java automation requirements.
The troubleshooter also hosts a new functionality in preview, which can put Power Automate in a verbose logging state. This state produces some files with detailed logs, which can help capture and diagnose potential issues the user may be facing.
The retry policy in actions’ error handling now also supports exponential delay intervals between retries, apart from fixed ones.
The scripting actions ‘Run DOS command’, ‘Run VBScript’, ‘Run JavaScript’, and ‘Run PowerShell script’ now come with an additional timeout parameter, to avoid cases where running flows might get stuck in those actions.
In the action ‘Extract data from web page’, trying to close the live web helper window now brings up a confirmation popup dialog, in case some data have already been captured.
The proper error messages are now shown when a user is unable to create a connection for a cloud connector action.
A new registry key is now available to prevent detailed logs per action from being uploaded to the flow logs, after a desktop flow runs through the console.
Work queues are now retrieved automatically in the ‘Work queue’ field of the corresponding actions.
The ‘Work queues’ group of actions has now been moved between the ‘Browser automation’ and ‘Excel’ action groups.
The cloud connector actions are now ordered alphabetically by their display name in the respective groups of the actions list.
The summary of the action ‘Add to datetime’ now includes the produced variable as expected.
The following list details issues in Power Automate for desktop that are now resolved:
The action ‘Write to CSV file’ now handles the ‘\r\n’ (new line) character as expected; in case ‘\r\n’ exists in a CSV entry, it will be contained in a single cell.
The sign-in popup in the machine runtime app now launches without delay, when the app is launched from the portal.
When users perform a search in the flows list in the console typing the name of a new, not yet saved flow, focus is now not lost from the search field.
Desktop flows now can’t be triggered multiple times using their hotkey triggers, preventing the exception that was caused by this behavior. A flow can now be triggered once; as long as it runs, the following keyboard shortcuts are ignored.
The text in the flow designer is no longer truncated under larger scaling values (i.e. 225%).
A minor issue with the behavior of the search field of the variable picker menu has now been resolved.
The action ‘Go to’ now properly lists all applicable labels in the respective subflow, resolving an issue occurring when the latter included blocks of actions like conditionals or regions.
Invalid or missing URLs behind ‘More info’ links in custom actions are now handled more gracefully.
The error handling screen is now hidden in cloud connector actions, if the user doesn’t have any connections available.
In the action ‘Display custom form’, upon opening the custom form designer, the properties of the form elements now also properly validate missing variables, apart from syntax errors.
The ‘Launch Outlook’ action now properly waits for the Outlook application to load before proceeding, preventing the intermittent errors that occurred because of the former behavior.
The live web helper window of the ‘Extract data from web page’ action is no longer unresponsive, when there are many tabs open in the target browser, or when Edge is used in IE mode.
Setting a combo box value through the recorder menu no longer produces an incorrect result.
Return to the all version availability page.
If you have any feedback on the release notes, please provide your thoughts here.