The Flux 7.10.3 maintenance release is now available! This release includes 3 improvements and 41 bug fixes.

Flux 7.10.3 is a drop-in replacement for any Flux 7.10.x version.

Improvements

• File transfer speed and performance are improved, and the file transfer buffer size has been increased from 8k to 50k.
• Expediting a flow chart now displays a confirmation dialog that allows users to see the total number of triggers that were expedited.
• The “Message Type” property of the JMS Action can now be edited in the Web-based Designer.

Bug Fixes

• The error message Warning: Unresponsive Script no longer appears after viewing the Flow Charts page of the Operations Console for a significant amount of time. Additionally, memory usage in the browser no longer grows unbounded while viewing the Flow Charts page for a significant amount of time.
• Runtime substitution now works correctly for namespaces that are more than one level below the root.
• The Database Stored Procedure Action property “Parameters” can now be set and viewed in the Web-based Designer.
• Flow charts no longer run out of priority order if one flow chart is finishing execution, a high-priority flow chart has a namespace with a lower alphanumeric value than the finishing flow chart, and a lower-priority flow chart has a namespace with a higher alphanumeric value than the finishing flow chart.

• The Operations Console now correctly returns to the home page if a connected engine becomes available while the “All Engines Unreachable” dialog is displayed.
• The Operations Console now correctly returns to the home page after adding a new engine from the “All Engines Unreachable” dialog.
• Broken images no longer appear in the Web-based Designer when using Google Chrome.
• The error Cannot read property ‘fluxAction’ of undefined no longer appears when adding a runtime data map to an action in the Web-based Designer using Google Chrome.
• Triggers and actions no longer become deselected after double-clicking them in the Web-based Designer when using Google Chrome.
• In the Web-based Designer, editing the “Timeout Expression” property on an action no longer causes the error Cannot call method ‘setAttribute’ of null to appear in the browser.
• The error Cannot execute [object Object]: Util.selectSinglenode[result[i] “map-value/value /text ()”) is null no longer appears when editing Flow Chart Actions in the Web-based Designer.
• The error java.lang.NullPointerException no longer appears if a JMS Inbound Configuration fails to register with the engine on engine startup.
• The engine now correctly recovers and connects to a database if the database was not available when the engine started, but the database becomes available later.
• The error com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name ‘SYSOBJECTS’ no longer occurs when using a SQL Server database with binary collation.
• Adding a new user in the Operations Console no longer fails with a browser error in Internet Explorer 8.
• The Web-based Designer no longer displays an error message if the domain or username is empty on a UNC host.
• If a File Exist Trigger has a stable period, and there are enough files located to satisfy a minimum count on an include but not enough stable files, the trigger will now correctly wait for all of the files to become stable instead of firing immediately.
• The Operations Console now correctly displays long engine and agent host names.
• Java API: The getActionHistory(String flowChartName, String actionName) method no longer throws a ClassCastException when calling next() on the ActionHistoryIterator object.
• Java API: The getActionHistory() methods no longer throw an EngineException when calling next() on the ActionHistoryIterator object for engines configured to use the H2 database.
• The Operations Console flow charts grid now correctly displays running flow charts that contain splits.
• When using LDAP in “group search mode”, special characters in group DNs no longer cause the login to fail with an error.
• The message column in the flow charts grid now correctly shows the status message set in the flow context.
• Using a Zip File Criteria in a File Action with no renamer no longer encounters an error during execution.
• Passwords are now correctly encoded in the URL property of FileInfo results for file triggers and actions, allowing them to be successfully used in runtime data maps.
• The REST Action property “Request Entity String” can now be edited in the Web-based Designer.
• The Flow Chart Action property “overwrite” can now be edited in the Web-based Designer.
• Flow Chart Actions no longer encounter the error message “You must be logged in to call this method” when LDAP security is enabled on the engine.
• The Web-based Designer no longer displays an error when attempting to edit an action’s properties that contain a file criteria in a copied flow chart.
• The error flux.EngineException: Unable to load flow chart from file: null no longer appears when running a Flow Chart Action when LDAP security is enabled on the engine.
• Java API: The getFlowChartElements(String namespace, SuperState superState, Set<SubState> subStates, String engineName, String actionName, String messageFilter) method now correctly returns results when filtered with SubState.ANY.
• Specifying a base directory of ‘./’ for an FTP, SFTP, or FTPS host type now instructs Flux to operate from the connected user’s home directory instead of the user’s root directory.
• When installing Flux, the flux Operations Console (flux.war) is now generated correctly if the system uses a JRE rather than a JDK.
• Flow charts are now correctly, alphanumerically sorted in the Operation Console’s repository page.
• The Audit Trail Trigger now correctly moves forward to fire on newer entries (the trigger no longer becomes stuck firing repeatedly on the first audit trail entry it finds).
• Flow Chart Actions no longer fail to run if security is enabled on the Flux engine.
• The Operations Console flow charts grid now correctly displays namespaces that contain digits.
• The JMS Action “body” property now correctly saves when edited from the Desktop Designer.
• In the Operations Console, the filter for the Audit Trail page no longer displays an invalid “deadline exceeding” event.
• The encryption type of an FTPS host now saves properly when using the Desktop Designer.