Release r202614
This release contains no new features, but does include one important update that we want to share with you.
Important updates
Consolidating our instances into one
The automator production environment currently consists of four separate instances:
automatorautomator-btautomator-euautomation
To reduce operational complexity and cost, we have decided to consolidate these into a single instance.
Over the coming weeks, the automator, automator-bt and automator-eu
instances will merged into the automation instance. The schedule is:
| Date | Event |
|---|---|
| Tuesday, June 9th | Merge automator into automation |
| Tuesday, June 16th | Merge automator-bt into automation |
| Tuesday, June 30th | Merge automator-eu into automation |
What this means for you:
-
No URL changes required. All existing hostnames (
automator.techwork.at,automator-bt.techwork.at,automator-eu.techwork.at,automation.techwork.atandautomator.at) remain active and continue to work. Webhook URLs registered in external systems do not need to be updated. -
All profile data is preserved and migrated to the target instance.
-
During the merge of each instance profiles will be temporarily set to read-only (= maintenance mode). We expect a merge itself to only take a couple of minutes, after which the maintenance mode is disabled again.
-
During the merge:
- Execution of packages, processing of inbound email and processing of schedules will be paused on the source instance. In-flight package executions are allowed to finish. Any package executions that are still queued when the merge starts will be carried over to the target instance and continue running there.
- Webhook endpoints continue to be responsive, but inbound events will be queued. These queued events will also be carried over to the target instance to be processed there.
- The service and file repository endpoints will continue to work.
-
Users of
automator-btwill prompted to set up MFA when logging in for the first time after their instance has merged intoautomation.
The merges will be performed outside of office hours (Central European Time Zone), between 8pm and 10pm.
If you have any questions about this change, please reach out to us by registering a support request in Xurrent.
Other changes
This release contains a number of smaller changes:
-
A number of base functions have been deprecated in favour of their modern JavaScript equivalents. The functions still work, but the documentation now recommends using the native alternatives instead:
Deprecated function Recommended alternative assignObject.assignor spread syntaxcheckNull??(nullish coalescing) or||getPropertybracket notation obj[name]setPropertybracket notation obj[name] = valueisArrayArray.isArrayisNullvalue == nulljointemplate literals or Array.joinpathJoinarray.map(...).join(...) -
Fix: in certain cases the package editor UI could freeze when hovering over the search box in the editor. The tooltip positioning logic that caused this has been improved to avoid this.
-
Fix: opening a package whose name contained a
:character could cause the package editor to crash (resulting in a blank screen). Such package names are now handled correctly. -
Fix: navigating to a Find in packages search result will now always switch to the script tab of that package.
-
Fix: code completion for the Xurrent audit lines endpoint was registered under the name
audit, which did not match the actual endpoint. It has been corrected toaudit_lines. -
Update: the Xurrent REST and GraphQL model metadata has been refreshed to include all field changes between May 2 and May 23, 2026. This affects code completion and field documentation for the corresponding endpoints.
Timeline
The expected deployment dates for this release are:
| Environment | Date |
|---|---|
| Demo | Friday, June 5th |
| Production (automator, automation) | Monday, June 8th |
| Production (automator-eu, automator-bt) | Thursday, June 11th |
The deployment of the Production environments will be conducted outside of office hours (Central European Time Zone), usually between 8 and 10pm.