All updates are cumulative of all prior updates. Updates are distributed as zip files. Follow these directions to apply the update. To upgrade to Flux 8.1, you must be using an 8.0.13 release.
- Shut down any Flux engine and Operations Console instances that are running.
- Download and extract the new Flux version to your system. Download the .zip version of the release from support.flux.ly.
- Unzip the downloaded zip file to a temporary directory.
- Delete the flux directory inside the
- Copy the flux.jar and flux.war files from the new release over your existing ones (i.e.,
/flux.jar and /webapp/flux.war).
- Copy the lib directory from the temporary directory into
- Copy the .sh files from the new release over to your existing one.
- Delete “log4j-1.2.5.jar” from the lib folder.
- Ensure your Flux 8.1 license key file is in the Flux directory.
- Run the configure.sh script.
- Restart your engines and web application.
After installing Flux, you can optionally enable the real-time Flux Log File Viewer by adding the following entries to the opsconsole8.properties file located in the
That’s it! Your new Flux version is now installed and ready to run.
Note: Flux 8.1 requires a JDK, not just a JRE.
- Flux 8.1 supports log4j version 2.17.1, which patches recent security vulnerabilities including CVE-2021-44228. Previous versions of Flux use log4j version 1.x and therefore are NOT vulnerable to this exploit.
- Flux 8.1 supports Java JDK 8, 9, 10, and 11.
- Engine.getFlowChartElements() returned no more than 100 results, regardless of the number of flow charts in the engine. Fixed. All flow chart elements are now returned correctly.
- A few files in the
fluxpackage did not belong there. They have been removed.
- Flow Chart Action continued to the next action when its child workflow entered the FAILED state, as though the child workflow completed. Now, in accordance with its Javadoc documentation, Flow Chart Action correctly blocks until the child workflow completes. By “completes”, that means the workflow runs to completion and is no longer on the engine. (This assumes the Flow Chart Action is running synchronously.)
- Flow Chart Action Asynchronous behavior defaulted to true, which was not in accordance with the Javadoc documentation for Flow Chart Action. Flow Chart Action’s default Asynchronous behavior meant this workflow action did not wait for the newly spun off workflow to finish running before this workflow action completes. Flow Chart Action Asynchronous behavior now defaults to false (in accordance with the docs), which means this workflow action waits for the newly spun off workflow to finish running before this workflow action completes.
Flux 8.1.2 is a drop-in replacement for Flux 8.1.1 and 8.1.0.
Before upgrading, ensure your workflows do not rely on the previous incorrect behavior.
- The PGP keys under the System tab now renders up to 100 keys instead of 10.
- The method flux.file.IncludesFileCriteria include(String filePattern) now defaults the file minimum count to 1 instead of 0, which caused the triggers to fire prematurely.
- Deprecated method flux.file.FileTrigger.setActiveWindow is now officially removed.
Flux 8.1.3 is NOT “drop-in” replacement IF-AND-ONLY-IF you use the flux.file.FileTrigger.setActiveWindow() method, which is deleted as of this maintenance release.