Release r202617
What's new
This release contains the following new features:
Restructured AutomatorScript language documentation
The AutomatorScript documentation has been restructured into two sections:
- AutomatorScript covers the language itself: variables, flow control, functions, error handling, arrays, and the automator conveniences auto-retry and auto-fetch.
- Packages covers how to structure, trigger and test the scripts you write with the language.
The new Relation to JavaScript chapter explains how AutomatorScript relates to standard JavaScript: which syntax and built-in objects are supported, and the few places where the language deliberately deviates.
The chapter about Testing has been completely rewritten. It explains how testing fits into developing your integrations; from sandbox environments and manual test runs to fully automated test packages. It documents how to define tests, the available assertion functions, mocking external calls, and the code coverage report, along with recommendations for organizing your test packages.
Improved error reporting in package logs
This release contains several improvements that make it easier to diagnose a failing package:
- The rate limiter warning introduced in the previous release is now also shown when an outbound HTTP call has to wait for a token that is already rate limited, for example by an earlier call in a previous execution. Previously, the warning was only shown when the call itself triggered the rate limit.
- When a connection to an external system is closed because it hit the idle timeout, the resulting error message now clearly states that the connection was idle for too long. See the new Connection timeouts chapter for how this timeout works and how to avoid it.
- Errors thrown by JavaScript's built-in objects and methods used to appear in the log as an empty object, hiding what actually went wrong. The name, message and cause of these errors are now included in the package log.
Other changes
This release contains a number of smaller changes:
- Support for the legacy (v2) engine has been removed. Since the introduction of the current engine in r202601, the legacy engine was still used as a fallback to execute packages whose code contains syntax errors that are not accepted by the current engine (see the Important section of those release notes). An analysis of all production packages showed that the legacy engine is no longer used there.
Timeline
The expected deployment dates for this release are:
| Environment | Date |
|---|---|
| Demo | Friday, July 10th |
| Production | Tuesday, July 14th |
The deployment to the Production environment will be conducted outside of office hours (Central European Time Zone), usually between 8 and 10pm.