New Features and Release Notes

Download the Flux 7.11 GA

Flux 7.11 Supports These New Features




Cognos Orchestration

Orchestrate files from FTP servers and the file system into position and then launch a Cognos report, all from within Flux.


From the Operations Console, copy configurations and flow charts between Flux development, QA, and production instances.

Engine and Agent Configuration Editor

Create and edit engine and agent configurations in the Operations Console.

Fine-grained Operations Console Privileges

Create various small privileges (permissions) to govern what tasks an Operations Staff can perform while working with the Operations Console. For example, there are privileges to allow a flow chart to be removed and to stop an engine. Other privileges include the ability to hide a tab in the Operations Console from users. For example, you can hide Designer tab from unprivileged users, if desired.

Engine and Agent Configuration Reloading

Engine and agent configurations can be reloaded on the fly. Allows engines and agents to restart with updated configurations, all from the Operations Console.

Restart Flow Charts

Running flow charts can be restarted from their initial state.

Variable Substitution More Powerful

Flux's variable substitution capabilities have been augmented to allow access to properties and methods in variables at runtime. For example, in Flux 7.10 using variable substitution, the email body of a Mail Action can access variables in the flow context action, the mail action, and the enclosing flow chart. However, you can't access properties or call methods on those variables. However, starting with Flux 7.11, you can. This greatly simplifies different situations when trying to access flow chart information at runtime.

The new variable substitution capabilities also allow for very expressive capabilities such as looping and iterating over collections, etc).


A RESTful Web service API to the Operations Console is available, which allows you to send requests to the cluster of Flux engines as a whole, without needing to reference a particular engine.

Multi-tasking Agents

Agents can run multiple tasks simultaneously.

Engine and Agent Configuration Names and Descriptions

Engine and agent configurations both can be configured with a descriptive name and a human-readable description. For example, an engine configuration may be named "For QA" and the description may read "For the QA machines in the server room". The Operations Console uses this name and description on the Repository tab and in the engine and agent dialogs from the homepage of the Operations Console. As part of this change, the engine configuration property NAME was renamed to ID_NAME. Two new engine and agent configuration properties were created: ID_FULL_NAME (the descriptive name) and ID_DESCRIPTION (human-readable description). The property ID_FULL_NAME does not need to be set, but if a configuration is uploaded to the repository without having ID_FULL_NAME set on it, a unique name will be generated automatically. Unique names for engine configurations follow the pattern "Engine Configuration 1", "Engine Configuration 2", etc. Similarly, unique names for agent configurations follow a similar pattern: "Agent Configuration 1", "Agent Configuration 2", etc.

License Info

License information in shown in the Operations Console.

Flux Messaging Removed

Flux Messaging has been removed in favor of using Flow Chart Trigger, Flow Chart Action, and Audit Trail Trigger, which perform and scale much better than Flux Messaging. For users who rely on JMS, JMS remains a strategic fit within Flux. Optionally and at the user's discretion, Flux will continue to integrate with JMS messaging systems.

Simpler LDAP Configuration

LDAP integration for retrieving usernames and passwords from an LDAP server is much simpler to configure and debug.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.