Release date: 28th February 2019
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.
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 backward 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.
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.
Usernameparameter is now mandatory for PUT requests on the
- 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.
- The expiration date of a new host license is not propagated at tenant level. The tenants keep the expiration date of the previous license. To fix this, you need to reallocate the licenses to your tenants.
- 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.
Updated about a month ago