- Release notes

Orchestrator release notes
Side panel layout updates
In an effort to improve the readability of the queue items side panel, we have changed its layout to a row format, and have made several minor font tweaks.
These updates aim to solve a rendering issue which caused content to have too little space in the old side by side layout to accommodate values. The underlying issue stemmed from a rendering change meant to account for any whitespace formatting coming from automations or raw content.
Changes to the count parameter
count
parameter in the Jobs
and QueueItems
endpoints is no longer true
by default for Enterprise tenants. To retrieve this information for jobs and queue items requests, add $count=true
to the URL.
Role-based access for elastic robots in AWS
Elastic robot orchestration in AWS just became more secure, by allowing the implementation of role-based autentication. Learn how to set up your AWS.
Improved identification of resource types
The improved identification of resource types, announced on July 9, 2024, is now enabled.
Error message improvement
We have improved the error messages displayed by all Orchestrator resources. The errors now include a Trace ID, where relevant, for more efficient debugging.
Bug fixes
- The package feed did not refresh when you switched folders. Versions from the previous folder remained visible until you switched between tabs.
- An error stating that the command must not be null was displayed when you attempted to update a process.
- Some fields using relative dates displayed details based on the system preferences instead of the user's language preferences.
- An error stating that the
startJobParameters
must not be null was displayed when you manually started a job from the user interface, or when you performed aStartJobs
API call. - The Log Details window previously did not display new-line characters correctly. Now, the window properly shows whitespace for all text values in logs, and its width has been increased for improved content visibility.
Applying size limits on large data fields
Progress
- limited to 104,857 charactersAnalyticsData/Analytics
- limited to 10 KBOutputData/Output
- limited to 100 KBSpecificContent/SpecificData
- limited to 500 KBProcessingException - Reason
- limited to 102,400 charactersProcessingException - Details
- limited to 102,400 characters
$top
filter is now also limited to a maximum of 100
records.
You can read more about these in Large data fields.
Removing the account authentication endpoint
api/Account/Authenticate
endpoint has been removed. We recommend
using external applications and personal access tokens instead.
Find out more about external applications.
New options on the Processes page
The Processes page now includes two new options: View Logs and View Jobs. The options allow you to easily access the logs and jobs associated to a specific process.
Launching the Orchestrator Credentials Proxy 2.1.1
- The error message displayed when you tried to use an encrypted
appsettings.Production.json
, which stated that a file or assembly could not be loaded, no longer occurs. - The BeyondTrust Password Safe - Team Passwords credential store would sometimes
not work as expected when the
Folder Path Prefix
parameter was used.
We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.
- September 2024
- September 25, 2024
- Side panel layout updates
- September 23, 2024
- Changes to the count parameter
- September 17, 2024
- Role-based access for elastic robots in AWS
- September 16, 2024
- Improved identification of resource types
- Error message improvement
- Bug fixes
- September 5, 2024
- Applying size limits on large data fields
- September 4, 2024
- Removing the account authentication endpoint
- New options on the Processes page
- September 3, 2024
- Launching the Orchestrator Credentials Proxy 2.1.1
- Deprecation timeline