Skip to end of metadata
Go to start of metadata

Flux continues to extend its workflow and managed file transfer technology in 2019. Building on its unique architecture that runs embedded in Java applications or as a standalone application, Flux is adding the following in 2019, listed in no particular order. 

  • Support for Java 8 Open JDKs.
  • Support for Java 11, both Oracle and Open JDK versions.
  • Rework of Flux's web services to make Flux more portable across application servers as well as improve its performance.
  • Improvements to the Flux scheduling engine itself to improve scalability and overall performance.
  • Improvements to agent processing to provide more scalability and better visibility into agent processes.
  • Add a File Read Action and a File Write Action. Also support reading and writing CSV files.
  • Allow workflow designs to have comments text placed on the canvas.
  • Allow predefined values to be stored in the Flux runtime configuration for commonly used workflow values. Instead of having to enter repeatedly used values into Flux dialogs,  Flux will fetch these values in the runtime configuration file allowing one to pick values from dropdowns.
    • Flux scripts (prescripts and postscripts)
    • Timer trigger definitions
    • Database definitions
    • Web service definitions
    • File selection criteria and process definitions
    • File definitions (i.e., expanded file pattern information), such as file name layout, minimum size, maximum size, maximum age, allow duplicates within hour, day, week, never, always
  • Add a runbook view to Cockpit - what's run today, what's going to run, how long have workflows run against averages
  • Accumulated CPU and memory statistics for Engine view
  • Add a chart tab to Cockpit to depict current engine and cluster state graphically.
  • The ability to interactively debug workflows.
  • Improved notification support for a workflow and its actions running too long, too short, too often, or not often enough.
  • More sample workflows and reports.
  • Add support for event-based file change notification into file triggers while continuing support for legacy polling model.

Have a suggestion? Send your ideas to

  • No labels