Release Date: 26th March 2018
Nothing is ever perfect, but we try to get closer with every release. This time, we focused our attention on providing you with the most secure RPA platform out there. As a result, in this hotfix, some security issues were resolved, along with other bugs that might have given you a hard time. Check out the details below.
- Starting a job from Orchestrator failed on Robot machines which had the
LoginToConsoleparameter set to
UiPath.Settingfile, and one of the following operating system updates installed:
- KB4088876 - for Windows 8.1 or Windows Server 2012 R2 Standard
- KB4088875 - Windows Server 2008 R2 SP1, Windows 7 SP1
- KB4088787 - Windows Server 2016, Windows 10 Version 1607
- KB4088776 - Windows 10 version 1709
For a full list of affected operating systems, please see this article.
get-infoRegutil command now also displays the date on which your license expires, in the Subscription expire date field.
- To better accommodate our users, NonProduction Robots are now able to execute workflows in debug mode from Studio. This makes in-depth analysis of workflows easier in Studio.
- In order to better track logs originating from activities interacting with the Silverlight extension, traces are now implemented in the slinject.exe Silverlight injector. This allows logs to be collected independently of the availability of slinject.exe.
- The Robot key stored in the
UiPath.settingsfile is now encrypted using the Data Protection Application Programming Interface (DPAPI) under the SecureLicenseKey field.
- In rare cases, a job failed to start and prevented you from starting other jobs on the Robot machine until it was restarted.
- We improved a response header that is used when logging in or out of Orchestrator, to improve the security of these pages.
- A message is now displayed when creating new roles which states that selecting the Settings, Roles and Users edit permissions can allow users to perform elevated operations, such as changing the password of another user.
- It is now possible to make POST/PUT/DELETE requests with the Orchestrator API, if you are using Windows Authentication.
- After several failed attempts of changing the password of the user you were logged in as, in the Profile page, a message stating the account was locked out was displayed but you were not logged out.
- The Orchestrator site became inaccessible if you deleted the database, manually created a new one with the same name, and then restarted the site.
VirtualNameattribute was added to a selector when working with Java apps and was removed because it is not a recommended attribute to build selectors with.
- Java Applet UI elements were not recognized in UiPath Explorer if the page was refreshed.
- UI elements in Java applications were not identifiable if the window needed to be scrolled in order to reach them.
- In rare cases, the Silverlight extension caused the Web Recording activity to become unresponsive while recording in Internet Explorer.
- Selecting a Silverlight web element while using the Web Recording activity caused Studio to become unresponsive.
- Fixed an issue which prevented users from inputting data to Fujitsu Java applications.
- The Variables panel froze when you tried to change variable details and had the German language pack selected as default in Windows and .NET Framework version 4.7.
- The Open Browser activity threw an exception when attempting to open the Mozilla Firefox ESR (Extended Support Release) version.
QueueItemvariable did not have the Progress property. Now, by using
QueueItem.Progress, you can read the Progress status of queue items.
- The ABBYY OCR activity consumed multiple licenses per query when used on a single page, with the Scale property larger than 1 and the Profile setting set to Legacy.