7.22.x to 7.23.0 and covers the following use cases:
- For administrators and developers: Database updates
- For administrators and developers: Full distribution update
- For administrators and developers: Bootstrap NES and AngularJS NES by HeroDevs, Inc.
- For developers: Set Variables Async API
- For developers: GraalVM Upgrade
- For developers: Spring Framework Upgrade (changes required when using Java 11)
- For developers: Quarkus 3.20 Extension Update
Database updates
Every ASEE Flow installation requires a database schema update. Check our database schema update guide for further instructions.Full distribution
This section is applicable if you installed the Full Distribution with a shared process engine. The following steps are required:- Update the ASEE Flow libraries and applications inside the application server.
- Migrate custom process applications.
$DISTRIBUTION_PATH.
Bootstrap NES and AngularJS NES by HeroDevs, Inc.
ASEE Flow 7.23 replaces the following libraries with versions of Bootstrap NES and AngularJS NES by HeroDevs, Inc.:- AngularJS (technical names:
angular,angular-animate,angular-cookies,angular-loader,angular-mocks,angular-resource,angular-route,angular-sanitize,angular-touch) - angular-ui-bootstrap
- angular-translate
- angular-moment
- Bootstrap
Set Variables Async API
Before version 7.23 (and patch version 7.22.1), the Set Variables Async API failed whenever at least one of the process instances did not exist. Starting with this ASEE Flow minor release, the behavior has changed: if any of the process instances was deleted or completed, the call will still succeed. As a consequence, the Set Variables Batch Operation will also succeed in this case. Please note that this does not apply to the Sync API, which keeps its behavior and fails if the process instance does not exist.GraalVM Upgrade
We are pleased to announce that the 7.23 release is compatible withGraalVM 21.3.x
The engine will automatically disable the system property polyglot.engine.WarnInterpreterOnly when a GraalJS script engine is used.
This adjustment ensures a smoother experience by suppressing unnecessary warnings related to interpreter-only execution in non-native GraalVM environments
which might cause confusion to our users running on non-GraalVM JDKs.
You can read more about the warnings here.
Heads-up!If you want to ensure the best performance for JS execution, you can always configure the GraalVM Compiler with your JDK of choice, or use the GraalVM JDK.More information on how to do this can be found in the official GraalVM documentation.
Spring Framework Upgrade (changes required when using Java 11)
Starting with version7.23, the camunda-engine artifact now uses Spring Framework 6 by default, replacing Spring 5 from previous releases.
Unlike previous versions, Spring Framework 6 requires Java 17 or higher. If you need to keep using Java 11, you will need to override the Spring version to keep using Spring Framework 5.