Banner background image
UI Automation Activities
Last updated Apr 26, 2024



Release date: 24 May 2021

Bug fixes

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


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.


Release date: 10 June 2020


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.


Release date: 10 February 2020


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.


Release date: 20 January 2020


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.


Release date: 9 December 2019


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.


Release date: 11 November 2019


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.


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 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.


  • 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.


  • 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.


  • 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.


  • 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.


  • 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.


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.


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.


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.


  • 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.


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


Release date: 16 July 2019


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.


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


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.


A backup of the original 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.


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


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

Known issues


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


Release date: 26 June 2019


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.


Release date: 24 June 2019


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.


  • 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.


  • 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.


  • 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.


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


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


Release date: 21 May 2019


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.


  • 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.


Release date: 25 April 2019


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!


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.


  • 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.


  • 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.


Release date: 20 February 2019


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


  • 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.


  • 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.


Release date: 18 February 2019


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.


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.

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.