November 2022 update of Power Automate for desktop

We are happy to announce that the November 2022 update of Power Automate for desktop (version 2.26) has been released! You can download the latest release here. New features and updates have been added, as described below.

A home page is now available in the console

A new home page has been added to the console of Power Automate for desktop, where new users are guided on the first steps of their RPA experience, while existing users can find popular and useful resources.

Home page

A license request form has been introduced in Power Automate for desktop

Users can now ask for a new trial or trial extension, or a license purchase/renewal directly through Power Automate for desktop, via submitting a request to their administrator.

License request from admin

Warnings have been introduced in Power Automate for desktop

Warnings are now supported in Power Automate for desktop, via the errors pane which has been enhanced accordingly, as well as via a proper banner in the action modals.

Warnings

More SharePoint connector actions are now available in Power Automate for desktop

More SharePoint connector actions are now available to be used (in preview) in Power Automate for desktop, in addition to the existing ones:

  • Get file content
  • Get all lists and libraries
  • Get file metadata
  • Get folder metadata
  • List root folder
  • Extract folder
  • Get lists

New SharePoint actions

Captured UI elements will now be more efficient

The reliability of the captured UI elements has been improved in the following ways:

  • Default web selectors have been adapted to ignore the element’s Class, Type and Value attributes, but include the newly added Text attribute.
  • Ordinal is only used in the final element of the web or desktop selector.
  • A selector validator applies behind the scenes, confirming that the captured element’s selector will find the same element when used at The validation is being performed at the moment of the capturing.
  • In case the selector proves invalid in the above scenario, a selector optimizer takes place, trying to automatically fix the selector at the moment of the capturing, by ignoring elements from the top level and continuing until the element is identified by the new selector in the process.

 

Hoping that you will find the above updates useful, please feel free to provide your questions and feedback in the Power Automate Community. If you want to learn more about Power Automate Desktop, get started with the below resources: