orchestrator
latest
false
- 发行说明
2024 年 9 月
Orchestrator 发行说明
Last updated 2024年9月17日
2024 年 9 月
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
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.
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
- 限制为 104,857 个字符AnalyticsData/Analytics
- 限制为 10 KBOutputData/Output
- 限制为 100 KBSpecificContent/SpecificData
- 限制为 500 KBProcessingException - Reason
- 限制为 102,400 个字符ProcessingException - Details
- 限制为 102,400 个字符
Additionally, the
$top
filter is now also limited to a maximum of 100 records.
您可以在大数据字段中阅读有关这些内容的更多信息。
api/Account/Authenticate
端点已删除。 我们建议改用外部应用程序和个人访问令牌。
详细了解外部应用程序。