As of this version FlowHeater supports the dynamic inclusion of FlowHeater Parameters from a Parameter file. The Parameter file, which needs to be in UTF-8 format, is read dynamically before each run and FlowHeater Parameters are preassigned with the values defined within it.
In the Designer, a static parameter file can be specified using “Menu ->Edit->Parameters”. The Batch Module further supports dynamic replacement of the default with the option “/ParameterFile filename”.
Any number of FlowHeater Parameters can be entered in a Parameter file. One Parameter can be assigned per line e.g. "Parameter name = value”. A detailed description of the structure of the Parameter file can be found under the Batch Module help.

modify processing stepsAs of this version, processing steps can be copied and deactivated. As copied processing steps are intermediately saved in the clipboard, processing steps can be copied from any other Definition. It is now also possible to disable warnings arising from individual processing steps.

This version introduces an automatic ODBC driver fallback for the Access Adapter if no suitable OleDB driver is found.

In times when crimeware like Emotet, ransomware trojans and other malware are causing more and more damage, in accordance with the principle "security first" we have decided to store Definitions and projects in encrypted form by default.

This version of the FlowHeater Server is enhanced with two powerful new functions that significantly improve the tracing of problems.
In the opening status tab window, the FlowHeater Server Manager now displays an alert when errors or warnings have occurred since the last opening. The alert remains until explicitly reset by the user. In addition, while the Server Manager is open the alert is dynamically updated. There are also different colors that distinguish between warnings and error messages: errors are highlighted with a red button and warnings with a yellow button. The totals of errors and warnings that have occurred are also displayed.

Furthermore, the display of history data has been extended with extensive filters and limitation criteria. It is now possible to search explicitly across all tasks, e.g. only for errors or warnings, and the search can be more precisely limited in time. This means that even errors and warnings from earlier periods can be analyzed without any problems.