Release date: 28th February 2019 Version number: 2018.4.4
Update dependencies and runtime rules at once across multiple automation projects stored locally or in source control repositories, using the Project Dependencies Mass Update tool available from Studio Backstage view or the command-line user interface. Once the changes are made, the modified projects can be saved locally or checked in to source control repositories. Moreover, projects can be published to Orchestrator or a custom feed. Find out more about the Project Dependencies Mass Update tool here.
Package management is now a breeze with our new bulk update feature. Yes, you heard that right. As of now you can update multiple processes at once in Orchestrator and it only takes a minute. Click here for more information.
You asked, we delivered! One of the main improvements brought by the v18.4.4 UIAutomation package is the support for UIA selectors in Edge.
Orchestrator drop-downs have been upgraded. We now have scroll bars to help you browse through all existing entries, even in the context of complex environments. The content is loaded dynamically and you can search for specific input at any time. Happy scrolling!
You can now configure whether the Remember Me check box on the Login page is displayed or not using the
Auth.RememberMe.Enabled parameter in
web.config. More details here.
You can now configure whether SignalR events triggered by updates on the Processes page are generated or not. The
Processes.TriggerUpdateRefresh parameter has been added in
web.config in this regard. To ensure backwards compatibility with Robots older than v2018.3, this parameter must be set to
True. More details here.
We have implemented a browser-based timer to work hand in hand with the authentication cookie. As such, as long as there are no user-initiated events (mouse or keyboard activity), the session is terminated according to the
Auth.Cookie.Expire parameter in
To address the inconvenience of manually disabling inactive accounts in Orchestrator, we brought to you a PowerShell script which takes care of the situation on its own. You can tailor the script to fit your needs and set the desired inactivity limit accordingly. Find the script in our public GitHub repository here. Please note that the script does not work for tenant admins.
You can now easily change certain details about a specific Robot without needing to know its password and username, by performing PATCH requests on the
To enhance the security of the Robot - Orchestrator communication protocol we added the possibility for the Robot to authenticate through a custom HTTP header. In this regard the
Scalability.SignalR.AuthenticationEnabled, is now at your disposal. Please note that if you enable this feature, also referred to as Robot SignalR authentication, you are no longer able to execute jobs on Robots with a version lower than 2018.4.3. More information is available on this page.
Lastly, to give you the possibility to control how special characters are parsed in the Orchestrator API, the
OData.BackwardsCompatible.Enabled parameter has been added in the
web.config file. For more information, click here.
For those that work offline, we have some good news: you can disable the default online feeds for Robot during the deployment process. This facilitates a seamless installation process even in restrictive environments without Internet access, from the command line. For more information, access this page.
Moreover, you can now configure the location of your automation processes, for Studio and Robot, through the command line of the
UiPathStudio.msi installer. This feature provides a customizable architecture to suit both strict deployments and hotseat scenarios. To read more about the newly added
PACKAGES_FOLDER parameter and how to use it in your mass-deployment of Robots, see this page.
In addition to that, the
UiPathStudio.msi installer enables you to easily set up your Citrix client extension with just a few clicks, as described here. If the command line is more of your thing, that's also now possible, as explained here.
Last but not least, you can now add your own activity feeds at install-time by using
UiPathStudio.msi's command line. More information about the
CUSTOM_NUGET_FEEDS argument and how to use it to set up your environment can be found here.
To ensure an even better integration between Azure and Orchestrator, it is now possible to include the local activity feed in your Azure environment directly at install-time, using the newly added
activitiesPackagePath parameter. To support this feature, you should also know that we added an archive,
UiPathActivities.zip, with all the activities in
UiPathOrchestrator.zip. To view more information on how to use this parameter, see this page.
You might be happy to know that you can use
UiPathPlatformInstaller.exe to set up UiPath Remote Runtime in the Citrix environment of your choosing. More information on this is available here.
UiPathPlatformInstaller.exe now also includes the Russian language, contributing to an immersive experience from the first click.
Usernameparameter is now mandatory for PUT requests on the
- 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.
- When using the Flow Switch activity, changing the
TypeArgumentproperty from the Properties panel scrambles the branches in the Flowchart.
- A Robot installed as a Windows Service is unable to install packages if the corresponding
Packagesfolder is shared and on a different machine. The Robot needs to be installed in user mode, and you can find out more on this page.
- If you have invalid cron schedules and you upgrade your Orchestrator instance from v2018.1.x or v2018.2.x to v2018.4.x, they are not going to work anymore. This occurs due to a change in the Quartz.NET validation code. Please make sure your cron expressions are valid before updating your environment.
- Using the
-fcommand to execute a process would ignore the Orchestrator activity feed.
Packcommand would return an error if the required dependencies were not available locally or in the NuGet download folder.
- The Click activity would often inaccurately detect web page elements which were not in view.
- Signing out of Windows caused any ongoing unattended jobs to stop with a "Wrong Password" error. This only occurred if the
LoginToConsoleparameter had been set to
- In rare cases, if you clicked the Allocate button, in the Tenants page, an error message was displayed and the page was refreshed.
- The Update button on the Edit Schedule window was disabled despite having selected a different process. This only occurred for a schedule that had been previously enabled on specific robots.
- Stacktrace information is no longer displayed in responses when making invalid requests to the Orchestrator API.
- We identified and fixed a security vulnerability which was found to impact Orchestrator. In this regard, the
System.Security.Cryptography.Xmllibrary has been upgraded to v4.4.2.
- To ensure a smooth experience in offline environments, the list of activity dependencies has been updated in all our installers. Please note that as a result, the size of the artifacts has increased.
The following activity packages and versions are included in the installers and are added as dependencies, by default, to a newly created project in Studio: