Release notes

To learn what has changed, check out the release notes.

v23.4.10

Release date: 26 October 2023

Improvements

For this release, we brought minor improvements and bug fixes to the activity package.

v22.10.10

Release date: 26 October 2023

Improvements

For this release, we brought minor improvements and bug fixes to the activity package.

v23.10.3

Release date: 23 October 2023

New features and improvements

Browser

When the browser closes unexpectedly or when it's closed during Windows shut down, the Restore pages pop-up window is displayed. This behavior can break the automation if no specific logic is implemented on browser opening (for example, checking if the pop-up window appears and closing it with a Click activity). We implemented a change that prevents the Restore pages pop-up window from appearing when opening the browser.

Automating multiple browser instances running with multiple user profiles at the same time is now supported. This feature allows users to design automations with multiple browser instances opened under different profiles for Chrome, Edge, and Firefox.

You can now install the Firefox, RDP, and VMware extensions directly from UiPathRemoteRuntime.msi.

UI Automation Modern

The following activities have been hidden from the Modern experience:

• OCR Text Exists
• Click OCR Text
• Double Click OCR Text
• Hover OCR Text
• Find OCR Text Position

To see these activities in the Activities panel, select the Classic filter.

Extended Trigger-based Attended Automation

For situations in which you need to identify the type of native events trigged when you interact with certain UI elements in an application, we introduced a new tool integrated with UI Explorer, namely Event Inspection Tool, which can be used for configuring the Application Event Trigger activity. The tool captures and monitors all the selected event types, enabling you to analyze the actions performed and, if applicable, diagnose issues.

We've added support for many events through the Application Event Trigger activity: HTML events, such as Download changed, Tab activated, Tab created, Tab removed, and Tab updated; a new WEBCTRL event, Selection change; and UI-based events: Appeared, Disappeared, Text changed, Focus gained, Focus lost, Invoked, Selected, Deselected, and Toggled.

We also added support for WEBCTRL based native events in native embedded browsers (such as Slack, Discord, or Electron test app).

The Application Event Trigger activity can now be used with coded workflows. As a result, we also introduced a way to monitor multiple target elements with a single Application Event Trigger and allow the number of monitored targets to be dynamic (the monitored targets may change after design time). Prior to this, a triggered workflow with an Application Event Trigger only monitored a single target element, requiring you to create a triggered workflow for each target element you wanted your automation to monitor.

SAP

We added support for the following SAP WebGUI elements: SAP Menu items (using the Select Item activity), SAP Toolbar buttons (using the Click Toolbar Button activity), and SAP Trees (including stable identification of the Trees and reliable automation across all browsers and all SAP FIORI versions). Note than you can use the existing capabilities to automate various other SAP WebGUI elements, such as ABAP lists, Context menus, Pictures, Textedit controls, Generic Object Services, Dialog boxes, and Table controls.

Multi-monitor scaling awareness is now supported. This allows a multi-monitor setup where each monitor has a different scaling percentage and can move the SAP window freely across the monitors. To support this feature, a new project setting is available in Studio: Project Settings > UI Automation Classic > SAP > Enable additional scaling.

We made some improvements to the SAP Table Cell Scope activity. Filtering now includes content for table cells (for columns and rows). Before, the identification of columns in an SAP table was based on their display name, causing issues when a table had several columns with similar names. Now, these scenarios are automatically identified and you can select other attributes instead, such as ColumnName. Additionally, you can filter on columns and rows to use any other property to identify elements. Two property names were renamed to support this improvement: Column Name became Column Name / Filter, and Row Number became Row Number / Filter.

General improvements

We added support for automating legacy versions of Oracle Siebel CRM Applications (e.g. 7 or 8).

We added support for the CTable component of the Clarity Java application.

Added the Copy to Clipboard option for all UI Automation dialog messages.

We improved the error messages displayed for nested remote sessions.

Computer Vision in Unified Target

In this version of the activity package, we optimized core issues by accounting for each targeting method's relevancy in terms of targeting power and resilience to UI changes and we addressed the main limitations in the 23.4.x. As a result, UI Automation Table Extraction is now Computer Vision boosted when indicating full tables and table extraction is also enabled for pure Computer Vision scenarios; you can change the OCR engine as you can now select a custom OCR engine besides the embedded UiPath Screen OCR; Computer Vision is enabled by default in scopeless activities further boosting fully loaded targets (having both selectors and Computer Vision descriptors); and we optimized the experience of indicating UI elements by updating the reconciling logic between Driver and Computer Vision regarding bounding boxes. We have thus continued to pursue our vision of a unified UI Automation user experience where both pure Computer Vision and combined Computer Vision plus Driver powered automations can be created without the need for the user to be aware of the intricacies of each targeting method. More specific details can be found below.

A new hierarchical concept is now applied to Unified Target, taking into account each targeting method and its relevancy in terms of targeting power and resilience to UI changes. Hence, selectors are now considered the primary targeting method, Computer Vision is a secondary targeting method, and Image is a tertiary targeting method (and is now disabled by default). Before this, all targeting methods were trying to identify the target element simultaneously and whichever targeting method was able to find it first was used. Also, a new setting, Wait for primary targeting method until timeout, has been added in Project Settings > UI Automation Modern. The setting is set to True by default and allows the primary targeting method to consume its full timeout until any fallback targeting method can be used.

Computer Vision is now integrated in the Table Extraction wizard. You can now simply indicate full tables without having to indicate a relevant table cell first. Since Computer Vision is able to see entire tables, this functionality is now also used at design-time to correct faulty selector-based extraction when indicating a full table. At runtime, however, we don't have a Computer Vision fallback mechanism in place just yet when selector-based extraction has issues extracting full tables. You can extract pure Computer Vision tables as well without having to switch to a CV Screen Scope activity or a CV Extract Table activity for scenarios where selectors are not available at all, such as remote desktops without the remote run-time installed. On top of that, you can now also extract tables spanning across multiple pages in pure Computer Vision scenarios by indicating the Next button in the wizard.

Using the same logic as in the CV Extract Table activity, extracting scrollable tables in pure Computer Vision scenarios is now also possible in the Table Extraction wizard, as well as extracting scrollable text using CV Get Text. The Log Table Scroll Data project setting (Project Settings > Computer Vision > Robot Logging) has been renamed to Log Scrollable Content Extraction Data and it now covers Computer Vision Table Extraction, Table Extraction for scrollable tables in pure Computer Vision scenarios, and CV Get Text with scrollable text content.

In the Use Application/Browser activity, in addition to the Computer Vision embedded OCR engine, namely UiPath Screen OCR, you can now use a custom OCR engine to enhance the text extraction in Computer Vision when used in Unified Target. The OCR engine can be changed in each Use Application/Browser activity by going to the activity card > choosing the hamburger menu that appears next to the informative screenshot after indicating an UI element > selecting OCR Engine > Custom OCR Engine. When this option is selected, a panel is added in the activity card where you can drop a different OCR engine activity than the embedded one. This only affects the Computer Vision targets, as the rest of the OCR activities still use the default OCR set in Project Settings > OCR section.

As the happy path is having fully loaded targets, Computer Vision is now auto-enabled for indicating in scopeless activities (that can be used outside an Use Application/Browser scope) when it is also enabled in Project Settings.

When Computer Vision is enabled as a targeting method in Project Settings, the App/Web Recorder now captures Computer Vision descriptors as well.

The Computer Vision toggle state (enabled/disabled) in the Selection Options helper is now stored and persists throughout all the indicate sessions in the same Use Application/Browser scope activity. Every new Use Application/Browser scope activity begins with the default Computer Vision project setting for each technology (Project Settings > UI Automation Modern > Targeting methods - Desktop applications / Web browsers / Java / SAP > Computer Vision).

We adapted our reconciling logic between Driver and Computer Vision regarding bounding boxes by matching the two targets to avoid indicating a Computer Vision-only target and to favor fully loaded targets. Selecting Computer Vision-only targets should now be reserved for scenarios like remote desktop with no access to selectors.

Strict selector failures are now displayed in the logs as warnings alongside ten suggestions of the closest selector matches that can be used to replace the faulty selectors. This feature is set to True by default in Project Settings > UI Automation Modern > Show closest matches in the 'Element not found' error message.

The Computer Vision screenshot no longer needs an initial delay, so now the start of an indicate session is faster.

UI Automation APIs

If you prefer to code when building automations, you can now achieve this using coded automations. Coded automations support UiPath services, such as UI Automation activities, and allow you to create hybrid automations, by integrating them with low-code automations.

Visit the UI Automation APIs section to browse through the available APIs and Coded Automations Introduction to learn how to create coded automations.

Bug fixes

• Fixed the broken Active Accessibility support for web pages containing IFrame elements or PDFs in Chrome and Edge version 117, which caused <ctrl /> selectors to fail.

  Also added the option to pass extra command-line arguments to the browser opened using the Open Browser / Use Browser activities. This can be done by setting the appropriate environment variable using the Set Environment Variable activity:

  • UIPATH_EXTRA_CMD_ARGS_CHROME

  • UIPATH_EXTRA_CMD_ARGS_EDGE

  • UIPATH_EXTRA_CMD_ARGS_FIREFOX

  These variables can be used to force-enable the Active Accessibility support in Chrome and Edge to avoid issues like the broken Chrome/Edge Active Accessibility support from versions 114 and 117.

  For Chrome, set the environment variable UIPATH_EXTRA_CMD_ARGS_CHROME with the value --force-renderer-accessibility=complete.

  For Edge, set the environment variable UIPATH_EXTRA_CMD_ARGS_EDGE with the value --force-renderer-accessibility=complete.

• MV3 browser extensions failed to initialize when using Microsoft Edge (versions 115 and newer) in Private mode. We have implemented a workaround for this issue that affected all MV3 extensions, not just the UiPath Extension for Microsoft Edge.
• We addressed some extension initialization issues affecting the Open Browser and Use Browser activities by adding six UI Automation Classic – Browser project settings: Extra arguments for OpenBrowser Chrome/Edge, Custom executable path for OpenBrowser Chrome/Edge, and Enable retry for OpenBrowser Chrome/Edge.
• The Table Cell Scope activity didn't recognize column names when SAP WinGUI was set in Japanese.
• Data Scraping returned empty cells for Salesforce reports.
• Support for Chrome/Edge running in App Mode is now available in the self-hosted MV2 browser extension installed via Group Policy Offline.

• When installing extensions with Admin rights, UiPath.Common is now automatically deployed to %ProgramFiles(x86)%\UiPath\UiPath.Common. When installing extensions without Admin rights, UiPath.Common is now automatically deployed to %LocalAppData%\Programs\UiPath\UiPath.Common.

• We added support for web pages using the ServiceNow Framework.

• The tableCol tag in the selector prevented some table elements from being identifiable.
• You can now automate applications running under a different Windows User (other than the one running UiPath Robot/Studio), without having to run Robot/Studio as administrator.
• In a cross-platform Use Browser activity, the browser connection failed or became unresponsive when more than one tab was opened at design time on the serverless machine where the connection got confirmed, the user was logged out of Studio, the user deleted her/his personal workspace in Orchestrator, or when encountering a communication error with Orchestrator.
• Adding a selector from an activity to Object Repository failed with the "The operation was canceled" error message when the reuse search took more than three seconds.
• The Use Application/Browser activity threw an exception at design time in StudioX due to the asterisk indicating a property field is required.
• The Send Hotkey activity caused the .xaml file to be shown as unsaved.
• Image screenshot was still captured even when Image was disabled as a targeting method in Project Settings.

• The You Are Calling The Computer Vision Server Too Often [429] error message displayed when reaching the Computer Vision rate limit has been changed to Error: Rate limit exceeded. If you're on a free tier, consider upgrading to paid license. If already on a paid license, please contact UiPath for further upgrade options.

• The modern Get Text activity did not extract text in pure Computer Vision scenarios.

v23.4.9

Release date: 5 October 2023

Bug fixes

• Fixed the broken Active Accessibility support for web pages containing IFrame elements or PDFs in Chrome and Edge version 117, which caused <ctrl /> selectors to fail.

  Also added the option to pass extra command-line arguments to the browser opened using the Open Browser / Use Browser activities. This can be done by setting the appropriate environment variable using the Set Environment Variable activity:

  • UIPATH_EXTRA_CMD_ARGS_CHROME

  • UIPATH_EXTRA_CMD_ARGS_EDGE

  • UIPATH_EXTRA_CMD_ARGS_FIREFOX

  These variables can be used to force-enable the Active Accessibility support in Chrome and Edge to avoid issues like the broken Chrome/Edge Active Accessibility support from versions 114 and 117.

  For Chrome, set the environment variable UIPATH_EXTRA_CMD_ARGS_CHROME with the value --force-renderer-accessibility=complete.

  For Edge, set the environment variable UIPATH_EXTRA_CMD_ARGS_EDGE with the value --force-renderer-accessibility=complete.

v22.10.9

Release date: 5 October 2023

Bug fixes

• Fixed the broken Active Accessibility support for web pages containing IFrame elements or PDFs in Chrome and Edge version 117, which caused <ctrl /> selectors to fail.

  Also added the option to pass extra command-line arguments to the browser opened using the Open Browser / Use Browser activities. This can be done by setting the appropriate environment variable using the Set Environment Variable activity:

  • UIPATH_EXTRA_CMD_ARGS_CHROME

  • UIPATH_EXTRA_CMD_ARGS_EDGE

  • UIPATH_EXTRA_CMD_ARGS_FIREFOX

  These variables can be used to force-enable the Active Accessibility support in Chrome and Edge to avoid issues like the broken Chrome/Edge Active Accessibility support from versions 114 and 117.

  For Chrome, set the environment variable UIPATH_EXTRA_CMD_ARGS_CHROME with the value --force-renderer-accessibility=complete.

  For Edge, set the environment variable UIPATH_EXTRA_CMD_ARGS_EDGE with the value --force-renderer-accessibility=complete.

v22.4.11

Release date: 5 October 2023

Bug fixes

• Fixed the broken Active Accessibility support for web pages containing IFrame elements or PDFs in Chrome and Edge version 117, which caused <ctrl /> selectors to fail.

  Also added the option to pass extra command-line arguments to the browser opened using the Open Browser / Use Browser activities. This can be done by setting the appropriate environment variable using the Set Environment Variable activity:

  • UIPATH_EXTRA_CMD_ARGS_CHROME

  • UIPATH_EXTRA_CMD_ARGS_EDGE

  • UIPATH_EXTRA_CMD_ARGS_FIREFOX

  These variables can be used to force-enable the Active Accessibility support in Chrome and Edge to avoid issues like the broken Chrome/Edge Active Accessibility support from versions 114 and 117.

  For Chrome, set the environment variable UIPATH_EXTRA_CMD_ARGS_CHROME with the value --force-renderer-accessibility=complete.

  For Edge, set the environment variable UIPATH_EXTRA_CMD_ARGS_EDGE with the value --force-renderer-accessibility=complete.

v21.10.10

Release date: 5 October 2023

Bug fixes

• We added support for the CTable component of the Clarity Java application.

• Fixed the broken Active Accessibility support for web pages containing IFrame elements or PDFs in Chrome and Edge version 117, which caused <ctrl /> selectors to fail.

  Also added the option to pass extra command-line arguments to the browser opened using the Open Browser / Use Browser activities. This can be done by setting the appropriate environment variable using the Set Environment Variable activity:

  • UIPATH_EXTRA_CMD_ARGS_CHROME

  • UIPATH_EXTRA_CMD_ARGS_EDGE

  • UIPATH_EXTRA_CMD_ARGS_FIREFOX

  These variables can be used to force-enable the Active Accessibility support in Chrome and Edge to avoid issues like the broken Chrome/Edge Active Accessibility support from versions 114 and 117.

  For Chrome, set the environment variable UIPATH_EXTRA_CMD_ARGS_CHROME with the value --force-renderer-accessibility=complete.

  For Edge, set the environment variable UIPATH_EXTRA_CMD_ARGS_EDGE with the value --force-renderer-accessibility=complete.

v20.10.15

Release date: 5 October 2023

Bug fixes

• Fixed the broken Active Accessibility support for web pages containing IFrame elements or PDFs in Chrome and Edge version 117, which caused <ctrl /> selectors to fail.

  Also added the option to pass extra command-line arguments to the browser opened using the Open Browser / Use Browser activities. This can be done by setting the appropriate environment variable using the Set Environment Variable activity:

  • UIPATH_EXTRA_CMD_ARGS_CHROME

  • UIPATH_EXTRA_CMD_ARGS_EDGE

  • UIPATH_EXTRA_CMD_ARGS_FIREFOX

  These variables can be used to force-enable the Active Accessibility support in Chrome and Edge to avoid issues like the broken Chrome/Edge Active Accessibility support from versions 114 and 117.

  For Chrome, set the environment variable UIPATH_EXTRA_CMD_ARGS_CHROME with the value --force-renderer-accessibility=complete.

  For Edge, set the environment variable UIPATH_EXTRA_CMD_ARGS_EDGE with the value --force-renderer-accessibility=complete.

v23.4.8

Release date: 2 August 2023

Bug fixes

• Fixed a bug for the Send Hotkey activity that caused the .xaml file to be shown as unsaved.
• Fixed a bug for the Use Application/Browser activity that threw an exception at design time in StudioX due to the asterisk indicating that a property field is required.
• We added support for the CTable component of the Clarity Java application.

v22.10.8

Release Date: 2 August 2023

Bug fixes

• Fixed a bug for the Send Hotkey activity that caused the .xaml file to be shown as unsaved.
• Fixed a bug for the Use Application/Browser activity that threw an exception at design time in StudioX due to the asterisk indicating that a property field is required.

v22.4.10

Release date: 2 August 2023

Bug fixes

• For MV3 extensions, the browser loads the extension later, after the web pages have loaded. To solve this kind of issues, we added the UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS environment variable that allows configuring the Open Browser timeout.
• A "Value does not fall within the expected range" error occurred when using the Data Scraping wizard (Extract Structured Data activity) in Microsoft Edge in IE Mode.
• An error occurred when using the Data Scraping wizard (Extract Structured Data activity) on a table with an empty column header.
• We added support for the CTable component of the Clarity Java application.

v22.4.9

Release date: 8 June 2023

Bug Fixes

The latest Chrome and Edge updates to version 114 introduced a breaking change to the way support for Active Accessibility is enabled. This caused automation processes to fail when trying to interact with browser screens such as the Print popup or PDF viewer.

v21.10.9

Release date: 8 June 2023

Bug Fixes

• The latest Chrome and Edge updates to version 114 introduced a breaking change to the way support for Active Accessibility is enabled. This caused automation processes to fail when trying to interact with browser screens such as the Print popup or PDF viewer.
• A "Value does not fall within the expected range" error occurred when using the Data Scraping wizard (Extract Structured Data activity) in Microsoft Edge in IE Mode.
• An error occurred when using the Data Scraping wizard (Extract Structured Data activity) on a table with an empty column header.

v20.10.14

Release date: 8 June 2023

Bug Fixes

The latest Chrome and Edge updates to version 114 introduced a breaking change to the way support for Active Accessibility is enabled. This caused automation processes to fail when trying to interact with browser screens such as the Print popup or PDF viewer.

v23.4.7

Release date: 7 June 2023

Bug Fixes

The latest Chrome and Edge updates to version 114 introduced a breaking change to the way support for Active Accessibility is enabled. This caused automation processes to fail when trying to interact with browser screens such as the Print popup or PDF viewer.

v23.4.6

Release date: 7 June 2023

Improvements

This package version includes various accessibility improvements.

v22.10.7

Release date: 7 June 2023

Bug Fixes

The latest Chrome and Edge updates to version 114 introduced a breaking change to the way support for Active Accessibility is enabled. This caused automation processes to fail when trying to interact with browser screens such as the Print popup or PDF viewer.

v22.10.6

Release date: 7 June 2023

Bug fixes

• Fixed a bug in CV Screen Scope that was causing the local server to keep returning OCR boxes even when UiPath Screen OCR was removed from the activity card or from Project Settings.
• Fixed a bug that caused selector generation to fail for Remote Desktop when the Remote Desktop Client was published as a RemoteApp.
• Fixed an issue which caused the Click Trigger activity to slow down the target application when opening a web page in Edge IE mode with Protected Mode turned off.
• For MV3 extensions, the browser loads the extension later, after the web pages have loaded. To solve this kind of issues, we added the UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS environment variable that allows configuring the Open Browser timeout.
• When installing extensions using the Native Host Only method, the file for the self-hosted extension is also generated, so that it can be added to the ExtensionInstallForceList policy.

v23.4.5

Release date: 27 April 2023

New Features and Improvements

UI Automation Browser Connections can now be used in Cross-platform projects.

You can create and edit a connection only in Studio Web (currently in preview) and consume it both in Studio Web and Studio Desktop.

The feature can be run only with Serverless Automation Cloud™ Robots; attempting to run the feature with local robots results in failure.

For further information, please refer to the dedicated UI Automation Browser Connection documentation page.

v23.4.4

Release date: 27 April 2023

New Features and Improvements

General

To decrease the package size for runtime, especially for cross-platform projects, the UiPath.UIAutomation.Activities package was split into design time package and runtime packages, as follows:

• UiPath.UIAutomation.Activities - design time package

• UiPath.UIAutomation.Activities.Runtime - runtime package; targets Windows and Windows-Legacy projects

• UiPath.UIAutomation.Activities.Runtime.Portable - runtime for portable package; targets Cross-platform projects

Two new options are available in UI Automation Modern and UI Automation Classic Project Settings. Open browser timeout (seconds) allows you to configure the browser startup timeout, and Inject Js Script – Execution world applies the InjectJs.ExecutionWorld setting globally. The Open browser timeout value can also be configured through the UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS environment variable.

You can now use the Open Application and Use Application/Browser activities to open the Power BI Desktop application.

We added Check support for more browser checkboxes.

We improved the Select Item activity to support complex HTML dropdowns, like non-native and non-Sap Fiori/Salesforce dropdowns.

The error prompt that indicates a version mismatch between the UiPath Remote Runtime component and the UiPath.UIAutomation.Activities package now contains a download link for the correct UiPathRemoteRuntime.msi version.

The UI Explorer selector no longer includes the hidden root for tree nodes.

UI Explorer no longer restores Studio window after indicating an element.

The Modifiers field for event data is now mapped to the NKeyModifier enum and returns a string (such as Shift, Alt, or Ctrl) instead of an integer when the toString() method is called.

If a Modern activity is used in a project, this information is now included in the published package, and is then available in Orchestrator. This feature requires Studio 2023.4 or later.

Browser extensions

We added the webRequest permission to the Chrome and Edge extensions to allow using the webRequest API. The Chrome and Edge extensions v2023.4 were published on the Web Stores with new extension IDs. The self-hosted extensions, used for Group Policy Offline installations, have also been updated with this permission, but they keep the same extension ID.

When installing extensions using the Native Host Only method, the file for the self-hosted extension is also generated, so that it can be added to the ExtensionInstallForceList policy.

Improved support for Chromium-based embedded browsers

We improved support for Chromium-based embedded browsers (Electron, CEF 103+) and added support for orphaned WebView2 windows.

We added support for Chromium Native versions 108, 109, and 110.

Cross-origin call forwarding for Chromium Native embedded browsers is now supported. This applies to CEF-native and Electron web controls.

We added support to automate CefSharp widgets embedded in applications with multiple UI threads.

We improved support for Electron applications that create multiple BrowserViews inside a single BrowserWindow. Each view can now be automated.

Trigger-based Attended Automation

In the context of the Trigger-based Attended Automation initiative, where execution performance is critical, we improved event monitoring usability and performance by implementing new sets of events supported by different types of application technologies: Active Accessibility with <wnd> and <ctrl> tags, Web with <webctrl> tags, and Java with <java> tags. The events are available through the new Application Event Trigger activity, which helps set up a trigger based on a native event for any type of UI element.

Also in the context of Trigger-based Attented Automation, we have migrated the most used Classic triggers to the Modern framework. The new Click Event Trigger and Keypress Event Trigger modern activities are designed to identify the elements via a unified target concept, use an Object Repository element and offer a friendlier user interface.

An important reason we provide them as part of the Trigger-based Attented Automation solution is that these triggers can block the original event and replay it later, or simply ignore it. This specific capability allows implementation scenarios like a form submission being stopped until all the fields are correctly filled in.

The old classic activities Click Trigger and Key Press Trigger are still visible in this version of the package if the Classic filter is added in Activities tab.

For all trigger activities (Application Event Trigger, Click Event Trigger and Keypress Event Trigger) we have the following behavior:

• When the activity is inside of a Trigger Scope, the activity doesn’t display the Scheduling mode and Enabled properties. In this case, the Scheduling mode property is available in the Trigger Scope activity.

• When the activity is added without a Trigger Scope, the Trigger Scope is automatically generated and the Scheduling mode and Enabled properties are displayed for the trigger activity.

Some existing classic trigger activities can be used both within a triggered workflow (new model) or within a Trigger Scope activity (old model):

• Hotkey Trigger

• Mouse Trigger

• Click Image Trigger

• System Trigger

• SAP Session Attributes Changed Trigger

• Element State Change Trigger

• Element Attribute Change Trigger

The Element State Change Trigger and Element Attribute Change Trigger activities, however, are now hidden from the activity package. If they are found in the workflow, they can be used, but they can no longer be added to the canvas.

The Set Text activity just got a modern version which can identify targets with the unified target concept and it can use an Object Repository stored element. Moreover, it can cache the target element to increase the execution speed when executing repeatedly, for example, when synchronizing text between multiple UI elements.

Native WPF support

WPF applications can be automated through Active Accessibility, which works out of the box unless accessibility support is disabled for that application. For example, accessibility support can be lost following an application update, in which case you might not be able to target individual elements in specific areas.

UiPath.UIAutomation.Activities v2023.4 provides access to UI Elements using native WPF API, instead of the generic Accessibility API currently used. This capability aims to reliably automate WPF applications using selectors with <wpf> attributes, resilient to change.

This feature is available through a new Project Setting: UI Automation Modern > Targeting methods - Desktop applications > Generate native WPF selectors (Preview). The default value for this option is False.

In v2023.4 this feature is under the Preview flag, as future versions may introduce breaking changes.

UI Automation Modern

The Inject JS Script activities, both Classic and Modern, have a new Execution world property field, which allows you to set the JavaScript world for a script to execute within. The Isolated option is for the activity's previous functionality, allowing the content script to make changes to its JavaScript environment without conflicting with the page. The new Page option allows the script to interact with the page as well.

Another modern activity that was added to the activity package is Check Element. You can now check the state of enabled or disabled elements in a curated way and perform actions based on their state, for example, when creating an automation that navigates a multi-page application to scrape data and you reach the last page, the next page button gets disabled and you need to stop scraping.

Modern activities require an application card/scope to minimize the searching area of the target element, thus, increasing the automation reliability. However, now no application card/scope is required when the activities receive an UiElement as input. So, all Modern activities have been updated accordingly.

Added support for writing a list of elements when using the Get Attribute activity in StudioX and saving it to Excel.

Improved matching for the Image selector by using the scale factor ratio (design time over runtime).

Improved the return of object types for the Get Attribute activity based on the selected attributes.

Added a red indicator for duplicate column names in the Table Extraction recorder.

SAP

We added support for reliable automation of SAP WebGUI using hardware events, including accurate identification of elements, stable attributes prefixed with sapweb-ls (for LightSpeed controls) or sapweb- (for SAP Scripting controls), and the ability to reliably use UI Automation activities with Hardware Events (Click, Type Into, Select Item, etc.). In this release, we added specific support for the following elements: SAP buttons (icons, push buttons, and radio buttons), SAP input fields, SAP dropdown lists, and SAP checkboxes.

We added specific support for SAP Fiori Calendars. Now, with the Select Dates in Calendar activity, you can easily automate calendars for all SAP Fiori-based systems, such as SAP S/4HANA or SAP SuccessFactors.

We added support for SAP Fiori Process Flow controls, including the ability to extract the status of these elements. We also introduced the concept of complex attributes, which have a ui5c- prefix and are represented in the JSON format. Note that the content of the new attributes is persistent, but the strings aren't reliable. For example, you could have {“a”:”value1”, “b”:”value2”} for the first call, and {“b”:”value2”, “a”:”value1”} for the next call.

Computer Vision

Computer Vision is now part of the Unified Target solution to help you reduce the complexity of building UI-based automations when you need both selectors and Computer Vision descriptors.

Adding Computer Vision to Unified Target increases the reliability and resilience to changes in UI-based automation: often, you do not control application UI changes; the UiPath robots must deal with these situations out of the box and not break, remaining uninfluenced by the UI deterministic changes.

Computer Vision can be a deep drill for targeting UI elements in the rare cases where the driver fails to ‘see’ certain UI elements or sometimes it can be the only viable technology like in the case of VDI automation. Other use cases of using Computer Vision span everywhere between these mentioned scenarios.

In terms of portability, any automation indicated in Native Windows can be reused in Remote Desktop environments by replacing the window selector.

In Project Settings > UI Automation Modern, the happy path for Computer Vision is to be enabled by default for Desktop applications, Java, and Web browsers and disabled by default for SAP as the happy path for SAP is using the strict selectors.

Computer Vision can be enabled as well from the Selection Options Helper new vertical bar design and it also has a keyboard shortcut (F8) to do so.

The CV Refresh activity is hidden from the package and can no longer be used in new projects.

Known Issues

If the Enable WebView2 Native Automation setting (from Project Settings > UI Automation Classic > Browser) is set to True, web selectors are generated by default for trigger activities. Because the UI Automation trigger activities don't currently support embedded browser apps, the events aren't triggered if default generated selectors (web selectors) are used. As a workaround, AA selectors can be used by changing the UI Framework from Default to Active Accessibility while indicating the target UI Element. Support for embedded browser apps for UI Automation trigger activities will be added in a future version.

A Java Runtime Environment limitation causes unexpected modifiers behavior for Click and Mouse released events triggered for the middle and right buttons when used from the Application Event Trigger monitoring activity, as follows: an action with the middle button, without modifiers, reports an alt modifier; however, the same action executed with the middle button and an altmodifier reports correctly. An action with the right button, without modifiers, reports a win/meta modifier; the same action executed with the right button and a win/meta modifier reports correctly.

SendWindowMessages for WPF native is not currently supported.

Bug Fixes

• You can now automate Acrobat Reader with version newer than 2022.003.20258 even if you have the Enable Protected Mode option enabled by default. For details, see Security Option in Adobe Reader DC.
• The Click activity failed on specific form elements when used with the Simulate input method. Now you can use the Enable workaround for simulate click with MV3 extension option in Project Settings.
• With some websites, selector validation failed in Edge IE Mode. This issue occurred when a web page URL opened in Edge IE Mode was redirected to another URL compared to the one in Edge Chromium.
• Browser automation activities intermittently failed to communicate with the Chrome extension, causing the following error: "Cannot communicate with the browser, please check the UiPath extension." This issue occurred on slower machines or machines with a high CPU load. To overcome this, the Chromium browser communication timeout was increased to 30 seconds.
• Fixed a bug that prevented you from indicating tab elements in the Internet Explorer Developer Tools window.
• With the UIAutomation Classic > Browser > Enable WebView2 Native Automation Project Setting set to True, in certain SAP Fiori pages opened inside SAP Business Client, WND and CTRL selectors were generated instead of HTML and WEBCTRL.
• Fixed a bug that caused selector generation to fail for Remote Desktop when the Remote Desktop Client was published as a RemoteApp.
• Fixed a bug that caused the UiPath Executor to crash when using a Get Visible Text activity on a Java application.
• For Java Runtime Environment versions 13 to 19, indicating a table cell when the cell editor is opened at that cell now returns a valid element, with the role corresponding to the editor (such as text). Before, the resulting element was unusable.
• Fixed an issue which caused the Click Trigger activity to slow down the target application when opening a web page in Edge IE mode with Protected Mode turned off.
• Fixed an issue with Table Extraction which prevented extracting values from an input field. Before the fix, the default text attribute generated in the metadata used the innerText HTML property to retrieve the text. Starting with v2023.4, newly generated workflows and activities use fulltext as the default attribute. This new attribute uses the same approach as the full-text scraping method. To use the innerText property in new activities, you can manually edit the metadata and change the attribute name from fulltext to text.
• Fixed a bug in Data Scraping that was causing the Join data table wizard to fail with ‘column not found’ error message due to column index being incorrectly marked as column name.
• Fixed a bug that was causing, in some cases, the CV Extract Table activity to stop before the first scroll event when extracting scrollable tables.
• Fixed a bug for the Click activity that was causing the activity to get stuck on a specific element when Input mode was set on Simulate. To solve the problem, the new UnblockInput property has been added to the classic Click activity, which should be used when Click triggers a modal dialog box or other blocking UI.
• Fixed a bug for Modern activities that was causing them not to work properly when culture info interpreted comma as decimal separator.
• Fixed a bug for the Attach Browser activity that was generating a memory leak when using a Browser variable.
• Fixed a bug for the Find OCR Text Position activity that was causing the activity to find an incorrect position when the text includes a special character, such as %.
• Fixed a bug in Object Repository that was causing the Design Data attribute not to be updated correctly when editing a target.
• Fixed a bug for the Type Into, Keyboard Shortcuts, and Mouse Scroll activities that was throwing an invalid warning stating ‘Click Offset is not supported on Simultate Input mode‘.
• Fixed a bug in CV Screen Scope that was causing the local server to keep returning OCR boxes even when UiPath Screen OCR was removed from the activity card or from Project Settings.

v22.10.5

Release date: 27 January 2023

Bug fixes

• The error prompt that indicates a version mismatch between the UiPath Remote Runtime component and the UiPath.UIAutomation.Activities package now contains a download link for the correct UiPathRemoteRuntime.msi version.
• Fixed a bug that was causing, in some cases, the CV Extract Table activity to stop before the first scroll event when extracting scrollable tables.

v22.4.8

Release date: 27 January 2023

Bug fixes

• Fixed a bug which caused selector validation to fail in a Citrix application when two Citrix client windows were available, but only one of them actually matched a remote window.
• Support for Chrome/Edge running in App Mode is now available in the self-hosted MV2 browser extension installed via Group Policy Offline.
• Fixed a bug that was causing, in some cases, the CV Extract Table activity to stop before the first scroll event when extracting scrollable tables.

v22.10.4

Release date: 7 December 2022

Improvements

The UI Automation user interface is now available in Traditional Chinese.

Bug fixes

• The error message displayed when you upgraded the activity package and had an incompatible Remote Runtime version was unclear. The message now clearly states which RemoteRuntime.msi version you need to install.

v21.10.8

Release date: 7 December 2022

Improvements

UI Automation Classic

The visibleInnerText attribute is now available in the Selector Attributes panel from UI Explorer.

Bug fixes

• You can now configure the internal timeout for the Open Browser activity through the UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS environment variable.

v20.10.13

Release date: 7 December 2022

Improvements

UI Automation Classic

The visibleInnerText attribute is now available in the Selector Attributes panel from UI Explorer.

Bug fixes

• The internal timeout for the Open Browser activity has been increased from 20 seconds to 60 seconds. Additionally, you can configure this timeout value through the UIPATH_OPEN_BROWSER_TIMEOUT_SECONDS environment variable.

v22.10.3

Release Date: 27 October 2022

Bug fixes

• Fixed an issue which caused the Check App State branch sequences to not be displayed in StudioX.

v22.10.2

Release date: 27 October 2022

Improvements

General

When you install browser extensions from UiPath Studio Home > Tools > UiPath Extensions, you can now select your preferred method. The available options in the drop-down menu for Chrome/Edge are Group Policy Offline, Group Policy Online, All Users, Current User, Native Host Only. The available options for Firefox are Group Policy Offline, Current User.

After the extension is installed, the installation method remains displayed in the disabled drop-down menu next to the Uninstall button, so that the extension will be uninstalled with the same method used for installation.

All the extension installation methods for Chrome and Edge are now available in the UiPathStudio.msi command line.

Support for Chrome/Edge running in App Mode is now available in the self-hosted MV2 browser extension.

The class attribute is now added to the default selector when it doesn't contain spaces or letters after digits.

The WEBCTRL selector attributes aria-label and aria-labelledby are now available in the default selector.

UI Automation Modern

The modern Use Application/Browser activity can now open browsers in remote environments.

When using the Default framework, the ctrlid attribute is now added to the selector for the following controls: TextBox (input field), Button, RadioButton, CheckBox, PictureBox, ListBox (select item), and ComboBox. The automationid attribute is also added to the selector for the same controls when using the UI Automation framework.

A new Workflow Analyzer rule is now available, UI-PST-001, which enables you to specify the logging level you want to log your Robot logs at.

Auto-anchor detection on Salesforce fields that use the for attribute has been improved and now works much faster.

Mouse Scroll now features the Input Mode property, which enables you to select which input mode you want to use to send the scroll action to the application you are automating.

The Check Element Visibility property has changed its name to Visibility check to make its purpose clearer.

In the Selection Screen, changing existing variable names is no longer possible.

The Take Screenshot activity now supports region selection via the F3 hotkey when indicating on screen.

Support for apps using Qt has been implemented in the UI Automation package. For now, only widgets are supported. No QtQuick/QML support has been added at the moment.

Table Extraction

A new option has been added to the Table Extraction wizard, when used with a Web browser, that enables you to select whether you want to create a new column with the text or URL of a selected element. The Extract URL toggle has been removed, as a result of this change.

Table extraction improvements.

Object Repository

Object Repository now offers an improved Indicate and editing experience when used with the Extract Table Data and For Each UI Element activities.

Arguments are now exposed as editable text in Edit screens for Browsers.

UI Automation Classic

The visibleInnerText attribute is now available in the Selector Attributes panel from UI Explorer.

The title attribute was removed from the list of available attributes for WebCtrl.

Computer Vision

When selecting Refresh with Delay in the Indicate wizard, scrolling resets the timer and the scrolling direction is saved in the activity. Also, there are three new properties for activities impacted by this change: ScrollingDirection, NumberofScrolls, and DelayScreenshotAfterScroll, which enable you to configure this feature.

CJK-OCR now also works with a Computer Vision API Key.

The UiPath Screen OCR activity now supports token authentication, so you no longer need to input the CV API Key if you’re logged into your UiPath cloud account.

The application cards for the CV Extract Table, CV Click, and CV Get Text activities have been updated to resemble their UI Automation Modern counterparts.

When both OCR and CV are requested for the same screenshot, we are now merging the two requests into a single server call. Since the requested UI elements and text are found in the same image, we are thus optimizing for both latency and rate-limiting.

The Computer Vision model now selects anchors automatically for text targets when indicating.

UiExplorer

UiExplorer has been upgraded to ActiPro version 20.1.

The Select Item and Extract Table Data activities, both Classic and Modern, now support working with multiple VB6 classes.

We have added support for automating native Chromium Widgets with on-screen rendering. This feature is supported only for Chromium v80 to v102.

Newtonsoft.Json v13 is now supported by UI Automation.

Java

The default selectors for toolbar buttons in Java applications have the name attribute now added by default to their selectors.

The backgroundColor and foregroundColor properties of Java elements are now exposed as strings containing RGB triplets in selectors.

The Kinaxis Java App is now supported by UI Automation. JGrid table permits cell identification, data extraction, etc.

Cross-platform

UiExplorer is now available in cross-platform projects.

Extensions

The deprecated ExtensionInstallWhitelist and NativeMessagingWhitelist whitelist policies are no longer added when installing the MV3 Chrome and Edge extensions.

If attaching the debugger to the extension background page is not possible (when DeveloperToolsAvailability Group Policy is not set to 1), then the MV3 extension for Chrome/Edge will use the embedded LTS Driver packages.

SAP

The ui5-path attribute is now available in the default selector for Tree items. Also, the Expand Tree activity was improved to support Fiori Tree items.

The Select Item activity has been improved to correctly populate the Item to select field when interacting with SAP Fiori searchable combo boxes, especially for SAP SuccessFactors.

Bug fixes

• Fixed an issue which caused the Type Into activity to fail when using Chromium API input method when page zoom ratio was different than 100%.
• When using remote environments, the Select Item activity would use the default timeout of 30 seconds instead of the timeout set by the user.
• Fixed an issue which caused the Windows Forms application to crash when using an Element Exists activity.
• When using Indicate Element, the element was found but validation failed if there were two Citrix App windows available on the client, but only one of them actually matched a remote window.
• Fixed an issue which caused Java-based applications to crash when the Robot is interacting with a specific type of Swing control (JEditorPane), which renders HTML inside.
• UiExplorer failed to identify elements in a Java application built with a specific customized Java framework.
• The Type Into activity failed to type the ( character in the SAP Web GUI when SimulateType is selected.
• Fixed an issue that caused automations using Java 9 applications launched with JNLP to fail.
• When using Microsoft Edge in IE mode to open a webpage whose URL contains Japanese characters, selector validation failed.
• Fixed an issue that caused Microsoft Endpoint Manager application to crash during robot execution when using the Get Visible Text activity.
• The column tooltip in the Preview section of the Table Extraction wizard was not updated properly if updating changes multiple times while indicating.
• When using the For Each UI Element activity, the number of items limit applied to the list of elements before filtering.
• Fixed an issue which caused forms created with the UiPath.Forms.Activities package version 1.9.5 to be incompatible with UI Automation.
• When adding an application for the first time in Object Repository, all information from that activity is now correctly displayed.
• Fixed an issue which generated the same selector for multiple apps.
• Fixed an issue which caused certain UI Automation activities to throw an exception when used in the Trigger section of a Pick Branch activity.
• Table extraction did not work on certain columns.
• The Select Item activity generated a wrong target in certain situations.
• Fixed a bug which caused an application that uses a specific Java framework to freeze when launched from Studio or when interacting with it through Studio.
• Fixed an issue that caused the target remote application to hang, in the case of an automation running through UiPath Remote Runtime.
• When the scope was defined as a region selection, changing DPI could cause the screen scope to be erroneously displayed while indicating.

Known issues

Important: Erratum 2 November 2022: When using the Use Browser activity in a cross-platform project, there is a Requires Authentication switch displayed that, when selected, opens a Connection drop-down that is not populated with any values. This is a known issue, as this feature pertains to an upcoming capability.

v22.4.7

Release date: 3 August 2022

Bug fixes

• Automating WinForms CefSharp applications performed very slowly.
• When automating Microsoft Edge in IE Mode, selector validation failed due to mismatched URL encoding between Edge and IE.

v20.10.12

Release date: 3 August 2022

Bug fixes

• Azure Windows Virtual Desktop (msdrc.exe) was not supported by UI Automation. The new process name associated with Azure Windows Virtual Desktop has been added, and is now supported.
• When automating Microsoft Edge in IE Mode, selector validation failed due to mismatched URL encoding between Edge and IE.
• When using the Type Into activity with the Simulate Type input method, the number 8 could not be typed in certain applications.

v21.10.7

Release date: 3 August 2022

Bug fixes

• In certain Java environments, the visibility attribute was not correctly populated for AWT dialogs, causing the application to behave incorrectly
• When using the Type Into activity with the Simulate Type input method, the number 8 could not be typed in certain applications.
• Automating WinForms CefSharp applications performed very slowly.
• Certain system exceptions caused too many log entries to be recorded, making debugging cumbersome. To fix this, the log level has been changed from Error to Information.

v22.4.6

Release date: 23 June 2022

Bug fixes

• Certain system exceptions caused too many log entries to be recorded, making debugging cumbersome. To fix this, the log level has been changed from Error to Information.

v22.4.5

Release date: 23 May 2022

Bug fixes

• Multiple accessibility and localization issues have been fixed.
• When using the Check/Uncheck activity on a target that dissappeared, an exception was thrown.
• Fixed some issues regarding F1 help links for activities.

v21.10.6

Release date: 23 May 2022

Bug fixes

• Multiple accessibility and localization issues have been fixed.
• When automating Microsoft Edge in IE Mode, selector validation failed.
• CV Extract Table was unable to refresh the output DataTable when used in a loop.
• Certain Java Konsis apps could not be targeted properly.
• When attempting to deserialize elements from a remote connection, the UI Automation activities sometimes crashed.
• Trying to paste certain types of strings from UI Explorer into Excel cells did not work.

v22.4.4

Release date: 9 May 2022

Improvements

General

The new UiPath Extension for Chrome, based on Chrome's Manifest v3 standard, has been released. This extension is fully backwards compatible, and we highly recommend you to upgrade and use it with your automation processes.

In light of the new cross-platform project type, the UI Automation package has gone through changes and now has a multitude of activities tailored to this new project type. You can read all about it here. Also, to increase the capabilities of the cross-platform projects, the new Extension for Chrome is also available on Mac

Extension management in Studio is now better than ever! The entire user experience has been revamped, offering a smoother interaction overall.

UI Automation Modern

The new For Each UI Element activity enables you to iterate through a set of actions for each UI element you have specified.

The new Inject Js Script Modern activity now offers you full JavaScript capabilities when using the Modern design experience.

A new activity, Drag and Drop has been created to enable you to perform the common drag and drop action, aiding in completing the pallete of actions that simulate human interaction.

A new Project Setting is now available, Runtime browser, enabling you to specify the browser type you want to use at runtime with the Use Application/Browser activity.

You can now use the Use Application/Browser activity with the WebDriver protocol via a new property.

The UI Automation Modern activities package now supports both design time and run time automation in multiple Windows Desktops.

One of the most highly requested features: scroll in Selection Screen, is finally here. Now, when indicating an element, you can scroll the target application without having to pause the selection using F2.

When using the Capture All Elements feature, you can now indicate a specific section of the application you are automating and extract only the elements in that area.

The Capture All Elements feature now only detects the tab in the browser you are indicating, so that toolbars and other additional, unrelated elements displayed in your browser are no longer captured.

The Take Screenshot activity can now be used outside of an Use App/Browser activity, so you can use it to take screenshots of your desktop at any time.

Object Repository now is able to display more than 5 results for multiple screens that have the same selector.

When dropping an Object Repository item over the plus sign in Studio, you are now prompted to automatically create variables based on that object.

The Mouse Scroll activity now supports adding key modifiers to the scroll action via the new Key modifiers property.

The Get Attribute activity now also displays the items attribute if the indicated element supports it.

The Click, Type Into, Check/Uncheck, and Select Item activities now have a new property field, Alter disabled element, which specifies whether you want to interact with UI elements that are disabled in the UI but can still be accessed by the Robot. Also, a new project setting has been added to the Modern activities enabling you to control this property project-wide.

A new project setting has been introduced, called Log audit information, which disables any logs generated by the Use Application/Browser activity. Also, the default logging level of the Use Application/Browser activity is now set to Verbose.

You can now switch between the available frameworks when using the Table Extraction Wizard by using the F4 hotkey.

In the Selection Screen, you can now simply click to select or deselect a highlighted target or anchor, and if you click on an empty area while outside of the add-anchor mode, you can deselect the current selection and view the helper.

The Timeout property of the Use Application/Browser activity is now automatically set to 60 seconds when indicating a window in a Remote Desktop environment.

The Select Item activity can now interact with Salesforce Lightning grouped combo boxes, as well as menu combo boxes.

UI Automation Classic

A new attribute, visibleInnerText, which reflects the actual innerText of the underlying HTML element, was added to UI Explorer.

Chrome Debugger API can now be used to send input to browser tab objects.

Attached browser type no longer replaced on selector app value if it contains a valid .exe name.

We've added support for Azure Windows Virtual Desktop client, which means you can now natively automate Azure Virtual Desktops with UI Automation activities by using the UiPath Remote Runtime and the RDP extension.

URLs can now be extracted from HTML tables. This was possible before only for structured data.

HTML elements with tag name 'HTML' are visible in UiExplorer for Chrome.

The UiPath extension for Java fully supports .jnlp type applications.

Added new injection mechanism for the UiPath extension for Java to facilitate the interaction with the application.

Improved support for Java Konsis and the custom Java Framework McBeans.

The UI Automation activities package now supports automating in nested CitrixApps.

Improved error messages for Setup Extensions and SAP WinGUI.

Implemented automatic fallback to alternative selection methods (AA for Google Chrome or Microsoft Edge and UIA for Firefox) when indicating a special tab in each of these browsers.

The Delayed Restore option from UI Explorer is now enabled by default.

Java versions 16 and 17 are now officially supported by the UI Automation activity package.

Computer Vision

The CV Extract Table activity now has two new properties. Scroll specifies whether you want to extract a scrollable table, and DelayScreenshotAfterScroll, which enables the activity to wait for a specific amount of time after performing a scroll action before taking a screenshot of the target table. The latter is useful for tables that load extra items when scrolling down. Also, when using the CV Extract Table activity, you can now use cell targeting by column and row indexes without the need to hold down the Shift key anymore.

Hitting Delete in the CV Selection Screen now deletes the current selection for quicker workflow building.

The CV Recorder no longer requires an API Key if Interactive Sign-In is used in Studio.

Computer Vision activities can now be used in StudioX by enabling the Show Developer filter.

When using CV Screen Scope, you can now toggle between Window, Element and Region Selection Types by using F3.

SAP

A new activity meant to help you identify any cell inside SAP ALV Hierarchical Table is available: Expand ALV Hierarchical Table. After you identify the cell, this activity can be used with all typical UI activities.

All SAP WinGUI activities support Object Repository integration.

A new project setting, Enforce hard timeout, is now available, enabling you to enforce a hard timeout for all activities performing SAP WinGUI automation.

Breaking changes

• Starting with this version, sending modifier keys with the Click activity when the Input mode property is set to Simulate also sends the modifier keys using Simulate. In previous versions, the modifier keys were sent by using Hardware Events, regardless of the configuration of the Input Mode property, so please note that workflows created with previous versions might suffer breaking changes.
• Fixed a bug that caused a Chromium-based custom browser to be recognized as a regular Windows application after upgrading to UiPath Studio v2019.x.

Bug fixes

• Fixed a bug for Internet Explorer with Developer Tools opened that caused multiple console windows to spawn when opening UI Explorer.
• Fixed a bug for the Send Hotkey activity that was causing the text not to be pasted into cmd.exe when changing the keyboard.
• Generating GetHtmlAncestryInfo selectors timed out on a specific UI element from a large table.
• Fixed a bug that caused some buttons not to be clicked or validated in Java Desktop Application by adding a new java attribute, hasTableAncestor, which is used to bypass tables when searching elements that have the attribute value set to 0.
• Fixed a bug in Internet Explorer 8 for the Type Into activity with Simulate as input mode that prevented the keycode 8 from being typed into a search box.
• Fixed a bug that prevented you from indicating the empty ViewPort space.
• Fixed a bug that prevented you from reading the correct state of a checkbox inside a table in Java applications.
• To clear the text from web pages elements, you can use empty strings with the Set Text activity again, just like in UI Automation v18.4.
• Fixed a bug that caused the UiPath Executor to crash while indicating elements in a Java application that opens another application, which uses native libraries to draw elements on the screen.
• Fixed a bug that prevented you from capturing the selectors from Chrome when in full screen mode.
• Fixed a bug in Data Scraping that was throwing a timeout error when extracting extremely large HTML tables.
• Fixed a bug that was causing the job to stop due to searching for <ctrl> selectors in parallel.
• Fixed a bug that was crashing the target application in specific cases when trying to capture a selector using Active Accessibility.
• Fixed a bug that prevented you from identifying certain parts of a Java application.
• Fixed a bug in Internet Explorer that was causing the Activate Window event to fail with a timeout error, after applying the Microsoft Update KB5005031.
• Fixed a bug in Firefox support, that caused SalesForce attributes to not appear on selector nodes and on default selectors.
• Fixed a bug that prevented you from automating certain web pages rendered in Edge/IE mode, when the URL contains space characters %20.
• Fixed a bug that prevented you from capturing onscreen values from a Java application.
• Fixed a bug for Internet Explorer mode on Edge that caused the selector validation to fail.
• Fixed a bug that was throwing a SelectorNotFound exception in the Maestro Java application when the structure of the page is very heavy with UI elements.
• Data Scraping did not generate an Extract Structured Data activity when working with certain applications.
• Fixed an issue which caused the Type Into activity to be unable to type the letter E on certain web pages.
• Fixed an issue which caused Studio to freeze when indicating an anchor in certain apps.
• Detection did not work on Microsoft Edge and Google Chrome opened in App Mode.
• Trying to interact with certain Excel files caused Citrix Remote Runtime to crash.
• Using a Click OCR Text activity with an invalid ApiKey caused a timeout error.
• When taking multiple screenshots with the Take Screenshot activity, the naming convention was used starting with the second screenshot.
• The runtime browser switcher failed to work as expectedon browsers via an RDP connection when using certain activities.
• When using Computer Vision activities, after editing a Descriptor, the change was not reflected neither in the informative screenshot or the Selection Screen.
• When using CV Screen Scope, indicating the full window for some Windows Native apps was very difficult because CV was using Element as Selection Type.
• Fixed an issue which caused the CV Extract Table activity to stop working when the maximum height limit was surpassed when extracting scrollable tables.
• Fixed an issue which caused certain Salesforce attributes to be unavailable in Firefox and Chrome.
• When using Image activities in Chrome, if the same image existed both inside and outside the specified clipping area, the wrong image was sometimes used.

Known issues

• To indicate an individual cell or sheet name in Excel 2016, you need to manually set AA as the selection mode. In v19.5.0, the default visual selection used AA. Starting with v21.10.4, the default visual selection uses UIA.
• When automating Chrome with the latest Extension for Chrome, the Modern Click activity used with the Simulate input method fails on specific form elements. As a workaround, you can use the Hardware Events or Chromium API input methods.
• Some selectors generated at design time with UI Automation v20.10 for SAP Fiori and the newest Chrome Extension can have some extra attributes which cause them to stop working when run with older versions of the Chrome Extension at runtime. As a workaround, the newest Chrome Extension should also be used at runtime, or the Selectors should be generated with at least UI Automation v21.10 at design time.
• Events are not detected when monitoring selectors from SAP NetWeaver Business Client to SAP Fiori, both locally and over Remote Desktop connections, or selectors from SAP NetWeaver Business Client to SAP GUI over Remote Desktop connections.

v21.10.5

Release date: 12 January 2022

Improvements

The UiPath Extension for Remote Desktop Protocol can now also be used with Azure Virtual Desktop client.

Bug fixes

• The Suppress Audit Logs Project Setting has been renamed to Log audit information and is set by default to True. Also, all logs generated by this setting are now at Verbose level.
• Fixed a bug for Oracle Forms that caused, in particular cases, the validation of selectors to fail.
• Fixed a bug that prevented you from reading the correct state of a checkbox inside a table in Java applications.

v21.10.4

Release date: 26 November 2021

Bug fixes

• When Background Mode was used with an Use Application/Browser activity that had the Resize window property set to Minimize, applications were not correctly minimized.
• To clear the text from web pages elements, you can use again empty strings with the Set Text activity, just like in UI Automation v18.4.

v20.10.11

Release date: 25 November 2021

Bug fixes

• To clear the text from web pages elements, you can use again empty strings with the Set Text activity, just like in UI Automation v18.4.

v21.10.3

Release date: 25 October 2021

Improvements

The Get Attribute activity has been reworked and now comes as part of the Modern design experience. Changes have also been made to improve the usability of the activity, making it offer a better experience overall.

The Get Text activity now features a wizard that enables you to preview the results of the text extraction, as well as configure the extraction method.

Two new activities, Get Browser Data and Set Browser Data, have been created to make it easier to migrate browser data from a session to another.

Adding or editing variables is now easier than ever! With the enhanced Selection Screen variable support this release brings, you can easily edit your selectors by using variables and arguments, and then choose to propagate the change throughout all instances of the said variable from that descriptor.

You can now refresh the Image selection when indicating in an application, by using the new button added in the Selection Screen.

All of the variable features added to the Selection Screen are now also available when editing selectors in the Selector Editor.

The Resize window property in the Use Application/Browser activity now has the option to minimize the window.

Support for Responsive websites has been added with this update. The Selection Screen now features a check box that enables working with elements that reflow when the browser window is resized.

The Open Application/Browser activity can now open applications in remote environments, making automation with the Modern experience in such environments much easier.

The Modern UI from the Selection Screen is now part of the Classic Experience as well.

Starting with this update, every time you start the Recorder, it starts recording automatically, and you no longer have to indicate the window first, thus making your automation life easier.

Applications provisioned through Microsoft RemoteApp can now be automated with the UI Automation activities.

As Internet Explorer 11 is approaching its upcoming end-of-life, we have developed a migration tool that enables you to convert all of the selectors and properties for your workflows seamlessly into ones fit for modern browsers, such as Edge, Chrome, or Firefox, ensuring you do not lose all of your automations based on this soon-to-be legacy browser.

The Type Into activity can now automatically detect the correct Input Mode based on what results each input mode returns for the application you are automating.

The Verify Execution feature in the Type Into, Click, and Hover activities can now check not only if the target element appeared or disappeared, but also if its text has been modified or if its visual appearance has been modified (status icons changing, etc.), via two new options in the Verify Element dropdown.

A new option has been implemented for the Input Mode property, called Chromium API, which is tailored for use with all Chromium-based browsers, being faster and more reliable than the others.

The App/Web Recorder now supports using the Object Repository when recording, enabling you to use already existing objects or create new ones on the fly.

The new Highlight feature in Object Repository enables you to highlight any object you have captured in the screen where you are capturing, making it easier to identify which element you are working with.

Auto-anchors are now suggested for all check boxes that implement the label-for attribute, regardless of the position of their label.

When validating results in the Selection Screen, multiple selectors are now searched for simultaneously.

The Extract Table Data activity now extracts all attributes when used on standard table extraction. Also, when automatically extracting URLs, the full URLs are now retrieved.

Adding another human ability to our robot workforce, we have developed a new activity, Mouse Scroll, which enables you to either scroll through pages for a fixed number of lines, or to a specified UI element, in applications you are automating.

The Edge Extension now supports Java Applets and ActiveX controls in IE Mode.

The Display Name property of the Use Application/Browser activity now automatically changes according to the indicated target, so you can easily spot which card points to which application at design time. In the situation when you are using nested application cards, you can now choose from a drop-down in the body of every activity the application card you want to reference when indicating on screen.

When recording Type Into with the Modern Experience, a drop-down for Special Keys is now displayed when entering the text you want to type.

When scraping tables with the Extract Table Data activity, the Extract Table Data Wizard now retains previous changes when reopened.

The Attach Browser and Attach Window activities now enable you to set both the Selector and Browser or Window properties at design time without throwing an error. At design time, the Selector property is used, while, at runtime, the Browser or Window properties are used.

Organizations can now use Robot governance policies deployed from Automation Ops to control what applications and URLs can be automated at runtime. The new Robot policy available in Automation Ops starting with Robot v2021.10 includes the App/Url Restrictions Runtime Analyzer rule that enables you to define the applications and URLs that are either allowed or prohibited for UI automation activities. The rule supports the use of * and ? expressions for defining patterns for URLs and application file names to allow or block.

Salesforce Lightning, with specific Salesforce AURA components path and attributes, and reliable selectors, is now supported in Chrome and Edge.

This activity package now supports .NET 5 Windows and Cross-platform projects. For more information, see About Automation Projects. Also, the following OCR engines now support .NET5: Google Cloud Vision OCR, Microsoft Azure Computer Vision OCR, Tesseract OCR.

Microsoft OCR, however, does not support .NET5; when using the UiPath.UIAutomation.Activities package in a .NET5 project, Microsoft OCR is not displayed.

The Mouse Scroll and Keyboard Shortcuts activities have been visually updated, sharing the same UI as the other Modern activities.

The Object Repository now uses Computer Vision technology for the Capture all elements feature, which can extract all the elements of a specified application and add them to your Object Repository. This can greatly reduce the time needed to build the Object Repository libraries, as you no longer have to manually add each element one by one. You can also open any element in the Capture Elements wizard directly in UIExplorer via a dedicated button.

The Use Application/Browser activity now has a new Input Mode, called Background, which enables you to use all its children activities in the background whenever possible.

You can now open the application or browser targeted by the Use Application/Browser activity by using the new button in the body of the activity.

The UI-SEC-010 and UX-SEC-010 Workflow Analyzer rules now also apply to remote target applications. Also, both rules now allow using wildcards in creating rules.

The App/Web Recorder now has an input method called Auto, which automatically selects the best input method available, making it easier to automate different kinds of apps.

UI elements from CefSharp embedded widgets (e.g. SharpBrowser, SAP NWBC with Fiori Launchpad) are now recognized as belonging to the host application instance.

The Open Browser activity has a new check box, AutomaticallyDownloadWebDriver, which, when selected, automatically downloads the required WebDriver executable on your machine in the %localappdata%\UiPath\WebdriverExe folder.

Starting with UiPath.Excel.Activities version 2.11.3 and UiPath.Presentations.Activities version 1.2.3, you can add UI Automation activities inside a Use Excel File or Use PowerPoint File activity to quickly automate the interface of Excel and PowerPoint.

The Check App State activity has been taken up a notch, and can now monitor the entire application screen for changes, not just a single UI element.

The RDP Extension can now be installed per system, removing the previous limitation, where it required per-user installation.

The new Text Changed option in the Verify element property drop-down menu enables you to verify any changed text in the targets of activities that support this, such as Click, Hover, and Type Into.

The Verify Execution property has been added to the Keyboard Shortcuts activity, expanding this feature to the scenario where you want to verify the way keyboard shortcuts are sent by your automation process.

The CV Activities now support table cell identification, enabling you to automate table cells a lot easier, based on either row and column content or indexes.

Project Settings

The new Runtime Browser project setting enables you to use a different browser at runtime than the one used at design time. This is done automatically, as all related properties and selectors are seamlessly adapted to the browser of your choice.

The Desktop Project Settings Targeting Methods (AA, UIA, Win32) have been merged into a single setting, called Targeting Methods – Desktop.

Multiple new project settings or the UI Automation package have been added or updated, to fit your automation needs, as follows:

A new Capture Screenshots setting that specifies whether activities save screenshots of their targets at design time. This setting is present in both Modern and Classic experiences.

A new Robot Logging section, with the Run value and Debug value settings that specify whether the Robot should log extra values.

The Targeting Methods Project Settings have now been split according to the type of the target application. Now you can configure separate settings for Web, Java, SAP, and Desktop applications.

The Verify Execution project setting has a new option which enables you to always perform verifications for Click, Hover, and Type Into activities in a project.

Also, the Input Mode project setting has been split into two separate project settings, Input mode for Edge browser and Input mode for Chrome, Firefox, IE, Edge in IE mode, to make sure the correct input method is selected when using Edge Chromium.

A new Project Setting, Show closest matches in the Element Not Found error message enables you to log either a detailed or a trimmed down version of the error message that is displayed when an UI element is not found.

SAP

The new SAP Session Attributes Change Trigger activity enables you to create triggers by monitoring changes in SAP session attributes.

Support has been added for Chromium for SAP Business Client. This allows users to use the same features and SAP Fiori capabilities available as when automating with UiPath Studio and Google Chrome.

Support has been extended for SAP ALV Tables with Multiheader. You can now extract data from tables which have their headers split into two or more lines.

The new Expand ALV Tree activity enables you to expand the parent ALV tree to the selected node and use any activities with the resulting elements, making SAP ALV Tree lists a lot easier to automate.

SAP Fiori UI5 attributes are now fully visible and usable with the Modern UI Automation experience.

Three new attributes, ColorIndex, ColorIntensified, and ColorInverse have been introduced for SAP ALV Tables, enabling you to identify the background color of elements, giving you extra methods of identifying the elements you want to work with.

Full text scraping is now supported in SAP ALV Tables, which means that you can now also scrape the text that is not visible.

When using the Extract Table Data activity to extract data from SAP ALV Tables, you can now distinguish between the column display name and the column tooltip, to make it easier to correctly identify your target.

Selectors have been improved for SAP ALV Tables, adding support for tooltip and text attributes.

Breaking changes

• The aastate attributes of <uia/> selectors were incorrectly retrieving the aastate value of the ancestor. The attribute’s value is now correctly retrieved, which may cause breaking changes in older workflows. This does not impact the Universal Windows Platform applications selectors which were built correctly.
• The Key Press Trigger activity was erroneously detecting some events when the IncludeChildren property is set to False. This may cause breaking changes in older workflows.
• In certain conditions, such as using a maximized Chrome window, the Click activity with the Click offset Anchoring Point property set to BottomRight triggered an extra scroll event. This behaviour is now fixed, and may cause breaking changes in older workflows.

Bug fixes

• Performance issues were present when working with certain Java applications.
• Fixed an issue which caused an error to be thrown when extracting data from certain types of webpages (ShadowRoot).
• Fixed an issue which caused UIExplorer to throw an error when using AA for targeting elements in Firefox. When using a new or empty Firefox tab with UI Framework set to Default does not allow selection of individual UI elements. Also, any Firefox tab permits selection of the entire window only when using the AA Framework.
• When Object Repository was enforced in a project, it could still be disabled from the Recorder.
• Fixed a bug that occurred when OCR was run on different OS region formats. Now, the OCR runs as expected and all results are generated correctly, no matter what OS region format is used.
• When using certain versions of dependencies, screenshots of Excel could not be taken.
• The Input Mode property of the Extract Data Table activity was not affected by any changes in the Targeting Method Project Setting.
• Trying to install Java Bridge from UiExplorer when using UI Automation v21.4.x failed.
• Fixed an issue which caused the Wait for page load property to not work properly on browser tabs that were loading.
• Trying to click a certain cell containing a date in a table by using Computer Vision activities failed in the case of certain tables.
• In certain cases, strings were merged between separate cells when extracting values from a table using Computer Vision activities.
• Automating PDFs opened in Firefox failed to extract individual UI elements.
• Fixed an issue that caused title HTML attributes to be mistakenly identified in certain types of tables. Added a new attribute, uipath-html-title, which has the value of the title attribute of the DOM node.
• Fixed an issue which caused Type Into to behave differently when the design-time keyboard layout was different than the one used at runtime.
• The Enter keystroke was not performed correctly in some activities when running as a XenApp in an App-V container.
• Fixed an issue which caused certain activities to perform very slowly when retrieving values when used with newer versions of UI Automation.
• Default selectors in Edge pop-up windows were generated incorrectly.
• Sending the Enter keystroke by using SendWindowMessages to buttons failed.
• UiPathRemote.exe sometimes crashed in Citrix environments.
• In certain situations, the Click Text activity caused applications to crash.
• Fixed an issue which caused the Recorder to throw an internal error when deleting a keyboard shortcut from the recorded steps.
• Fixed an issue which caused elements inside an iFrame to not be detected in Edge and Chrome.
• Fixed an issue which caused interactive selection with Smart-Sizing and using different resolution scaling to not work properly when automating in RDP.
• Fixed an issue which caused the Attach Browser activity to throw an error when it was configured to use both the Browser and Selector properties.
• Using the Type Into activity with the SimulateType or SendWindowMessages properties when automating a Command Prompt window failed to type the correct text.

Known issues

• The Silverlight extension might not work on Windows 10 x64 systems where the Windows update 10.0.19043 was applied.
• If you want to use any OCR Engine in Studio v19.10 with UI Automation activities, please install the UiPath.CoreIPC package, version 2.0.1 or higher.
• In a C# process, editing a descriptor does not display changes at design time when using the CV activities.
• When using UI Automation v21.10 with Studio v2019.10, the UX-SEC-010 and UX-DBP-029 Workflow Analyzer rules are not available.
• When using Firefox, Salesforce-specific sfl attributes are not displayed in selectors and selector nodes.
• On certain applications that use Windows Forms, when using only the Fuzzy selector method for targeting elements in a minimized app, the target cannot be found.
• Using Background input mode with apps that use Universal Windows Platform causes the apps to be brought to the foreground.
• When using the Modern experience with SharpBrowser, selectors are not correctly generated, lacking webctrl tags.

Accessibility

• Indicating an application requires the use of a mouse, and cannot be executed by using the keyboard.
• Variable right click functionality requires the use of a mouse and cannot be performed only by using the keyboard.

v21.4.4

Release date: 2 June 2021

Bug fixes

• Java Bridge could not be installed from UiExplorer.
• Fixed performance issues with the Get Attribute, Get Position, Get Text, Text Exists, OCR Text Exists activities.
• When using the Call Transaction and SAP Login activities running XenApp in an App-V container, the Enter key was not performed.
• SAPGUI scripting did not work for automating SAP Logon applications published as App-V.

v20.10.10

Release date: 2 June 2021

Bug fixes

• Java Bridge could not be installed from UiExplorer.
• The On Image Appear activity displayed a corrupted screenshot when indicating the target for the first time.
• Fixed performance issues with the Get Attribute, Get Position, Get Text, Text Exists, OCR Text Exists activities.
• Fixed an issue that caused certain webpages in Chrome to freeze the entire OS when indicating with an Use Application/Browser activity.
• When using the Call Transaction and SAP Login activities running XenApp in an App-V container, the Enter key was not performed.
• SAPGUI scripting did not work for automating SAP Logon applications published as App-V.
• The Click activity stopped working when a window froze in the foreground during runtime.
• After indicating an element or an Anchor, UiExplorer was unable to return to the foreground.
• When using the Indicate Element and Repair features, multiple Selector Editor windows were opened.

v19.11.5

Release date: 24 May 2021

Bug fixes

• Using the Click Image activity in a loop threw an exception.

v18.4.8

Release date: 28 April 2021

Bug fixes

• When using UI Automation v18.4.x with Studio 2021.4, working with the Indicate Element and Repair features caused multiple Selector Editor windows to be opened.
• When using UI Automation v18.4.x with Studio 2021.4, after using Indicate Element or Indicate Anchor, UIExplorer would remain minimized and could not be brought to the foreground.
• In projects created with Studio v2018.4.2 and UI Automation v18.4.2, activities that made use of selectors when working with Internet Explorer might have not worked correctly after upgrading the Robot to v2020.10.4.
• The Click Image activity did not use the values specified in the Timeout and WaitForReady property fields.
• The Attach Browser activity did not switch focus to a tab when the webpage in that tab was a frameset.

v21.4.3

Release date: 26 April 2021

Improvements

UI Automation Modern

The Extract Table Data activity has been revamped, containing several new properties, as well as a new wizard that helps guide you through the data extraction process. This whole feature can also be used from the new Table Extraction recorder, which appears in the Ribbon if you have selected the Modern Experience. Structured data has never been easier to extract, thanks to the multitude of new features that this release brings!

The new Verify Execution feature allows you to ensure that the action (a Click or Type, for example) was correctly executed at runtime – that it had the expected outcome. This feature can be configured from the following activities and from Project Settings:

• Click
• Type Into
• Hover

The Use Application/Browser activity has a new property field, Incognito/private window, which enables you to open the browser session in incognito or private mode.

The new multi-selector search is now used for all searches, both at run time and design time. This works under the hood, so it won’t impact your experience with the product, but simply yield better results overall.

You can now define an area you want to automate by dragging when using the App/Web Recorder feature, thus enabling you to use Image automation in your workflows.

Check:text was a hidden feature of the Fuzzy Selector, that enabled you to easily target elements that contained text. In a way, it is similar to the older Click Text activity. Now, upgraded to be a part of the Modern experience, this feature can be found under the Fuzzy Selector, in the Selection Screen, and by using it you can now select how you want text to be processed from while Indicating your target, with support for wildcards, variables, and the whole shabang.

To increase usability and customizability, certain settings, such as the timer set for Pause (F2) when indicating an element on screen, now persist per machine, across sessions.

You can now indicate dynamic targets, which are no longer dependent on their text labels. This enables you to work with elements that have dynamic text labels, or with specific elements in search lists, in regard to their position in the search rather than their text labels. This is done by harnessing the power of the Fuzzy Selector, which can now also use wildcards for extra fuzziness.

The new Get URL activity enables you to retrieve the URL of a web page and reuse it in your automation, thus making web automation much easier.

Targets that are no longer available, such as apps that are closed, can now be edited in Offline Mode, so you don’t need to pass through the entire process of bringing up the same window again to edit a single character in your selector. Yay!

The Check App State activity can now also be used outside the Use Application/Browser activity for situations such as connecting to a VPN, or starting a Virtual Machine.

The App/Web Recorder can now be used with any app on you machine, without the need for switching between apps. We have adapted the recorder to your needs, and it can now automatically determine the fact that you are indicating actions in a different app and behave accordingly, automatically recording your steps.

To make your automation life easier, indicating certain types of apps with the Use Application/Browser now autofills the Arguments property, making it easier to use Java apps, PDFs, Office apps, or Windows apps.

You can now use variables and arguments directly in the Selection Options screen when editing the Selector and Fuzzy Selector.

The Click and Hover activities now have the CursorMotionType property, which enables you to select the type of motion you want the mouse to use while performing the action, be it Instant or Smooth.

Wildcards are now supported in the Item field of the Select Item activity. Also, a new property field has been added to this activity, AlterIfDisabled, which performs the selection action even if the target element is disabled.

Due to the fact that some actions, such as Double-Click failed when performed with the Simulate method, they are now performed with the Hardware Events method by default, thus avoiding the situation when the workflow fails silently.

The Extract Structured Data activity now supports integration with the Object Repository.

The Enforce Element Visibility check box has been implemented in the Selection Options window, enabling users to work exclusively with visible UI elements.

The App/Web Recorder now supports using modifier keys when recording actions.

The Wait for ready property has been renamed to Wait for page load in all of the Modern UI Automation activities, better reflecting its purpose.

UI Automation Classic

The Start Process activity can now open files with all extension types, such as .doc, .xls, .png, .pdf, etc.

The Click and Hover activities now have the CursorMotionType property, which enables you to select the type of motion you want the mouse to use while performing the action, be it Instant or Smooth.

Wildcards are now supported in the Item field of the Select Item activity. Also, a new property field has been added to this activity, AlterIfDisabled, which performs the selection action even if the target element is disabled.

The Table Cell Scope activity has a new property field, Table Row Index, which displays the index of the found row, and is useful in cases of tables that have the first empty row.

Java Native Scraping now retrieves the bounds of words when the Get Words Info check box is selected.

The Attach Browser activity has a new option in the BrowserType property, suitable for other Chromium-based browsers.

Support has been added for websites that use Shadow DOM for their UI elements. These pages can now be automated using Google Chrome, Firefox, and Edge.

When using variables in selectors, changes made in the Variables Panel now also take effect in the selectors. Please note that this does only apply to variables that are modified after upgrading to this version of the UI Automation package, so this does not cause a breaking change in older workflows.

The Key drop-down in the body of the Send Hotkey activity now supports auto-searching hotkeys in the list when it is expanded.

SAP Automation

UiPath Studio supports now the latest version of SAP WinGUI 7.70 with all new features such as a new visual theme, Quartz, support for alternative browser control (Microsoft Edge), as well as multi-monitor scaling support.

Data scraping and Screen scraping are supported for data extraction for SAP ALV Tables. One or multiple tables on the SAP screen can be extracted.

The Table Cell Scope activity can be now used for SAP FIORI table automation.

Computer Vision

The CV Click, CV Hover, and CV Check activities now have the CursorMotionType property, which enables you to select the type of motion you want the mouse to use while performing the action, be it Instant or Smooth.

The Computer Vision activities now support using only OCR, if you configure them as such, ensuring an overall better user experience.

A better Change Detection mechanism has been implemented in the Computer Vision activities, minimizing the number of full CV analyses required and optimizing the process.

The CV Get Text activity now displays a text result preview in the designer, displaying the text that is going to be extracted.

UI Explorer

UiExplorer has a new feature that delays restoring the UiExplorer window until after the selector data is loaded. This is meant to be used with UI elements that auto-close on losing focus.

Breaking changes

• The Expected Text subfield of the Verify execution property field’s functionality has been modified and is no longer compatible with automation projects built with UI Automation v21.2.0-preview, causing a breaking change.
• The Timeout property in the Element Exists activity can now be configured from the Project Settings in Studio.
• Using Click with Simulate Click on a Java application that does not support that capability did not work, but no error was thrown and the workflow continued execution. The same scenario now throws an error and may cause breaking changes in workflows that used it.
• In a Java application, using the Click activity with Hardware Events on UI elements from a tab different than the one in focus now throws the correct exception. Please note that this may break old workflows.
• Deprecated the Microsoft Project Oxford Online OCR engine. The following exception is thrown at runtime: Microsoft Project Oxford has been completely retired. Please switch to a different OCR engine.

End of Support for Microsoft Edge Legacy

• Starting with v21.10, the UI Automation activities package will no longer support the Microsoft Edge Legacy browser, so the extension for Microsoft Edge Legacy will no longer work.

Bug fixes

• When the URL property field in the Use Application/Browser contained a string variable with an URL, clicking the button in the body of the activity that opened a new browser session with the specified settings did nothing.
• The Select Item activity did not work with combo and list boxes in Java applications.
• Fixed an issue which caused exceptions to be handled improperly when using Parallel activities.
• The type initializer for Emgu.CV.CvInvoke threw an exception when using Image or Computer Vision activities.
• The Text Exists activity always returned True when used inside a Parallel activity and the Parallel property was selected.
• UiExplorer failed to load selectors in certain situations on Internet Explorer. The implementation of the window restore delay feature in UIExplorer has helped avert this issue.
• Screen Scraping an image through a While loop failed in certain situations.
• Fixed an issue which caused the Executor to crash when working with a Java Application.
• The Block User Input activity was unblocked when using only the Alt key.
• An exception was thrown when using a library containing the Set To Clipboard activity that set an empty string.
• When using the Selector Editor, removing ”app=” from a selector did not invalidate it.
• When Data Scraping on certain data tables, the preview window did not display Col. A.
• Indicating a PDF in Internet Explorer with a Use Application/Browser activity caused a freeze.
• The Hide Window activity is now hidden from StudioX.
• Chrome popups were not detected when using Remote Desktop Protocol connections.
• Certain webpages in Chrome froze the system when indicating with an Use Application/Browser activity.
• Indicating a Chrome or Internet Explorer page with a Use Application/Browser activity in poor network conditions caused a freeze.
• When using Type Into with Hardware Events, letters were duplicated in the typed text on a specific web page.
• When using Click with the Simulate method on elements from Java applications, the action was reported as succeeded, even if the action was not supported by the target element. Now, attempting to click with the Simulate method on an element that does not support the action (such as panels), a more descriptive errors displayed.
• Fixed an issue that caused UI Automation to be unable to detect Citrix Apps when used in 64-bit mode.
• Enter key did not confirm selection when used to map elements in Object Repository with Configure Each Element on.
• In certain situations, when using the Use Application/Browser activity with the Minimize activity would automatically restore the minimized window when performing actions on it.
• When using Check App State on an invalid UI element, the returned element was not null.
• When using the Take Screenshot activity with the Object Repository, the FileName was empty.
• Fixed an issue that caused the Use Application/Browser activity to have the Attach mode property set to Process Name instead of Application Instance when created from the Object Repository.
• Fixed an issue which caused the NewSession property in the Open Browser activity to behave incorrectly.
• The Edge extension could not be installed via policy for offline users that were not connected to Active Directory, and the policy was blocked, causing the SetupExtensions tool to erroneously inform the user that the extension was successfully installed.
• The Help button in the Preview Data section of the Data Scraping wizard did not lead to the correctly localized page.
• Using UI Automation Next activities with apps or browsers that had overlays behaved incorrectly.
• The Callout activity did not correctly consider the DPI of the machine it was running on.
• When editing the Target.Clipping Region property in the Properties Panel in any of the activities that use it, changes were not saved.
• Indicating the Address bar and certain toolbar elements UI elements in Chrome or Firefox did not work as intended.
• When running an automation process in a loop, the Open Browser activity threw an exception.
• The aaname html attribute retrieved the text from all the children of an indicated node. Now, only the text from the indicated note is retrieved. This rule does not apply for the following HTML node types: input, img, button, textarea, area, a, select, table. The Get Text activity still retrieves the text content of the entire subtree of the indicated node, which is the recommended way to capture the value of an element.
• Anchors can now be indicated from the Selection Screen when working with UI elements in Image Selection mode.
• When automating Java applications, the state of check boxes could not be recognized.
• Fixed an issue which caused drop-down menus to be untargetable in certain webpages.
• Fixed an issue which caused the Selection Options window to have long delay times when indicating certain elements in Edge and Internet Explorer.
• The Find Children activity no longer throws a SelectorNotFoundException error when used with a valid selector but with a filter condition that causes all the elements to be filtered, and instead returns an empty list in such cases.
• Fixed an issue that caused the Attach Browser and Attach Window activities to display selectors that used variables incorrectly.
• Fixed an issue which caused the Chrome extension to not work properly after upgrading from Studio v2020.10 to Studio v2021.4 under the same user, if installed from the Tools section in Studio without elevated rights.
• Fixed an issue which caused the Chorme extension to not work properly after upgrading from Studio v2020.10 to Studio v2021.4, if installed from the Tools section in Studio with elevated rights.
• The Element Exists activity threw an error when used with Internet Explorer, with an UI Automation version newer than v19.4.2.

Known issues

• The Firefox, RDP, Citrix and VMWare extensions installed via the Tools section in Studio with Studio 20.10 do not work any longer when upgrading visually to Studio 2021.4, for the same user that initially made the installation.
• The Firefox, Chrome, Edge, Citrix, RDP, and VMWare extensions installed via the Tools section in Studio with Studio 2020.10 do not work any longer when upgrading silently to Studio 2021.4, or when using a different user than the one who initially installed Studio.

v18.4.2.1

Release date: 14 April 2021

Bug fixes

• In projects created with Studio v2018.4.2 and UI Automation v18.4.2, activities that made use of selectors when working with Internet Explorer might have not worked correctly after upgrading the Robot to v2020.10.4.

v20.10.9

Release date: 8 February 2021

Bug fixes

• Fixed an issue which caused the Selection Screen Helper to remain visible on Windows 7 machines after indicating an UI element.
• The Use Application/Browser activity was unable to target Adobe Acrobat even though it was open.

v20.10.8

Release date: 14 December 2020

Bug fixes

• When automating an app that had multiple window instances, inside a Use Application/Browser container with Attach Mode set to Application Instance, manually modifying the selector of a Click activity to an inexistent one caused the entire target application to be targeted instead of the initial element. This happened only when the Selector check box was selected.

v20.10.7

Release date: 10 December 2020

Improvements

The Double Click action has been added to the Action Picker menu in the Recorder.

The window selector is now shown when editing a descriptor in offline mode.

Bug fixes

• The Extract Table Data activity can now be used with the Object Repository feature in Studio.
• Fixed an issue that caused wrong files to be invoked by the Invoke Process activity.
• JavaState attribute matching was not correctly performed.
• Fixed an issue that caused Type Into with SimulateType to fail when used with Lawson in Chrome.
• The Click Image activity did not use the values that were set in the Timeout and WaitForReady property fields.
• A Null Pointer exception was triggered when retrieving text from an NRichLabel in Nexaweb environments.

Known issues

• Installing the UiPath extensions for Chrome and Edge Chromium using UiPathStudio.msi fails if either of the browsers is running during the installation. You are now prompted to close your browser before installing them.

v20.10.6

Release date: 20 October 2020

Bug fixes

• The Table Cell Scope activity was displayed when Modern experience was selected in both Studio and StudioX, even though it was not compatible with them.

v20.10.5

Release date: 12 October 2020

Improvements

Unifying UI Automation and UI Automation Next

The UI Automation and UI Automation Next activity packages have been unified under the UI Automation v20.10.5 activity package, containing the best of both worlds, now taking advantage of the new Unified Target technology, which brings all of the targeting methods together, making all your automation endeavors much easier.

Also, some activities have been reworked to support the Unified Target technology. Don't worry, though, we haven't removed their old counterparts from the package, you can simply opt whether to use them or not by selecting the Classic Modern experience from the Design tab in Studio Backstage Settings.

Choosing the Modern experience also grants you access to the new App/Web Recorder, which is a single recorder to rule them all, replacing all previous UI Automation recorders with a new, anchor-based, multi-technology element identification system that makes recording your actions considerably easier and faster.

You can install the unified UI Automation activity package even on Studio v2020.4.1 or lower. Doing this displays all the classic and modern activities in the Activities pane. Please note, however, that wizards that require newer Studio/Robot versions than 2020.4.1 are not available in older versions.

Note: Improvements performed on the UI Automation Next package between v20.4.3 and v20.10.5 are listed in their own subchapter below, for increased clarity.

Desktop Triggers

Trigger Scope Activity

We have developed a completely new scope activity for triggers, called Trigger Scope. This activity can be found in the System activity package v20.10.1 but is usable with all the triggers present in both UI Automation and System activity packages. It offers the required arguments to work with the trigger out of the box, like trigger name and type or its source event. Moreover, it can treat the incoming events sequentially or concurrently while it can exit after one execution.

New Triggers and UI Redesign

In this regard, we have added several new trigger activities, and redesigned some of the existing triggers, moving the most used properties at hand. The new activities are:

• Element Attribute Change Trigger
• Element State Change Trigger

Triggers SDK

Most importantly, we have democratized trigger development. We provide a trigger SDK for everyone to use and develop custom triggers, just like you do with custom activities. You can read more about this here.

Workflow Analyzer Rules

Two new Workflow Analyzer rules have been added, as follows:

• Forbidden Variables Usage In Selectors enables you to scan for all UI Automation activities that use variables in selectors, thus removing any risks of using non-compliant selectors in your automation processes.
• Insecure Password Use checks if any Type Into activities used in your workflow use plain text to type passwords instead of SecureString variables.

Computer Vision

This release brings an update to the user experience offered by the CV activities by modifying the way screens you are working with are cached. The new cache strategy saves all of the screens you are working on within the CV Screen Scope activity and allows you to perform actions on them at design time in an easier fashion.

UI Automation Next

Take Screenshot - This new activity enables you to take a screenshot of a specified UI element and save it as an image file.

You can now place Use Application/Browser activities one inside another. This gives you more flexibility when designing automations that work with multiple applications.

A new option named Configure every step is available in the App/Web Recorder. When it is enabled, the following changes occur before a step is recorded:

• Target selection is no longer made automatically after you click the UI element to interact with. You can add or remove anchors, remove and add the target again after indicating it, and confirm the selection.
• When adding the Get Text action, you are prompted to save the value.

The App/Web Recorder now remembers the last position where you moved it on the screen. When you close it and launch it again, the Recorder opens in the same position where you last left it.

New activities

The new Modify Text activity updates a specified text by using methods such as find and replace, trim, or concatenation, offering you multiple new ways to manipulate any text files you might need to.

The new Table Cell Scope activity enables you to attach to an existing Table UI element and perform multiple actions within it. This activity is specifically tailored for SAP WinGUI automation.

The new CV Extract Table activity enables you to retrieve any visible table by using Computer Vision and storing it into a DataTable variable for further use.

To increase support in dealing with troublesome UIs of WPF and WInForms Windows applications, we have created the new Inject .NET Code activity, which enables you to inject .NET code in any target application.

Other improvements

Improved the message displayed for the Type Into activity if the EmptyField field is not filled in.

We’re extending the capabilities for creating automation projects for SAP. As such, this release, will make it possible and easy to automate SAP FIORI by building selectors out-of-the-box.

The CV Get Text activity now also has the RefreshBefore check box, which, when selected, enables you to scan again using the Computer Vision neural network for any changes since the first CV Screen Scope scan.

We have now added support for User Events monitoring for Citrix desktops and apps, as well as automations over RDP.

The GetProcessNameByPid and GetWindowProcessName attributes now return a lowercase value instead of the raw process name, which had to be converted to lowercase.

The Google Cloud Vision OCR activity received a new option, named DetectionMode.

Improved the behavior of the Type Into activity when it was used on Outlook Web in Internet Explorer and Chrome. The ClickBeforeType property had to be set to true for all input methods, while the <idx> attribute with a large value was unreliable.

The default value for the SAP Logon activity is now retrieved from the corresponding registry entry.

Selectors generated for SAP table columns now return the column name as the default value instead of the column number. As such, the selector is now generated with the <colTooltip> attribute to indicate the column name.

It’s now possible for the Click activity to interact with JSpinner arrow elements in Java applications.

Selectors for Java applications now support the <cls> attribute.

Breaking changes

• A fix for the Take Screenshot activity causes all exceptions in the activity to be handled differently. Before the fix, any exception simply caused the screenshot to be returned as null, but now, the exception is thrown normally, stopping workflow execution. This can cause breaking changes in already existing workflows.
• A fix for the Click before typing property in Java applications causes the cursor to be placed after the existing text instead of at the beginning of the existing text when a Type Into activity with Activate selected and Click before typing set to Single or Double is used in a Java application.
• On rare occasions, target and anchor pairs created in version 2020.4.x may fail to identify the correct element in this version. To fix this issue, select the anchor again or add another anchor for the target.

Bug fixes

• Fixed an issue with the Attach Window activity which did not properly function on Java applications when the process was started from Orchestrator. The issue occurred after a Windows update was performed. Please note that you are not prompted to install the extension for Java if the awt.dll file is not loaded in the target Java application. This is done to prevent the installation pop-up from showing up when applications cannot be automated through Java selectors. You can read more about the extension for Java on this page.
• Improved the selector generation for the Microsoft Teams application by fixing the <cls> tag which was incorrectly generated.
• The Key press trigger activity would fail to detect an element if its selector contained the <idx> attribute.
• In some cases, a dropdown or context menu would disappear right before the Click or Hover activities could interact with them. This has now been fixed.
• The Key press trigger activity did not function correctly when used on SAP WinGUI elements.
• We fixed an issue in the App/Web Recorder that sometimes made the Choose action hover menu difficult to click.
• When Acrobat Reader DC is the target application for a Use Application/Browser activity which has the Open property set to Always, an error no longer occurs if Acrobat is already open. The activity now attaches to the existing Acrobat window. For example, if a PDF file path is provided as an argument, the file is opened in a new tab in the existing Acrobat Reader DC window.

Known issues

• The Object Repository does not currently support the Extract Table Data activity.
• Some C# expressions might not work when used with the OCR engine in a CV Screen Scope activity. A workaround for this issue is using an Assign activity before the CV Screen Scope activity to run the expression.
• The Invoke Workflow File activity is unable to open the correct file at runtime when a previous activity alters the target directory.
• When automating an app that has multiple window instances, inside an Use Application/Browser container with Attach Mode set to Application Instance, manually modifying the selector of a Click activity to an inexistent one causes the entire target application to be targeted instead of the initial element. This happens only when the Selector check box is selected.

v20.4.3

Release date: 24 August 2020

Bug fixes

• Fixed an issue that caused Java selectors to not be generated after installing the UI Automation v20.4.2 package.
• On some occasions, the Select Item activity would not interact with its target element.
• After upgrading to Firefox 79, the Indicate on screen function would not detect elements inside iFrames.

Known issues

• The Open Browser activity throws an error after installing the KB4525237 update for Windows 10 1803. The issue does not occur after you install the KB4561621 update.

v20.4.2

Release date: 26 June 2020

Improvements

Improvements were made to UIExplorer to considerably reduce the load time of panels and values when complex selectors were generated for particular applications and web pages.

v19.11.4

Release date: 29 October 2020

Bug fixes

• Indicate on Screen did not work when indicating inside an iFrame on Firefox 79.0.
• The Robot crashed at runtime when using a Monitor Events activity with no value in the RepeatForever property.

v19.11.3

Release date: 10 June 2020

Improvements

It is now possible to create automations for the New Edge Browser (Chromium-based), by installing the corresponding extension. This can be done either at install time, when installing Studio from the UiPathStudio.msi file or later, after installation, from Studio > Tools > UiPath Extensions > Edge option.

The number of RemoteRuntime calls has been reduced, resulting in faster response time and better performance.

Improvements were made to make it possible to properly identify UI elements inside the Adobe Acrobat DC 19 application, without having to open a PDF document first. Previously, a PDF document had to be opened before being able to properly identify UI elements.

This patch upgrades the Cloud OCR engines in the UI Automation package to support TLS v1.2, as the older v1.0 and v1.1 have reached end-of-life.

Bug fixes

• Fixed an issue that caused Studio to stop responding during element selection when the UiPath.UiAutomation.Activities v19.10.1 or newer was used.
• Fixed the behavior of the Click Trigger activity which used to return the true value when the Click actions was performed on an unresponsive Internet Explorer window.

Known issues

• Automations for the New Edge Browser with the WebDriver protocol are not supported in this release. Upgrade to the UI Automation package v20.4.1 or newer to use the New Edge Browser with the WebDriver protocol.

v18.4.7

Release date: 2 June 2020

Improvements

This patch upgrades the Cloud OCR engines in the UI Automation package to support TLS v1.2, as the older v1.0 and v1.1 have reached end-of-life.

v20.4.1

Release date: 6 May 2020

Improvements

The newly developed Invoke ActiveX Method activity enables you to invoke ActiveX methods in your workflows as well as interact with ActiveX controls where no selectors can be found.

The new Export UI Tree activity detects and exports all UI elements and their attributes and values from an indicated element, enabling you to fully understand what may cause a selector to fail at execution. For this release, this activity is flagged as experimental, as it is still a work in progress.

The Use Foreground scope activity enables you to run a specified set of activities in the foreground.

Activities which use the SimulateType or SimulateClick properties now benefit from the AlterIfDisabled property. If set to false, corresponding activities do not interact with disabled UI elements.

The new CV Check and CV Dropdown Select activities have been added to the Computer Vision suite, offering you new tools to handle UI elements such as check boxes and drop-down lists.

The Computer Vision Server is now officially supported for Windows. You can deploy an on-prem Computer Vision server on any local Windows machine.

UI Automation's Workflow Analyzer Rules have received an addition, with a new rule enabling you to allow or deny specified URLs or applications from being used in your automations.

We have performed minor visual improvements to the activities icons so it is easier to differentiate between similar activities when browsing through the activities panel.

We have created a new set of activities delivered by the UI Automation activity package specially-tailored for SAP. They are as follows:

• Click Picture on Screen which allows you to perform click operations on pictures displayed on an SAP GUI screen.
• Click Toolbar Button which makes it possible to click a button from the system application or SAP toolbars.
• Read Statusbar which returns the message displayed in the SAP GUI window statusbar.
• Select Dates in Calendar which makes it easy to select particular dates or periods of time from an SAP calendar.
• Select Menu Item which allows you to select a menu item from the SAP GUI window.
• Expand Tree which expands a parent tree to an active node or an active item.
• Call Transaction which executes the provided transaction code or program.
• SAP Logon which makes it easy to bring up the SAP Logon.
• SAP Login which allows you to log into your SAP system.

We are constantly adding to the list of technologies for which you can create automation processes, and this time around we introduced support for WMware Horizon, making it possible to generate native selectors just as you would on your own machine. We know it is of help.

If you decided to upgrade to the New Microsoft Edge Browser, we now offer the means to install the UiPath extension for it, so you may continue building your web automations with this browser.

Since debugging is an important part of building a flawless automation process, we decided to make UI Explorer a standalone tool. This allows for a more convenient way to inspect elements and selectors without having to install Studio. The package also contains the SetupExtensions tool so that you can analyze elements across all your automation needs.

We’re providing our selectors with more methods of accurately identifying UI elements. Apart from Fuzzy and RegEx search, you can now identify elements with the Case-Sensitive selectors property. It works by looking at casing of the target element’s attribute value, and it also works along with RegEx search on the same attribute.

Fuzzy Search and RegEx now support the Java and SAP selector types.

Some changes were made to the interaction between activities and the Remote Runtime which results in faster response time and better performance.

The Extension for Chrome can be installed using Policy settings.

The isbrowsertabactive attribute has been added to selectors to indicate whether or not a browser window is active.

The ScreenScrapeJavaSupport tool now indicates if a wrong folder was used as a path argument.

Fuzzy Search now also works with <rdp> selector types.

Breaking changes

• Selectors generated for Java applications that contain multiple WND tags cannot be used with events monitoring.

Bug fixes

• Fixed an issue that generated an incorrect index for the selector when using the Indicate on Screen function.
• The Click Trigger activity would return a true value when interacting with an unresponsive Internet Explorer window.
• Fixed an issue that caused the target Java application to suddenly close when the Text Exists activity was used in a loop.
• The Microsoft Dynamix 2009 application would suddenly close after using the Indicate on Screen function.
• Fixed an issue in which grid elements from a custom application were not detectable.
• Fixed an issue that caused a Silverlight application to be regarded as a single element, instead of properly identifying individual UI elements.
• The Find Text Position activity would return an error message when used on Chrome or Firefox.
• Selectors with wildcards would not function on SAP applications.
• The MDesktopPane element type was not detected in custom Java applications.
• Using the Type Into activity with the SymulateType property enabled did not type spaces in a text box in Internet Explorer.
• A pop-up prompting to install the extension for Java was continuously brought up whenever a process attempted to start a custom Java application.
• The Browser is not supported error would be shown when trying to indicate elements in Mozilla Thunderbird.
• Selectors that had multi-line text attributes would fail to validate.
• The Type Into activity would fail to type anything after encountering the [ or ( characters.
• Fixed an issue that caused the Type Secure Text activity to stop typing after encountering the [ character if the SendWindowMessages property is set to true.

Known issues

• Internet Explorer memory usage increases after long-term, continuous interaction. We recommend reopening the browser whenever memory usage increases.
• Extensions for browser are no longer functional after updating Windows 10 to version 1903. We recommend reinstalling the extensions after performing the specific Windows 10 update.

v19.11.2

Release date: 10 February 2020

Improvements

This patch upgrades the Cloud OCR engines in the UI Automation package to support TLS v1.2, as the older v1.0 and v1.1 are approaching end-of-life.

v19.11.1

Release date: 20 January 2020

Improvements

As part of our further development of the Workflow Analyzer, we have implemented specific rules for the UI Automation activity package in this release.

Bug Fixes

• Text was not written in Chrome by the Type Into activity used with the SimulateType property enabled.
• Fixed an issue that caused inconsistent interactive selection behavior because of high latency over an RFP connection.

v19.11.0

Release date: 9 December 2019

Improvements

Selectors can now be generated for the Hitachi JP1/Automatic Job Management System 3 (JP1/AJS3) application.

Breaking changes

• All activities used for working with FineReader and FlexiCapture Abbyy product families were moved into a separate package named UiPath.Abbyy.Activities. This has led to a breaking change that caused the version to skip ahead from v1.8.1 to v2.0.0. for the UiPath.Vision.Activities package, and from v19.10.1 to v19.11 for the UiPath.UIAutomation.Activities package.
• The activities moved from the UiPath.UIAutomation.Activities to the UiPath.Abbyy.Activities package are Abbyy OCR and Abbyy Cloud OCR.

Bug fixes

• The value selected for the KeyModifier property across all UI Automation activities was not saved.
• Interactive selection launched from the Selector Editor did not minimize Studio.
• Indicating a web selector that contained & caused the resulting selector variable to be invalid.
• An invalid or empty selector was generated for the title bar of Excel.
• Fixed an issue that caused anchor selection to be faulty in cases when different UI regions were overlapping.
• The same anchor could be indicated multiple times in the case of overlapping UI elements when using Computer Vision activities.
• When targeting text without specified anchors with the Computer Vision activities, an incorrect target was sometimes displayed at runtime.
• Distinct anchors set for radio buttons with different labels would sometimes be considered duplicates.
• In certain situations, text that was correctly detected by OCR was not processed by the Computer Vision activities.
• Fixed an issue that caused invalid selectors to be generated for web page elements in Chrome selected with the AA framework.

Known issues

• The UiPath.Abbyy.Activities package cannot be used with versions lower than v19.11 for the UiPath.UIAutomation.Activities package.
• If Abbyy OCR or Abbyy Cloud OCR are set as default OCR engines in Studio Project Settings, you might lose this setting when upgrading to UiPath.UIAutomation.Activities v19.11, with or without the UiPath.Abbyy.Activities package.
• In certain situations, when installing UI Automation 19.10 or above in a project that already contains the UiPath.AI.ComputerVision.Activities package, the warning message is not always displayed.

v19.10.1

Release date: 11 November 2019

Improvements

The Computer Vision activities have now moved to the UI Automation activities package, as the newer technology offered by them is more and more becoming essential for automating various environments that are hard to target by other means. As a result, the documentation for these activities has also moved to the UI Automation section in the docs.

The Callout activity has changed its name to Tooltip, to better reflect the actual use case of the activity. This is only a cosmetic modification, so you don't have to worry about any old workflows breaking.

We’re proud to present the support for Webdriver processes. What this means for you is that headless browser automation is now a thing, and you don’t necessarily have to rely on extensions anymore.

We have further increased language support by adding Turkish, Portuguese (Portugal), Spanish (Latin America), and Spanish (Spain) to the list of languages present in the UiPath Platform.

The Microsoft Project Oxford Online OCR activity has been deprecated.

The Microsoft Azure ComputerVision OCR activity now has a new option named UseReadAPI that enables you to handle handwritten documents.

The Computer Vision Recorder now supports Shift + Click for editing anchors at design time.

The hotkey for opening the Computer Vision Recorder has been changed to Alt + Ctrl + V in Studio. Also, the Recorder can now be found alongside the rest of the recorders, in the Recorders drop-down.

SAP

Interactive selection now properly generates selectors for SAP popup windows.

The SAP grid technical header attribute is now supported by the Extract Structured Data activity.

The Click and Check activities are able to interact with SAP grid table controls.

Selectors can now be generated for SAP Menubar controls.

Silverlight

Silverlight popup windows now generate valid selectors.

Bug fixes

• Fixed an issue that caused the Key Press Trigger activity to crash when it was set to monitor modifier keys.
• Users could create variables that contained invalid characters.
• The Anchor Base activity's body was erroneously drawn at design time.
• The Computer Vision Recorder now supports the Shift + Click command for editing anchors at design time.
• On 2K and 4K resolutions, Anchor/Target pairs valid at design time were valid at runtime.
• Attributes obtained from the IAccessible2 accessibility API were not validated.
• Particular elements were identified even if they had ancestor elements with the aastate=”invisible” attribute.
• Using Data Scraping on an Excel table would return also return all empty cells.
• In some cases, child elements inside a popup window were not detected.
• Improved the behavior of the WaitVisible property to better identify elements inside the target window.

Java

• Rarely, interactive selection on the first column of a CJSpread table would appear offset.
• Data could not be extracted from customized JTable cells, resulting in a thrown exception.
• An exception was thrown when trying to extract data from a JTable cell that contained invalid XML characters.
• Improved the selection of elements inside the Eclipse application.
• Element detection inside CAA Tables has been improved.
• Selectors were not generated for Java SWT apps.

Silverlight

• Adding an anchor from the Selector Editor window would cause the selector to become invalid.

Known issues

• Enabling the Simulate Click or Simulate Type properties of an activity ignores the Clipping Region and Cursor Offset parameters of that activity.
• Drop-down menus are not clickable with the Computer Vision activities in SAP. A workaround for this is using the CV Type Into activity with the first few characters of the specified item followed by enter.
• If the target Windows session is not fully initialized, the Take Screenshot activity does not return any output.

Edge

• Interactive selection does not work for Edge until all corresponding processes are terminated from the Task Manager. It is recommended to close the browser and terminate its process right after you install the extension.

WebDriver

• Currently, the WebDriver protocol can only be used with Google Chrome and Mozilla Firefox.
• If multiple tabs are opened and a selector cannot be found, the execution repetitively switches between tabs in a constant retry to find the target selector. It is recommended to use a single tab in browser automations with the Webdriver protocol.
• If the selector for the Close Application activity uses a <WND> tag, the browser session is closed, but the webdriver process remains active.
• For headless browser automation in Chrome, the Get Visible Text activity throws an exception if the target element is not inside the window frame when it opens. This is because the Chrome headless window opens in a small resolution by default.
• Selectors for elements inside iframes cannot be validated.
• Activities that trigger hardware events (such as Click or Type Into), need to be configured to use the SimulateClick, SimulateType, or SimulateHover properties instead of the SendWindowMessages property.
• Headless browser automation does not use a visual browser window, making events monitoring an unsupported action.

Selectors

• The Non-Greedy search capability is currently not supported for Universal Windows Platform applications.
• Fuzzy and RegEx search in selectors are not validated for html tags containing the app attribute which are used to identify a process name.

v18.4.6

Release date: 20 September 2019

Improvements

We have improved the Visible Text Scraping on Multiselect Scroll controls in an Oracle Fusion application.

v19.8.0-ce

Release date: 27 August 2019

Note: This is a community release, which means that in order to be able to download the package, you have to select Include Prerelease in the Package Manager. For more info on installing packages, go here.

Improvements

This release brings a long-awaited feature that makes your experience with building workflows a lot more pleasant - Project Settings enable you to configure certain properties for all the activities from a single place.

The HandwritingRecognition option was added to the Microsoft Azure Computer Vision OCR activity. Reading documents written by hand is always a challenge. Ease your job by using the new HandwritingRecognition option that can extract information from handwritten documents.

Localization has been enriched. We now added German, Spanish (Latin America), Portuguese (Brasil), and South Korean.

Added the possibility to configure automatic scrolling of pages, either by a custom number of lines or one screen at a time.

As a result of working to provide native automation for Chromium, you can now generate native selectors for applications embedding Chromium through CefSharp.

Added the ClickType property to the Click Trigger activity which allows you to specify the default type of trigger for a click event.

It’s now possible to automate desktop Silverlight applications by simply installing the corresponding extension.

Java

Selectors for the NetPhantom framework are now natively generated.

Various improvements to element selection from CAA Tables have been made.

Bug Fixes

• Selectors that contained an idx attribute with a value greater than 1 and exact search attributes would not locate target elements.
• Opening an unelevated instance of UI Explorer and selecting an element from an application with a higher priority would generate selectors after a considerable delay.
• Fixed an issue that prevented UIA selector validation on table views in Microsoft Office applications.
• Element highlight during interactive selection would appear offset when using multiple displays.
• Fixed several issues caused by foreground windows becoming null, leading to the Desktop has been disconnected while performing UI actions exception.
• Closing a minimized UWP (Universal Windows Platform) application would make it impossible for the next activity to send input while throwing an exception.
• The Open Browser activity would throw an exception when used after a Close Tab activity on Chrome version 36.
• Fixed an issue that caused the default framework selection to become AA when Firefox Webrenderer was turned on.
• On rare occasions, child elements were not identified in WinForms applications.
• In Excel, child elements were erroneously identified.
• In some WPF applications, particular elements would generate inconsistent selectors.
• The Key property in the Key Press Trigger activity received string input without requiring the use of quotation marks.
• The UIA framework would sometimes inaccurately compute the index attribute, leading to an element being reported as unique, even though multiple similar elements existed matching a given attribute.
• The Get Full Text activity would throw an exception when used on the QMF for Workstation application.

SAP

• Selectors were not generated for grid control items in SAP if the particular grid is inside a custom control.
• Using a full SAP ID with wildcards would generate invalid selectors.
• Selectors for column and row headers were erroneously generated.

Silverlight

• The Set Focus activity would not properly function for some Silverlight elements.

v19.7.0

Release date: 16 July 2019

Improvements

This minor update brings the Chinese language to the group of officially supported languages for versions 19.7 and above.

Screen scraping can now be performed by using the entire suite of OCR engines supported by the UiPath Platform.

The Chrome Extension can now also be installed on Chrome versions lower than 64.

It’s now possible to create automation projects for OpenJDK.

The aastate attribute can now be included in WND selectors.

Citrix

Detection of UI elements was improved to support different resolution settings and scaling modes.

SAP

Improved selector generation to allow unique identification of SAP session windows.

Selectors for SAP now benefit from the getTooltip attribute. It returns the tooltip message from an element that includes a tooltip.

When indicating SAP elements, you can now generate AA selectors besides the default SAP selectors.

Events monitoring has been improved to properly interact with target activities.

Java

A backup of the original accessibility.properties file is now created when you install the Java Extension.

Some improvements were made to decrease the installation time of the Java Extension.

Bug fixes

• The UI framework would change back to Default after using the Delay function during interactive selection. Note that the issue did not occur if the framework was changed from the UI Framework drop-down.
• The Click Trigger activity on a web page element in Internet Explorer or Firefox was not blocked by the BlockEvent property. This happened on 32-bit machines.
• On particular web pages, the Data Scraping wizard did not scrape data from the second page.
• The SetupExtensions.exe /chromepolicy /uninstall command did not properly remove the Chrome Extension.
• Monitored events were not detected on web browser elements if the corresponding selector contained the idx attribute.
• The Copy Selected Text activity would return an empty output if the SendWindowMessages property was enabled.
• In some cases, the aastate attribute would be ignored during process execution.
• The htmlWindowName attribute is now truncated and replaced with a wildcard if its length exceeds 256 characters.
• Several improvements have been made to the Chrome Extension installation via command line arguments.
• When the Monitor Events activity is used inside a browser window or browser context, user events triggered with partial selectors were not detected.

SAP

• Selectors would not be generated for elements returned via API calls.
• The Select Item activity would return incomplete selectors for particular tree list items.

Java

• Fixed an issue that caused selectors for particular elements in a tree list to become invalid on process execution.

Known issues

SAP

• Only the top-left element can be identified in collapsed SAP tree list.

v19.4.2

Release date: 26 June 2019

Improvements

We want to reach out to the entire world and make automation a language everyone can speak. So, starting with this release, the entire platform is available in Chinese.

Note: Chinese can only be used in this package when installed in Studio v2019.4.4 or v2019.7 or above.

v19.6.0

Release date: 24 June 2019

Improvements

We’re glad to introduce support for web and native applications exposed through the Microsoft App-V virtualization technology. Selectors are now natively generated for the applications exposed through this virtualization solution.

Interactive selection for the Microsoft Office suite now generates UIA selectors by default instead of AA. This considerably improves generating selectors, especially for the Slide Panel and Main Body in PowerPoint, and various Excel elements.

Several improvements were made regarding element detection in SAP. On the one hand, item selection for SAP GUI Table Controls is now possible with multiple activities, such as Select Item, Select Multiple Items, Click, Highlight, and more. On the other hand, it’s now possible to generate selectors for SAP list trees.

Native selectors can now be generated for applications running on JRE and JDK 9, 10, 11, and 12.

Bug fixes

• The Type Into and Type Secure Text activities did not work properly in web applications when the EmptyField and ClickBeforeTyping check boxes were simultaneously selected.
• Selectors that contained two or more wildcards could not be validated.
• The Click Trigger activity was inconsistent after the UiPath.UIAutomation.Activities package was upgraded from v18.4.3 to v19.4.1.
• On rare occasions, interactive selection would suddenly end, returning an incorrect selector after previously obtaining a UIA selector from a UWP native application.
• The Type Into, Click, and Click Image activities would considerably reduce the process execution performance when used on Internet Explorer.

Java

• Selecting particular elements from AWT lists in Java applications would generate selectors for different elements.
• In particular cases, using the Get Attribute activity in Java SwingSet applications would throw an exception.

SAP

• Selectors were not generated for nodes with no text labels in SAP trees.
• The Select Item activity did not properly interact with SAP menus which contained multiple top folders.

Edge

• On a machine with multiple users, the Edge extension could only be installed for a single user.
• A confusing error message was displayed after the Chrome extension was uninstalled via the SetupExtensions /ChromePolicy /Uninstall command.
• The Select Item activity would not identify elements inside InfoPath combo boxes.
• Executing a process that included an Open Browser activity that launched Internet Explorer to navigate to a trusted site threw an exception. This happened if the Enable Enhanced Protected Mode or the Enable 64-bit processes for Enhanced Protected Mode options were enabled.
• The Find Element activity did not wait for the browser to finish navigating to a page, generating invalid selectors.
• The Find Element activity would sometimes be unable to detect elements from inactive tabs in Internet Explorer.
• Web page UI elements that were not in view were improperly targeted by the Click activity in Internet Explorer.

Known issues

• Selectors for the Add new sheet button in Microsoft Excel 2016 can not be generated. This is because the object is not exposed via the Active Accessibility or the UI Automation framework.

App-V

• The Java extension can not be installed for App-V Java applications that are virtualized in the JRE.

Java

• Detection of UI elements in Java 9+ applications on Windows Enterprise editions is faulty.

v19.5.0

Release date: 21 May 2019

Improvements

All activities that use images as targets, such as Find Image Matches, have a new property, called Profile. This drop-down enables you to change the image detection algorithm and use the new Enhanced algorithm, which can identify images with more precision at the expense of more resources.

Always at your fingertips, the UI Explorer can now be opened from the options menu in the body of any activity that utilizes selectors. Also, the user interface of the UI Explorer has received some minor cosmetic changes.

The Change Reading Options of Current Document window is now automatically opened and the correct accessibility settings are selected when you indicate elements from a PDF file in Adobe Reader DC.

Selectors can now be generated for trees in the SAP Business Client 6.5.

Screen and Data Scraping can now be used to create your automation projects for applications relying on the JxBrowser library.

Bug fixes

• Selecting UI elements from high integrity applications would throw an exception.
• Addressed several issues in which the Simulate Type and Simulate Click properties would inconsistently perform on particular events.
• In the SAP Business Client, selectors were not generated for tree elements that contained slashes.
• UIExplorer would stop responding when you selected elements from particular websites in Chrome or Firefox.
• The BlockEvent property of the Click Trigger activity would not function on the Close button of an application or web browser.
• The Select Multiple Items activity would throw an exception when used in Internet Explorer.

Java

• Selectors were not validated for internal frames and title panes in Java applications.
• Columns with 0 width are now ignored during data extraction.
• The Check activity would throw an exception after changing a checkbox selection in Java applications.
• The Type Into, Set Text, and Click activities did not function on tables in Java applications.
• Using the Select Multiple Items on specific list elements in Java applications would throw an exception.

v19.4.1

Release date: 25 April 2019

Improvements

Variables can now be used when editing a selector in the Selector Editor, so now you can easily store parts of selectors in variables and reuse them without a hassle.

Edge (Experimental)

The v19.4.0 UI Automation package now makes it possible to create automations in the Edge browser!

JxBrowser

There’s always something more to automate! With this release, we make it possible to natively generate selectors for applications that rely on the JxBrowser library. No extensions required!

RDP Extension

Creating automation projects over RDP connections just got a lot easier. With the help of the Windows Remote Desktop extension, selectors are natively generated.

You’ll be happy to hear that you can now create browser automations with native selectors for web applications exposed through Citrix Virtual Apps and Desktops.

Since we’re constantly working on new updates for you, we made it possible for the UiPath Remote Runtime component to support multiple versions.

The UIA_IsEnabledPropertyId attribute is now exposed in selectors. This enhances UI element detection in applications that rely on the UI Automation framework.

User events monitoring faced an overhaul to address different issues when detecting trigger events, while also improving performance.

Bug fixes

• Fixed an issue that caused Click Image to throw an exception when used after a Find Image activity.
• Using the Click Image Trigger activity with the Block Event option enabled would block all clicks on the target application. This happened if the corresponding selector was targeting the entire application.
• When throwing an exception, the Send Hotkey activity caused the CTRL key to remain stuck.
• Studio froze when using UiExplorer with an instance of Internet Explorer that had Enhanced Protected Mode enabled.
• Hovering or Indicating on Screen in a PowerShell console window caused Studio to crash.
• In Java applications, the Click activity used with hardware events would fail to perform on UI elements from a different tab than the current one.
• The Chrome extension would fail to install after upgrading Google Chrome to version 73.
• In a Citrix environment, the running process would throw an error if it contained the Anchor Base activity.
• The Take Screenshot activity did not return any output if the Windows session was not fully initialized.
• In a Citrix environment, selectors were not generated for windowed mode Apps.

Known issues

• The Tesseract OCR engine fails to properly read some images with black borders.
• The Windows Remote Desktop extension works only with RDP clients that use mstsc.exe.
• Executing a process that scrapes a large text file with the Get Full Text activity over an RDP session throws an exception.
• The RDP extension can only be installed per user. This is done either from Studio or the Command Prompt.
• Jobs started from Orchestrator on an RDP machine throw an exception after many executions. It occurs after the RDP connection is left in a disconnected state multiple times.

Citrix

• After you change DPI scaling levels, it is mandatory to restart your Citrix session for selectors to be accurately generated.
• Using multiple displays with different DPI can cause inaccurate detection of UI elements when the target window is moved across the displays.

Edge

• The UiPath Edge extension needs to be installed on Windows 10 build 1803 or above.
• The UiPath Edge extension does not work for a user on a machine if it has been already installed by a different user.
• Processes that use the UiPath Edge extension can not be started from Orchestrator on a machine on which Edge is the default browser.
• In Edge, web page elements are not detected if the web pages are loaded from the local machine.
• When automating the Edge browser, selectors containing the htmlWindowName attribute are not validated.
• The Type Into, Type Secure Text, and Send Hotkey activities need to have the ClickBeforeTyping property enabled. In general, for browser automations, it is also recommended to enable the SimulateClick property for activities that perform click operations.
• On some occasions, element highlighting becomes offset or imprecise.

JxBrowser Applications

• For JxBrowser applications, the Recording wizard is not yet supported.
• When you use the Type Into activity, be sure to enable the ClickBeforeTyping property.

v18.4.5

Release date: 27 March 2019

Bug Fixes

• The Extract Structured Data activity did not return any data when used with Java applications v1.3 to v1.6.
• When selecting web page elements in Internet Explorer, the wrong idx attribute would be generated, causing selectors to become invalid.
• The Chrome extension would fail to install after upgrading Google Chrome to version 73.

v18.4.4

Release date: 27 February 2019

Improvements

You asked, we delivered! One of the main improvements brought by the v18.4.4 UI Automation package is the support for UIA selectors in Edge.

Breaking changes

• The Extract Structured Data activity does not return any data when used with Java applications v1.3 to v1.6. Please note that this can cause a breaking change and it is recommended to upgrade Java to a newer version.

Bug fixes

• The Click activity would often inaccurately detect web page elements that were not in view.

v19.3.0

Release date: 20 February 2019

Improvements

The v19.3.0 UI Automation package now makes it possible to create automations in the Edge browser!

UI elements in XenApps are now detected even on non-standard DPI.

We’re always looking to extend your automation capabilities. As such, we have implemented support for applications that rely on the JxBrowser library. Selectors are created natively, without having to install any extensions.

The newly developed Microsoft Azure ComputerVision OCR engine uses the new API from Microsoft, enabling you to keep up with the evolution of technology.

We've added the ability to automatically downsize images to the Google Cloud Vision OCR activity, adding a new property called ResizeToMaxLimitIfNeccesary. This has been done to make sure the size of your images does not break the maximum limit of the engine.

The Abbyy OCR activity can now be configured to use Abbyy FineReader Engine 12 via the FineReaderVersion drop-down property. Also, the PredefinedRecognitionProfile property can be used to use one of the official Abbyy recognition profiles and the CustomRecognitionProfilePath property can be used to load in your own recognition profile into the project.

Breaking changes

• Due to some internal dependencies being updated, starting with this version, the minimum required version of Studio for using this package has changed to v2018.4.4 or v2019.2 or above.

Bug fixes

• Google Cloud OCR crashed when receiving an image larger than its maximum limit.
• Google OCR was not renamed to Tesseract OCR when used in certain activities.
• The Extract Structured Data activity did not return any data when used with Java applications v1.3 to v1.6.
• In the SAP application menus, only the first item on the list would get recognized.
• Fixed particular cases when the UIA selection was returning a non-UIA selector.
• The Find Text Position activity was unable to find text that contained spaces in Internet Explorer.
• The Text Exists, Click Text, Find Text Position, and Hover Text activities did not properly interact with particular character combinations in Internet Explorer 11.
• In some cases, wildcard matching did not work correctly when used with Internet Explorer and other Windows 10 applications.
• Fixed several issues that were causing selectors to not generate for UI elements when the SAP Business Client is used.
• The Set Text activity did not work inside JTable cells with the Text role in Java applications.
• Using the Check activity on checkboxes inside Java applications would return an error.
• Fixed an issue that was causing the Robot Executor to stop functioning during process execution.
• On some occasions, the Get Visible Text activity would fail and throw the Capture timeout error.
• Additional fixes were made to improve the functionality of the Extract Data activity on tables in Java applications.
• The Screen Scraping wizard would not return any data when used with Office 365 components.
• The Attach Browser activity could not switch to a frameset web page tab in Internet Explorer.
• On particular web pages, the idx=’1’ attribute in a selector would cause trigger events to be ignored by events monitoring.
• The Type Into activity was unable to type particular characters.

Known issues

Edge

• The UiPath Edge extension needs to be installed on Windows 10 build 1803 or above.
• The UiPath Edge extension does not work for a user on a machine if it has been already installed by a different user.
• Processes that use the UiPath Edge extension can not be started from Orchestrator on a machine on which Edge is the default browser.
• In Edge, web page elements are not detected if the web pages are loaded from the local machine.

JxBrowser Applications

• For JxBrowser applications, the Recording, Data Scraping, and Screen Scraping wizards are not yet supported.
• When automating JxBrowser applications, it is recommended to use the default framework when building selectors for JCef and Cef applications.
• When you use the Type Into activity, be sure to enable the ClickBeforeTyping property.

Citrix

• After you change DPI scaling levels, it is mandatory to restart your Citrix session for selectors to be accurately generated.
• In a Citrix environment, using multiple displays with different DPI can cause inaccurate detection of UI elements when the target window is moved across the displays.

v19.2.0

Release date: 18 February 2019

Improvements

The new Context Aware Anchor has been created by building upon the old Anchor Base activity. To increase precision, it now takes into account the pairs of anchors and targets, without requiring an anchor to be unique.

The Google OCR, Google Cloud OCR, and Microsoft Cloud OCR engine activities have been renamed to Tesseract OCR, Google Cloud Vision OCR, and Microsoft Project Oxford Online OCR, respectively. Don't worry, as this does not cause a breaking change to your already existing workflows!

The Extract Structured Data activity has two new properties that enable you to choose what kind of click you want to use when changing pages if the data you want to extract spans multiple pages.

Bug fixes

• Fixed an issue that caused the Click Trigger, Click Image Trigger, and Key Press Trigger activities to crash when using certain applications.

v18.3.6962.28967

Release date: 23 January 2019

Improvements

To ensure backward compatibility, the HtmlWindowName attribute in html tags is now ignored when UI elements are selected in pop-up windows in Internet Explorer.

A few steps need to be performed if you want to use a different UI Automation package, and you can read more about it here.

v19.1.0

Release date: 21 January 2019

Bug fixes

• The Data Scraping wizard threw an error if you tried to scrape nested tables in Internet Explorer.
• In some cases, the Click activity would not accurately identify web page elements that were not in view.
• Particular keyboard input events were erroneously flagged by the Type Into with the SimulateType property enabled.
• In Java apps, selectors were improperly built for contextual menu items.
• Selecting CSS elements from a web page in Internet Explorer would return an error.
• Selectors could not be properly generated by UI Explorer for particular Java apps. In some situations, this would cause the Java app to stop working.
• The Click activity with the SimulateClick property enabled would improperly interact with particular web page elements in Internet Explorer.
• Selectors were erroneously generated when using the SAP Business Client (NetWeaver).
• The Type Into activity with the SimulateType property enabled would not always properly type inside fields on the Orchestrator login page.
• Selection algorithms for Java applications with customized UI have been improved, thus fixing several issues the Extract Data activity had.

v18.4.3

Release date: 10 January 2019

Improvements

This new year brings two more languages in the entire UiPath Platform - French and Russian. Since we layed down the foundations of localization in our previous release, we are continuing our efforts in bringing you a more immersive experience and lowering the language barrier bit by bit.

v18.4.2

Release date: 7 December 2018

Improvements

With Citrix environments being so popular, we are further extending automation capabilities with native support for Citrix XenApps. To benefit from this, the UI Automation package must be installed, along with the Citrix Remote Runtime.

Also, dark times ahead, the Dark Theme is now available, in its beta version, on all of the activities and wizards in this package.

Breaking changes

• The HtmlWindowName attribute in html tags was ignored when UI elements were selected in pop-up windows in Internet Explorer. As a result, selectors were incomplete, causing actions to be performed on the parent window instead. Please note that processes created with the UiPath.UIAutomation.Activities v18.3.6962.28967 package ignore the HtmlWindowName attribute in selectors, while v2018.4.2 does not. This might affect process execution and you should manually update them.

v18.3.6897.22543

Release date: 20 November 2018

Breaking changes

• The HtmlWindowName attribute in html tags was ignored when UI elements were selected in pop-up windows in Internet Explorer. As a result, selectors were incomplete, causing actions to be performed on the parent window instead. Please note that processes created with the UiPath.UIAutomation.Activities v18.3.6962.28967 package ignore the HtmlWindowName attribute in selectors, while v18.3.6897.22543 does not. This might affect process execution and you should manually update them.

v18.3.6877.28298

Release date: 31 October 2018

Improvements

The UiPath.Core.Activities package is now split into two distinct packages: UiPath.UIAutomation.Activities and UiPath.System.Activities. The first contains all the activities that mimic human interaction, such as Click or Type Into, while the latter sums up all the blocks required for building an automation, from invoking another workflow to logging a custom message in Orchestrator.

This change was made so that both in present and future versions, you can reference any version of the UiPath.UIAutomation.Activities and UiPath.System.Activities packages as dependencies for your projects, completely independent of Studio. This is a step forward for being able to update UiPath Platform components without worrying about how they affect your automations.

v2018.2

Release date: 22 May 2018

Improvements

We've added a new Continue activity to the Core package. It enables you to streamline conditions inside a For Each loop, without nesting If activities, by skipping iterations.

Four new activities have been created for the enhanced manipulation of DataTable variables:

• Lookup Data Table - Modeled after the Excel VLOOKUP function, it searches for relative cell values in a data table.
• Filter Data Table - Enables you to select filtering conditions for a data table with the help of a wonderful wizard.
• Sort Data Table - Sorts a data table in ascending or descending order based on the values in an indicated column.
• Remove Duplicate Rows - Removes the duplicate rows from a specified `DataTable variable.