A maintenance release for Flux 7.4 is now available and includes one improvement and several bug fixes.
Flux 7.4.5 downloads are available here:
my.fluxcorp.com (for Flux customers)
The latest version of Flux is available from:
www.fluxcorp.com/download (for Flux evaluators)
The following maintenance changes were made in this Flux maintenance release, version 7.4.5.
Improvements:
1. Flow charts names are now case-sensitive in order to reduce database
deadlocks. WARNING: This could have a negative impact on your
application. Please test and make appropriate changes.
Bug Fixes:
1. A NullPointerException could occur when attempting to register an
agent with an engine that did not have cluster networking enabled.
Fixed.
2. When using a secure Flux engine, clicking a flow chart in the flow
charts grid of the Operations Console would produce a JavaScript error.
Fixed.
3. Sub flow charts were being displayed as separate flow charts inside the flow charts page of the Operations Console. Fixed.
4. Controls for pausing, stopping, resuming, etc. were not available
for engines in the engines page of the Operations Console on initial
load. Fixed.
5. In the Operations Console flow charts page, flow chart action
buttons were enabled for sub flow chart actions, even though Flux does
not support flow chart actions on sub flow charts. Fixed.
6. The "RESULT.result" flow context variable was case-sensitive when
set as the condition on a customized conditional flow from a Business
Process Trigger. Fixed.
7. Confirming a Business Process Trigger on a stopped engine would result in a NullPointerException. Fixed.
8. In the Operation Console's engines page, a NullPointerException
could occur when viewing multiple engines bound to the same RMI
registry using separate bind names. Fixed.
9. The indicator for the currently executing action in the real time
monitor of the Operations Console failed to stop when the action
stopped execution. Fixed.
10. Select inputs on the Reports page would show through the Report
Details pane of the Operations Console in Internet Explorer 6. Fixed.
11. Pre scripts were only executed once per trigger, instead of once per trigger for each flow context. Fixed.
12. If a sub flow chart failed, the parent flow chart was not able to
be recovered through the Operations Console's flow charts page. Fixed.
13. The Operations Console's flow charts page displayed an unlimited
number of flow charts, causing performance issues. The flow charts page
is now limited to 500. Fixed.
14. The start of run property was dynamically set on the start action
of a flow chart by Flux, even if the end of run action could not be
determined. Fixed.
15. Engine status icons in the engines grid of the Operations Console's
engines page were sometimes displaying incorrect states. Fixed.
16. An IllegalAccessError could occur when clustering was enabled. Fixed.
17. Certain engines were not being displayed on the engines page of the Operations Console. Fixed.
18. The Flux engine could become blocked and cease processing jobs under heavy load. Fixed.
19. When using multiple Simple File Target Criterias with a File Move
Action, the source files would not be moved to all but the first target
criteria. Fixed.
