UiPath Release Notes

UiPath Release Notes

Release date: 12th December 2018

What's New

Authentication

You asked we delivered. This release ships with the much-awaited support for SAML 2.0 which allows Orchestrator to handle single sign-on authentication. You can now take advantage of the speed and convenience of accessing your Orchestrator instance with the same set of credentials used within your organization. In this regard, the new ExternalAuth.Saml2.Enabled parameter has been added in the web.config file. For more details about how to configure and use this new feature, click here.

A notable addition in this newest release, Smart Card Robot Authentication is now here to handle Common Access Cards and Personal Identity Verification support. As such, Unattended, Development, and NonProduction Robots can simply use your SmartCard to start sessions on machines, besides the conventional way. The connection method is easily selected when a Robot is created or edited. Check out how it is done on this page. Lastly, the Orchestrator API, namely the /odata/Robots endpoint, has been updated to accommodate this functionality. An example is available here.

Scalability

Do you think Attended Floating Robots are sweet? Good! Because the Floating Robots feature has been augmented to incorporate Development Robots as well. This is a major step forward in ensuring better, more convenient resource management of your Non-Persistent VDIs and hotseat environments. Create and configure your Development Floating Robots and connect to them from any defined machine.

This, paired with the fact that you can now activate your Studio license from Orchestrator through the Robot that connects them, makes for a broader automation experience, since workflows can be executed, modified, and debugged with Development Floating Robots. For more information, click here.

Orchestrator’s scheduling mechanism has been substantially improved in terms of performance. As a result, enabling multiple custom schedules in clustered environments does not pose a threat to the performance of system operations.

Extensibility

For an even more fruitful partnership between your UiPath automation and your complex existing app network, we made it possible to use webhooks with Orchestrator. You can now subscribe to Orchestrator events and send them to any external DCM, BPM, or CRM solution. Multiple users can be informed, for example, that there is a new item in a given queue, a schedule has failed, or a process has been updated. As you might have gotten used to by now, the Orchestrator API has also been updated to accommodate this new functionality. For more information, please see the documentation here and some API examples here.

User Experience

Furthering our efforts to bring you a smoother user experience, UiPath Platform now incorporates the highly-anticipated Dark Theme. Both Studio and Orchestrator have been painted in an eye-soothing gray, with bits of blue to keep the products’ color signature. Panels and controls are all available in a darker shade, making the whole UI more appealing and easier on the eyes. Please note that for Studio this feature is still considered experimental. For the Dark Theme to work, automation projects must have as a dependency at minimum UiPath.UIAutomation.Activities v18.4.2 and UiPath.System.Activities v18.4.1.

If you ever wanted to release the licenses on a machine, you are familiar with the tedious task of having to contact your IT support team and waiting for it to happen. As of v2018.4, this is no longer a problem as you can now easily enable/disable non-production and unattended-purposed machines. License consumption in this scenario is now yours to manage and it can be done straight from the convenience of your own Orchestrator instance. See here how to do that. If the Orchestrator API is more of your thing, then you can access a request example here.

Improvements

Validation has been added to the /odata/Processes/UiPath.Server.Configuration.OData.SetArguments endpoint. Additionally, please note that this endpoint can no longer be used to change the input and output parameters of an automation package if you upload it to Orchestrator through the API, the Packages page, or the NuGet feed.

Additionally, please note that the serialized string of input and output parameters is now used all throughout Orchestrator.

We simplified the process of creating an Attended Standard Robot, by removing the Password field. A gladdening "side-effect" of the removal is the consistency between the Floating and Standard Robot-creation scenarios.

All email address input fields are now limited to 254 characters.

In terms of setup, you might want to know that the UiPathPlatformInstaller.exe, UiPathStudio.msi, and UiPathOrchestrator.msi installers now also check the operating system to ensure a smooth execution of the entire ecosystem.

SignalR has been upgraded to v2.2.3 in an effort to attain a more reliable WebSocket communication and better memory management.

The performance of deleting Robots has been significantly improved in the context of a large deployment.

A confirmation dialog is now displayed when you grant a user Edit permissions on Robots. This comes in addition to the existing Edit permissions on Settings, Roles, and Users which require user confirmation.

The Jobs and Robots charts on the Dashboard have been enhanced so as to achieve better visibility.

Breaking Changes

  • Updating a v2016.2 Orchestrator to any newer version is not possible if you have duplicate entries in the SQL database. Remove the duplicates prior to database migration as a workaround. Additional information is available here.
  • If you have more than 2 million logs in the SQL database, the update process times out. If your logs are kept in Elasticsearch, the update is smooth regardless of the number of logs maintained there.
  • In rare cases, if you click the Allocate button, in the Tenants page, an error message is displayed and the page is refreshed. Use the License page to distribute your licenses across tenants, if this occurs in your environment.
  • For enabled webhooks, payloads are not sent if you manually stop or kill a pending job.
  • If a large number of Robots become unresponsive at the same time, the robot.status webhook event is not triggered.
  • The Job.created webhook event is not sent to an external system if it is triggered by a Robot.
  • It is possible to add duplicate webhooks through POST requests to the /odata/Webhooks endpoint.

Known Issues

  • Updating a v2016.2 Orchestrator to any newer version is not possible if you have duplicate entries in the SQL database. Remove the duplicates prior to database migration as a workaround. Additional information is available here.
  • If you have more than 2 million logs in the SQL database, the update process times out. If your logs are kept in Elasticsearch, the update is smooth regardless of the number of logs maintained there.
  • In rare cases, if you click the Allocate button, in the Tenants page, an error message is displayed and the page is refreshed. Use the License page to distribute your licenses across tenants, if this occurs in your environment.
  • For enabled webhooks, payloads are not sent if you manually stop or kill a pending job.
  • If a large number of Robots become unresponsive at the same time, the robot.status webhook event is not triggered.
  • The Job.created webhook event is not sent to an external system if it is triggered by a Robot.
  • It is possible to add duplicate webhooks through POST requests to the /odata/Webhooks endpoint.

Bug Fixes

  • Installed versions of Robots on a machine were inconsistently displayed across multiple organization units.
  • "Robot is unresponsive" alerts were received despite having disabled Robot alerts. (Profile page > Alerts section > Robots).
  • When multiple new versions were available for a package, clicking the Latest button updated the package incrementally instead of updating it to the latest version in one go. This happened if you used an external feed.
  • Switching to an older version of a package in an environment caused the associated process icon to be updated in all environments containing that package. This happened if you used an external feed.
  • Development Robots having the same username were not correctly licensed if you had acquired fewer concurrent licenses than the number of Robots. One of the Robots was never licensed, and therefore was unable to execute jobs.
  • Switching from an API key to basic authentication credentials when securing your external feed prevented processes from being displayed. This occurred when you used the same deployment URL.
  • In rare cases, in Orchestrator environments with a Load Balancer, if you logged in with the same user on two different browsers, the first session did not expire after 1 minute.
  • If you created a schedule on an empty environment, the exceptions and their stack traces were logged twice in Event Viewer.
  • Business conflict exceptions such as failures to retrieve statistics for charts are now logged in Event Viewer under the Orchestrator.BusinessException source.
  • It was possible to add invalid cron expressions in schedules if they were disabled.
  • Better validation was added to the Security tab of the Settings page.
  • It was possible to create a process using a package that did not exist through POST requests to the /odata/Releases endpoint. Now, if you try to perform this call with a package that does not exist, an error is thrown.
  • A warning was displayed in the Parameters tab of the Edit Schedule window, if you replaced the initial process with one that had input and output parameters.
  • If you changed the email of an Active Directory user, Orchestrator failed to send a confirmation message on the newly added address.
  • An issue was fixed that prevented you from updating Orchestrator if your activities and/or automation packages were stored in a shared folder and did not have special elevated permissions. Now, when updating, UiPathOrchestrator.msi only requires Write access to the shared folder in which you store your packages.
  • The UiPathStudio.msi did not remove the Java extension through the Change functionality.
  • You could not reinstall Orchestrator if the folder you used had broken permissions.
  • The UiPathPlatformInstaller.exe stopped working if you started the installation process under a specific user, then tried to uninstall the products under a different user. Now, the UiPathPlatformInstaller.exe setup can handle multiple login sessions.
  • Better validation has been added for the TenantId parameter, when making requests to the /odata/Users endpoint.
  • Duplicate records were returned if you made calls to the /odata/QueueProcessingRecords/UiPathODataSvc.RetrieveLastDaysProcessingRecords(daysNo={},queueDefinitionId={}) and /odata/QueueProcessingRecords/UiPathODataSvc.RetrieveQueuesProcessingStatus() endpoints.
  • The /odata/Assets/UiPath.Server.Configuration.OData.GetRobotAsset endpoint has been deprecated. Instead, you can use the newly added one - /odata/Assets/UiPath.Server.Configuration.OData.GetRobotAssetByNameForRobotKey through POST requests. Last but not least, the Get Credential and Get Asset activities have also been updated to use the aforementioned call, if you are using them with a v2018.4 Orchestrator.
  • SQL queries for bulk operations caused deadlocks in the database. Multiple adjustments which improve bulk operations in terms of performance have been made.
  • A user that became idle was not automatically logged out of the application while on the Dashboard page.
  • An error message was displayed when you tried to add or edit a user without having permissions on Units. This occurred if you had organization units enabled in your Orchestrator instance.
  • The Platform does not support setting SSL protocols on HTTP client handler error message was displayed twice in the Event Viewer when Orchestrator was started.
  • An error message was displayed when you tried to log in using an incorrect password.
  • An error message was displayed when you cleared the Select All check box on the Manage Environments window before it was fully loaded.
  • The confirmation email concerning tenant creation was not sent despite having a valid email address and correctly set up email settings.
  • A user was able to see the Edit button on the Environments page despite not having the appropriate permissions.
  • Fixed an issue that prevented page numbering from being reset after a filter was applied.
  • Several of the latest generated alerts were not displayed in the Alerts drop-down.
  • The Account Lockout Seconds field is now limited to a value of 2592000.
  • An error message was displayed when you filled in more than 2000 characters in the Reviewer field on the Assign Reviewer window. The field is now limited to 64 characters.
  • Fixed an issue that allowed users to create a queue with a blank space character for a name.
  • An error message was displayed when you tried to add or remove Robots from an environment having at least 12,000 Robots.
  • The same confirmation message is now displayed at password reset, whether the user exists or not.
  • User details were not retrieved when you imported an Active Directory user group on an Orchestrator instance using Windows authentication.
  • Importing an Active Directory user group without defining organization units caused all the existing organization units to be assigned to each of the users.
  • Refreshing the Queues page while items were still being processed caused the containing queue to be displayed twice on the page.
  • When using Windows authentication, after your session expired you were redirected to the Login page of Orchestrator instead of Windows login.
  • Fixed an issue that allowed an Active Directory user to see the information from the Dashboard without having the appropriate permissions. This happened when being automatically logged into the Default tenant after session timeout of a different user.

Updated about a month ago


2018.4.1


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.