A maintenance release for Flux 7.6 is now available and includes one improvement and several bug fixes.

Flux 7.6.3 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.6.3.

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. The Flux engine could become blocked and cease processing jobs under heavy load. Fixed.

2. The "filenames" and "url_objects" properties of file action result
objects were cleared before the next action's execution when retrieving
the result object from a file action that contained multiple outgoing
flows. Fixed.

3. An SQLException occurred when scanning the audit trail with an engine configured to use a DB2 database. Fixed.

4. An EngineExcpetion would occur when using the Flux Command Line
Interface's "dispose" argument from the "client" command when the
configured database's driver, of the given properties file, was not
located on the class path. Fixed.

5. The DesignerConfiguration.setPassword() function was not documented in the JSDoc documentation. Fixed.

6. Controls for pausing, stopping, resuming, etc. were not available
for engines in the engines page in the Operations Console on initial
load. Fixed.

7. Confirming a Business Process Trigger on a stopped engine would result in a NullPointerException. Fixed.

8. All engines running in the same JVM logged to the same log file. Fixed.

9. An XML error was displayed to the engine console when using an unsupported XML parser. Fixed.

10. Icons indicating the state of engines in the engines page of the Operations Console were sometimes incorrect. Fixed.

11. A JavaScript error could occur when clicking on a flow chart in the
flow charts page of the Operations Console when using a secure engine.
Fixed.

12. Using a Simple File Target on a File Move or File Copy Action would not work properly. Fixed.

13. JavaScript exceptions occurred when embedding the Web-based Designer as a JavaScript widget. Fixed.

14. The source files were only moved to the first target criteria when
using multiple Simple File Target Criteria with a File Move Action.
Fixed.

15. A NullPointerException could occur when removing a running sub flow chart. Fixed.

16. An error was displayed when right clicking on a file action in the Web-based Designer. Fixed.

17. A ClassCastException occurred when editing action variables in the Web-based Designer. Fixed.

18. Process Action properties were not displayed in the Web-based Designer. Fixed.