A maintenance release for Flux 7.7 is now available and includes four improvements and several bug fixes.

Flux 7.7.6 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.7.6.

Improvements:

1. (FLUX-463) Made the default engine bind name for the Desktop Designer configurable via a Java properties file.
2. (FLUX-371) Added support for loading resources from JAR files located in the flow chart's listener class path.
3. (FLUX-492) Added a configuration option to remove the "remember me" check box when signing into an engine in the Operations Console.

1. (FLUX-461) If the file_transfer_debug configuration option was set to true and a Secure FTP host was used, the expected debug output would not be generated. Fixed.
2. (FLUX-430) If a File Not Exist Trigger criteria include used variable substitution and the file limit was set to a value greater than zero, a ClassCastException would occur. Fixed.
3. (FLUX-457) Transferring files using a Secure FTP host did not work correctly with some Secure FTP servers. Fixed.
4. (FLUX-454) Cluster networking utilized the User Datagram Protocol (UDP) when configured to use the Transfer Control Protocol (TCP). Fixed.
5. (FLUX-203) If a flow chart was resubmitted to the engine soon after completing execution, an EngineException would occur. Fixed.
6. (FLUX-495) Agents registered to an engine would fail to re-register if the engine was restarted. Fixed.
7. (FLUX-343) The SQLException was not logged when Flux obtained an invalid database connection. Fixed.
8. (FLUX-496) When running Flux against Sun JDK 6, cluster networking did not work correctly and the log displayed the error message "Unable to initalize the Flux network cache". Fixed.
9. (FLUX-486) If an agent encountered an error while running a Process Action, a NullPointerException could be thrown. Fixed.

A maintenance release for Flux 7.7 is now available and includes four improvements and several bug fixes.

Flux 7.7.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.7.5.

Improvements:

1. Improved file actions and triggers to allow periods in base directories.
2. Added support for string-to-string maps in the Web-based Designer.
3. Added support for Firefox 3 in the Web-based Designer.
4. Added support for configuring the default project name and copyright string in the Desktop Designer.

1. A ClassCastException occurred when running a File Delete Action with an FTP host specified. Fixed.
2. An exception occurred when attempting to search the reporting logs in the Operations Console. Fixed.
3. An error occurred when attempting to save a flow chart to the local drive from the repository in the Operations Console. Fixed.
4. Using the guided flow chart rescheduled in the Operations Console could cause an error. Fixed.
5. A SQLException occurred when calling Engine.getLongestRuntime(). Fixed.
6. The File Rename Action was not working properly when using a remote host with a file path specified for the file criteria target. Fixed.
7. Flow charts containing string maps could not be saved from the desktop or Web-based Designer. Fixed.
8. If a File Action used an FTP, SFTP, or FTPS host and the target file was already present, the source file would be copied to the base directory of the target host. Fixed.

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

Flux 7.5.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.5.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.

1. The Flux engine could become blocked and cease processing jobs under a heavy load. Fixed.
2. Confirming a Business Process Trigger on a stopped engine would result in a NullPointerException. Fixed.
3. All engines running in the same JVM logged to the same log file. Fixed.
4. Using an unsupported XML parser would display XML errors to the engine console. Fixed.
5. Icons indicating the state of engines in the engines page of the Operations Console were sometimes incorrect. Fixed.
6. Clicking a flow chart in the flow charts page of the Operations Console
   could cause a JavaScript error when using a secure engine. Fixed.
7. A File Move Action using multiple Simple File Target Criteria would only move files to the first target criteria. Fixed.
8. Running a flow chart with a checkpoint (a flow that publishes messages)
   could cause a message iterator to close prematurely. Fixed.
9. JavaScript exceptions occurred when embedding the Web-based Designer as a JavaScript widget. Fixed.
10. A NullPointerException could occur when removing a running sub flow chart. Fixed.
11. A ClassCastException occurred when editing action variables in the Web-based Designer. Fixed.
12. An EngineException occurred when running the software developer's security example. Fixed.
13. Regular expression special characters were not allowed inside variable values when using substitution. Fixed.
14. A NullPointerException occurred when attempting to access the
    Web-based Workflow Designer of the Operations Console on an engine
    configured to use external security. Fixed.
15. A NullPointerException occurred when accessing the security page of the
    Operations Console on an engine configured to use external security.
    Fixed.
16. When using a UNC file host, regular expression excludes were not working properly. Fixed.
17. An exception occurred when using a Process Action in a sub flow chart with an agent pool defined. Fixed.

Recent Flux Customer: Internet Broadcasting Systems

A maintenance release for Flux 7.7 is now available and includes two improvements and several bug fixes.

Flux 7.7.2 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.7.2.

Improvements:

1. Added support for designing flow charts that utilize signals in the
   Web-based Designer.
2. 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. Database deadlocks could occur when running a heavy load in a clustered
   scenario using DB2, MySQL, or SQL Server 2005 databases. Fixed.
2. The variable editor would not display correctly after loading a flow chart
   from the repository. Fixed.
3. A ClassCastException could occur when using a File Exist Trigger after
   upgrading from previous releases. Fixed.
4. When using the database exception action, verification of the JDBC, or JNDI,
   action properties failed. Fixed.
5. An EngineException occurred when running the software developer's security
   example. Fixed.
6. An error was displayed when right clicking on a file action in the Web-based
   Designer. Fixed.
7. A ClassCastException occurred when editing action variables in the Web-based
   Designer. Fixed.
8. Process Action properties were not displayed in the Web-based Designer.
   Fixed.
9. A blank page with the word "error" was displayed when attempting to edit a
   users permissions. Fixed.
10. A ClassCastException occurred when exporting a flow chart that contained a
    For Each Delimited File Action. Fixed.

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.

Recent Flux Customer: Dexia