Chromium-based embedded browsers
Cross-origin iframes support for CefSharp
We’ve added cross-origin iframes support for our CefSharp WPF implementation. This is now available for CefSharp versions v122.1.120 and newer.
Coded automations
Activities In Coded Workflows use Project Defaults for Timeout
UI Automation activities in coded workflows now use the project ‘s default values for activity timeouts instead of having to manually enter a value for each. The timeout value is taken from Project Settings > UI Automation Modern > Timeout.
Option to choose when to close the target app
The behavior in coded workflows was to always kill the target application by default and this couldn’t be changed from the activity itself. We now have a Close option for the target application, that we can use anywhere in the coded workflow, when needed.
Overload with SecureString for TypeInto in UiAutomation API
Previously, in coded workflows the TypeInto activity supported just string as parameter type for the text:
TypeInto(TargetAnchorableModel target, string text)
TypeInto(string target, string text)
We added overloads with SecureString as type for the text parameter, for Studio Coded Workflows:
TypeInto(TargetAnchorableModel target, SecureString text)
TypeInto(string target, SecureString text)
Core UI Automation
Expose WaitForReady property in selection helper
The Wait for Page Load property with its three values (None, Interactive, Complete) was configurable from the Properties panel for UI Automation modern activities. We’ve now made it available in the Options section of the Selection Helper.
The Application Card attaches exclusively by its defined selector
Starting with UIAutomation 24.12 we changed the Use Application/Browser activity attach logic such that it will attach exclusively by its defined selector (at run-time).
For newly created Use Application/Browser activities it is inhibited the previous attach logic that tries to attach by fuzzy title / URL. For example, if there are two browser tabs open with the same URLs and different titles, the title attribute from the Window selector will be used for matching the browser tab.
Auto-verify Execution for Type Into in pure Computer Vision scenarios
This enhancement ensures that execution verification is automatically applied when only Computer Vision (CV) is available, significantly improving the resilience and reliability of automations. For scenarios where selectors are available, Auto-Verify Execution ensures that the input is validated by checking if the expected value has been correctly entered after execution. Now, this same robust mechanism extends to pure CV scenarios, where no selectors are present.
Semantic Icon Descriptions for Objects and Activities
We’re enhancing the Object Recorder with the power of the CV AI Model to generate Semantic Icon Descriptions: the model now outputs semantic descriptions of icons, improving object naming for elements captured through the Object Recorder, including features like Capture All Elements. Additionally, these semantic descriptions are used to rename activities based on pure CV icon targets, ensuring greater clarity and consistency across your automation workflows.
Hebrew and Arabic Support for UiPath Screen OCR
The latest update brings support for Hebrew and Arabic to Screen OCR. This enhancement allows you to seamlessly extract text in these languages, improving automation capabilities for users working with right-to-left scripts.
The UIAutomation v25.2 preview package is not included in the Studio 2025 February Community Release. You will be able to try the new features by adding the UiPath.UIAutomation.Activities package v25.2.0-preview as dependency to your project.
Remote Runtime support for Amazon WorkSpaces
The Remote Runtime support for Amazon WorkSpaces for the PCoIP (PC-over-IP) protocol was released in version 24.10 Oct LTS. With version 25.2 we continued to expand support for Amazon WorkSpaces with the DCV (Desktop Cloud Visualization) protocol.
We now provide this support for both DCV and PCoIP protocols, allowing customers to choose the best option for their use case.
-
Automating Amazon WorkSpaces using PCoIP requires UiPath.UIAutomation.Activities, UiPath Studio and UiPath Remote Runtime v24.10 or higher.
-
Automating Amazon WorkSpaces using DCV requires UiPath.UIAutomation.Activities, UiPath Studio and UiPath Remote Runtime v25.2 or higher.
Similar to the other remote solutions, our extension for Amazon WorkSpaces is composed of a client part and a server part.
-
Client part: The UiPath extension for Amazon Workspaces that can be installed from Studio - Tools - Extensions page or with
SetupExtensions.exe. -
Server part: UiPath Remote Runtime that can communicate with the extension and must be installed with
UiPathRemoteRuntime.msi.
Browser Dialog Scope activity
In business process automation, users encounter cases when browser dialogs block the execution of the current browser page. Typically, the user would want to dismiss the browser dialog and also get the dialog message for later use in the business scenario.
JavaScript has three kind of popup boxes: Alert, Confirm, Prompt. Starting with UiPath.UIAutomation.Activities version 25.2 we introduced a Browser Dialog Scope activity to handle this type of dialogs. This activity should be used as a scope for the activities that may generate a browser dialog.
The Browser Dialog Scope activity must be added inside a Use Application/Browser activity and the activities that may trigger the dialog must be placed in the body of the Browser Dialog Scope activity.
For example, this is how the Browser Dialog Scope activity can be configured to handle a Confirm dialog that is triggered when you click a Submit button. When it pops up, the user will chose to click the OK button to proceed.
Default OCR engine
UiPath Studio now lets you set a default OCR engine for any new UIAutomation Scope (Use Application/Browser).
With this new Project Setting, you can predefine your preferred OCR engine, and every new UIAutomation Scope will automatically use it—along with its custom settings configured in the Project Settings panel. This makes automation more consistent and saves time when working with OCR-heavy processes.
Set Value renamed Update UI Element
The Set Value activity has been renamed Update UI Element to better reflect its purpose—allowing you to seamlessly update fields in an application without worrying about selectors. We hope this change makes it more intuitive, especially for users new to semantic automation. Let us know what you think! 
Dialog Handling App Card options and Project settings
Starting with UI Automation v25.2 we introduced the Browser Dialog Scope activity which can handle common JavaScript browser dialogs (alert, confirm, prompt), in Chrome or Edge, both in Windows and Cross-platform projects. The activity is not yet available for the Firefox browser.
From version 25.4 we complemented the Browser Dialog Scope functionality with browser dialog handling options added to the Use Application/Browser activity.
The new Dialog Handling options section in the App Card allows users to describe how to auto-dismiss browser dialogs (which types of dialogs to dismiss and what response to give to confirm and prompt dialogs).
- Dismiss Alerts
- Dismiss Confirms + Confirm dialog response
- Dismiss Prompts + Prompt response text + Prompt dialog response
We have also added similar project settings for Dialog Handling, which work as defaults for the Use Application/Browser Dialog Handling options.
- Windows projects: UI Automation Modern > Application/Browser
- Cross-platform projects: UI Automation > Application/Browser
AppSignatures package for Chromium Native signatures
Chromium Native signatures have now their standalone package (UiPath.AppSignatures) that can be used to update the signatures as quickly as possible for a given Driver, without having to change and retest the entire UI Automation package. The new package should be added as a Nuget dependency on our UiPath (Driver) package.
From version 25.4 the AppSignatures package is published together with the Driver package. Version 25.4 of the UiPath.AppSignatures package will be fully compatible with the UiPath.UIAutomation.Activities package v24.10.6 or higher.
For instructions on configuring package dependency and deploying to a remote machine, you can check the official docs page: AppSignatures package for Chromium Native signatures.
Modern Get/Set Clipboard activities available in UI Automation API
Customers working with coded workflows asked for an API for Get from Clipboard and Set to Clipboard activities.
To achieve this, UI Automation v25.4 introduces modern versions of classic activities: Get from Clipboard and Set to Clipboard, in Windows and Cross-platform projects.
Important mention for Cross-platform projects: modern Set Clipboard / Get Clipboard activities will only run on Windows or MacOS. Other operating systems are not supported.
The new modern activities can also be used in coded workflows.
Clipboard based copy-paste execution mode for Type Into activity
When using Hardware events to type with the Type Into activity, some applications don’t receive the text correctly. In these cases, a workaround could be used:
- Set to Clipboard the text you want to type.
- Send Hotkey of
Ctrl+V.
Sometimes, this workaround may also perform faster than the Type Into activity with delay between keys set to 0.
The Type Into activity now offers enhanced flexibility with a configurable clipboard usage strategy. This improvement ensures that text input is both efficient and adaptable, allowing automation to seamlessly handle various application behaviours.
We added a new property, Type by clipboard, which indicates whether the clipboard is used to type the given text. The following options are available:
- Never – Never use the clipboard.
- Always – Always use the clipboard.
- Whenever possible – Use the clipboard when possible. This depends on the OS and the text to be typed (e.g. if any special key is used, then the clipboard will not be used).
WaitForPageLoad property for Get URL activity
The WaitForPageLoad property is already available on most UI Automation activities. Starting with UI Automation v25.4 this property is also available for the Get URL activity, with the following possible values:
- None
- Interactive
- Complete
Window attach mode setting in Project settings
Use Application/Browser activity has the default value for the Window attach mode property equal to Application Instance, which means a Window selector exists in every UI Automation activity placed inside the App Card.
Many automations use different Window selectors for Dev, Test, and Prod target applications. Sometimes developers don’t pay attention to the Window attach mode property of Use Application/Browser. They do their whole project without realizing this and then must clean it up later.
With UIAutomation version 25.4 we introduced a project setting that allows users to default the Use Application/Browser’s Window attach mode property to Single Window. Users can now set it this way in their automation templates.
The new project setting in UI Automation Modern > Application/Browser section, has the following options available and will apply to newly added Use Application/Browser activities:
- Application instance – Inner activities will search in the indicated application instance, including all parent and child windows (alerts, popups, etc.). Other instances of the application are excluded.
- Single window – Inner activities will search only in the indicated window.
Edge browser support in cross-platform projects
Test Suite clients have requested the ability to run their automation tests across Chrome, Edge, and Safari browsers. Previously, Chrome and Edge were supported on Windows projects, while cross-platform projects supported Chrome and Safari. However, there was no project type that enabled testing across all three browsers.
We’ve now added Edge browser support for cross-platform projects, allowing users to develop and maintain a single project for comprehensive cross-browser testing. This enhancement simplifies automation efforts and improves consistency across platforms.
New modern activity – Window Operation
The new modern activity Window Operation can be used to perform various operations on the specified window element.
This activity must be added inside a Use Application/Browser activity, and the window on which to perform the operation can be:
- Main application window or Input Element - Apply the operation to the window specified either by the parent Use Application/Browser activity or through the Input element property.
- Specific application window - Apply the operation to the indicated window.
Closest matches information in exception message
In classic UIAutomation activities, when a target UI element isn’t found, the exception message includes information about the closest matches. Previously, for modern activities, this information was only available in the output panel and logs.
Starting with UIAutomation version v25.10.14-preview, the closest matches are now also shown directly in the “Runtime execution error” window. This makes it easier for users to copy and share the details with developers for faster troubleshooting.
Sticky “Enable Native Text” option in selection helper
The Enable Native Text setting in the UI Automation Selection Helper is now persistent. Similar to the behavior of the Enable Computer Vision toolbar button, once a user enables this option, it remains active the next time Selection Helper is opened. This enhancement addresses client feedback by eliminating the need to manually re-enable the option for each UI element.
“UnblockInput” Property Added to Modern Click Activity
The classic Click activity includes an UnblockInput property that helps handle pop-ups or modal dialogs that block the main UI thread. This functionality was previously missing in the modern Click activity.
Starting with UIAutomation v25.10.14-preview, the Unblock input property is now available in the modern Click activity. It should be used when the click action triggers a modal dialog or any other blocking UI element, ensuring the automation flow can continue smoothly without interruption.
