Improvements​

• For auditing purposes, we added the necessary properties to several resources DTOs, hence to the response bodies of the following endpoints:
  • /odata/Users

• odata/Robots

• odata/Releases

• odata/Assets

• odata/Libraries

• Retrieving audit logs via API now returns entries in batches of maximum 3000 entries, to increase performance. To get the remaining entries, use the query parameters $skip and $top.

Bug Fixes​

• You could not debug assets per user/machine pairs from Studio. To check if a specific user-machine pair received an asset, you had to launch the job from the Assistant or Orchestrator. This is no longer the case.
• Trying to create a calendar without Edit permissions on Settings threw a "Calendar with the same name exists" error instead of "You are not authorized!". The behavior has been corrected and the right error message is displayed.

Improvements​

• Starting now, the Tenant Administrator role comes with View permissions on Background Tasks. This change does not alter existing Tenant Administrator roles. See details about default roles and their permissions.

• Hey there Automation User, we just unlocked the Logs [Create] permission for you by default. From now on you are able to create logs every time you run jobs in Orchestrator as an Automation User. To benefit from this configuration in your existing tenants, navigate to Tenant > Settings > Standard Roles, and update the Automation User roles to include the missing default permission.

  

Bug Fixes​

• Volgograd’s timezone in Orchestrator’s application settings has been renamed from (UTC+04:00) Volgograd to (UTC+03:00) Volgograd. This was a display issue, the timezone itself was correct (i.e. UTC+03:00).
• A Release does not exist error was thrown upon refreshing the monitoring details window for a process in a child subfolder (Monitoring > Processes > Include Subfolders > Processes Overview).
• Licensing overuse when you had no licenses of a kind left was not properly illustrated in Orchestrator on the License page due to no licensing cards being displayed. This behavior has been fixed and cards are displayed in overuse scenarios with 0 licenses.