Online License Update for RUNTIME Definitions
FlowHeater RUNTIME Definitions created with RUNTIME Designer run at the customer’s site without requiring additional license activation. These RUNTIME definitions can still be modified by your customers, albeit with certain restrictions. However, if a customer is using a newer version for which they no longer have update authorization, a new RUNTIME definition previously had to be distributed to the customer. With this version, it is now possible to search online for a new or updated license in order to update the affected RUNTIME definition.
Release notes for version 4.5.5 dated June 20, 2026
Creating RUNTIME Definitions with the 30-Day Trial Version
To test RUNTIME definitions without a license, you can now use the 30-day trial version. The RUNTIME definitions created in this way are valid for as long as the 30-day trial version is valid. Once the trial period expires, the RUNTIME definitions created in this way can no longer be used.
FlowHeater Server – Running the Current Version
Previously, with each FlowHeater Server version, a separate directory was created under “...\Versions\[x86|x64]\” containing that specific version for batch execution. This version was then used to run a FlowHeater definition with that exact version. This approach resulted in additional version folders being created with every update, most of which were not needed at all.
With this version, only a single “Current” directory is created for the current version and processor architecture, in which the respective version is overwritten with every update. This version is now used for execution, unless there is exactly one version in the “Versions” directory that was used to originally create the definition.
So, if a backward compatibility issue ever arises, you can manually download the corresponding standard FlowHeater version from the download archive and copy it to the appropriate version directory on the server.
Corrections (bug fixes)
- FlowHeater Server: Under heavy load, the execution history might not have been written to properly. Although all tasks were processed correctly, it was not possible to perform a subsequent check of these “incorrectly logged” tasks.
