- Release notes
October 2021
-
For auditing purposes, we added the necessary properties to several resources DTOs, hence to the response bodies of the following endpoints:
-
/odata/Users"LastModificationTime": "2021-10-12T07:29:25.914Z", "LastModifierUserId": 0, "CreatorUserId": 0 -
odata/Robots"LastModificationTime": "2021-10-12T07:32:24.940Z", "LastModifierUserId": 0, "CreationTime": "2021-10-12T07:32:24.940Z", "CreatorUserId": 0 -
odata/Releases"LastModificationTime": "2021-10-12T07:29:25.914Z", "LastModifierUserId": 0, "CreatorUserId": 0 -
odata/Assets"LastModificationTime": "2021-10-12T07:57:15.145Z", "LastModifierUserId": 0, "CreationTime": "2021-10-12T07:57:15.145Z", "CreatorUserId": 0 -
odata/Libraries"Created": "2021-10-12T07:59:04.182Z", "LastUpdated": "2021-10-12T07:59:04.182Z", "Owners": "string", "IconUrl": "string", "Summary": "string", "PackageSize": 0, "IsPrerelease": true, "LicenseUrl": "string", "ProjectUrl": "string"
-
-
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
$skipand$top.For example, to get the second batch of 3000 audit log entries, the API call looks like below: GEThttps://{base_url}/{organization}/{tenant}/api/auditLog?top=3000&skip=3000
- 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.
Support for GCP
For those of you using Google Cloud Platform (GCP), we have added support for using this provider for elastic robot orchestration.
GCP is now available as an option in the Settings > Cloud Connections page.
New name for the machine template
The machine template used for elastic robot orchestration has been renamed from Cloud Machine Pool to Elastic Robot Pool.
More control over auto-scaling
We have added a few extra knobs to the Elastic Robot Pool machine template so that, when using auto-scaling (Automatically Create Machines is enabled), you can add specific rules for how and when new machines should be created. Here are the new controls:
-
Selecting the new Advanced option for Scheduling lets you set the allocation speed, as well as the number of machines you want to keep in standby and the idle time allowed for machines:
-
Profile scheduling is a new setting for the machine template which lets you specify exceptions - with a start and end time - during which you want a different scheduling profile to apply for the template:
For example, if your machine template uses the Balanced profile, but you know the end of the month is busier than usual, you can add an interval to use the Fast profile during the last 5 days of the month. This way, elastic robot orchestration is faster during this period, then reverts to the original profile set for the machine template - Balanced.
- 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.
- 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 existerror 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.
