orchestrator
latest
false
- Release notes
Orchestrator Release Notes
Last updated Sep 17, 2024
September 2024
Elastic robot orchestration in AWS just became more secure, by allowing the implementation of role-based autentication. Learn how to set up your AWS.
The improved identification of resource types, announced on July 9, 2024, is now enabled.
We have improved the error messages displayed by all Orchestrator resources. The errors now include a Trace ID, where relevant, for more efficient debugging.
- 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
startJobParametersmust not be null was displayed when you manually started a job from the user interface, or when you performed aStartJobsAPI 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.
Starting today, we are rolling out size limits on large data fields to Enterprise
tenants. The change will gradually go into effect over the course of a week. These are
the new limits:
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
Additionally, the
$top filter is now also limited to a maximum of 100
records.
You can read more about these in Large data fields.
The
api/Account/Authenticate endpoint has been removed. We recommend
using external applications and personal access tokens instead.
Find out more about external applications.
The release of the Orchestrator Credentials Proxy 2.1.1 brings two important fixes:
- 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 Prefixparameter was used.
- 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
