Designer with support for multi-monitor environments
This version of the Designer includes extensive changes in the area of “Multiple Screens” environments.
The Designer now remembers the screen/monitor and the position on which it was last opened. When the Designer is restarted, it will attempt to reopen in exactly the same position. It will check whether the screen/monitor is still available. If not, the default screen/monitor will be used.
All windows/dialog boxes opened by the Designer are also opened on the currently active screen/monitor.
Note: The same mechanisms have been implemented in FlowHeater Server Manager.
Release notes for version 4.5.2 dated October 26, 2025
Old support forum articles have been archived
First, the good news: all support forum articles (including examples) are still available. However, articles that are more than two years old and have little relevance have been moved to archived categories.
Important: These “archive” categories are only available after registering/login with the forum. So if you are looking for a solution to your problem, it is best to register/login with the forum before entering your search criteria. This will give you direct access to all forum articles and the examples behind them.
Improved error analysis in Designer
If an error occurs during execution, you want to find and eliminate the error quickly. To help you locate the error even faster, Designer now displays the processing step where the error originally occurred when an error occurs during execution.
FlowHeater Server now also terminates child processes
In FlowHeater Server, long-running tasks can be terminated prematurely. Previously, only the process started by FlowHeater Server was terminated directly. If the started process had started further processes (child processes), these processes continued to run. With this version, FlowHeater Server terminates (kills) the entire process chain, including any child processes that have been started.
Corrections (bug fixes)
- Designer: Output of last processing step incorrect when aborted
- If-Then-Else Heater: Comparison with DBNULL values corrected
