OUT OF SUPPORT

v20.4

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.

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.