...
| Info |
|---|
Update 5f replaces Update 5e. It carries the complete content of Update 5e (August 31, 2026). If Update 5e is installed, replace it with Update 5f. No migration or rework is involved. See Upgrading from Update 5e below for the one behavior that differs between the two. |
FrameworX 10.1 Update 5f, September 9, 2026
The Update themes:
- Alarms, Historian and redundancy. Alarm history queries complete without a database syntax error on PostgreSQL, Oracle, and MySQL alarm historians and on ActionNet-branded installations. Historian data keeps replicating to the standby on large TimescaleDB databases with compression enabled. The active server's memory stays bounded under heavy alarm-history load, redundancy settings are applied when the runtime auto-starts as a Windows service after a reboot, and replication behavior around a handover is documented and tunable through
/TimeAutoSwitch. - Web client performance. HTML5 clients start faster and remote clients see lower latency, with the connection sequence running in parallel and server responses reaching the client in a single network round trip.
- Scripts. Script profiler entries are timed with a high resolution clock and every started entry is paired with a terminator, so profiler output can be used to find slow scripts and scripts that never returned.
- Ontology and knowledge graph. Ontology import reports what it actually created, resolves relationships and member names consistently, and the exported knowledge-graph visuals render correctly and use the product's own terminology.
- Displays and symbols. The Tags list, the Displays tag panel and drag and drop insertion all report and apply the same symbol mapping, including mappings inherited from a User Type. Display geometry survives the import and export round trip, custom symbols survive a 10.1.4 to 10.1.5 migration, popup displays keep a fixed custom position, and display parameters used inside a larger expression track live values again.
- Designer and data. Import Solution brings Templates and Tags in correctly, Dataset Table inserts respect SQL Server DEFAULT values on unmapped columns, and configuration pages sort alphabetically as soon as they open.
- Devices and mobile. Modbus master reads device identification data through function code 43, and the mobile client Settings screen is readable in Light mode.
- Security. OpenID Connect sign in works in solutions running on .NET Framework 4.8. A logon is refused when the server's user check fails internally, stored credentials can no longer be read or overwritten through the AI tools' grid edit path, and a security guard built on a parameterized display disables as configured.
See Update 5f - Detailed Release Notes for the complete item-by-item list.
Upgrading from Update 5e
...
- .
...
- Alarms, Historian and redundancy
...
Viewing alarm history from a Trend Chart, a Drilling Chart, or the Alarm Viewer completes without a database syntax error. This covers alarm historians on PostgreSQL, Oracle, and MySQL reached through their native connectors, and ActionNet-branded installations, where the query could previously be rejected by the database. Where the query failed, the chart kept drawing the data it already held, so the failure was easy to miss, but the alarm markers were missing or out of date and the query failed again on every refresh. The correction covers the Alarm Viewer in both Alarm History and Audit Trail modes, and applies to the rich client and the HTML5 client alike.
On a redundant pair whose history database is very large and uses TimescaleDB compression, Tag Historian data no longer stops reaching the standby node. Rows still waiting to be replicated when their portion of the database was compressed could no longer be read by the replication process. Each cycle attempted to read the whole table, exceeded the connection time limit and restarted, so the backlog never drained and no history reached the standby. Alarm replication was unaffected, because alarm rows are replicated before compression takes place. A second condition affecting Tag Historian data in normalized configuration is also corrected. A small number of rows could arrive at the standby without a tag name, and the standby rejected the entire batch, so a few unresolvable rows blocked all the remaining valid rows on every cycle. The standby now imports the rows it can resolve and reports the ones it cannot, and the active server records which tag index it could not map.
...
- . Historian data keeps replicating to the standby on large TimescaleDB databases with compression enabled. The active server's memory stays bounded under heavy alarm-history load, redundancy settings are applied when the runtime auto-starts as a Windows service after a
...
- reboot, and replication behavior around a handover is documented and tunable through
/TimeAutoSwitch.
See Update 5f - Detailed Release Notes for the complete item-by-item list
Alarm historians over ODBC or OleDb
On an alarm historian reached through an ODBC or OleDb connection, every query that separates alarm records from audit trail records is rejected by the database, so the Trend Chart and Drilling Chart show no alarm markers and the Alarm Viewer's Audit Trail view returns nothing. The Alarm Viewer's Alarm History view is affected only when Audit Trail is enabled. With Audit Trail off it works normally, and the combined Alarm History plus Audit Trail view is unaffected.
This covers Microsoft Access, Microsoft Excel and CSV files, and Oracle, MySQL, or Firebird when connected through ODBC or OleDb rather than their native connector. Alarm historians on SQL Server, SQLite, or on PostgreSQL, Oracle, and MySQL through their native connectors are not affected.
...
Web client and performance
...