Complete feature and improvement details for FrameworX 10.1 Update 5e, organized by product area.

Release Notes → Update 5e → Update 5e - Detailed Release Notes

FrameworX 10.1 Update 5e — August 31, 2026

Build: 2107

HTML5 and web client

• Faster HTML5 client startup and lower latency for remote clients — the connection sequence runs its steps in parallel, the browser opens its communication channel while the page loads, and repeated round trips were removed from the startup path.
• Server responses reach remote clients in a single network round trip, improving the responsiveness of displays, trends, and reports over remote connections.
• Upgrades stay compatible with servers and clients from earlier 10.1.5 updates.
• Combobox is populated on first load in HTML5.
• Icons and images stay in place on the HTML5 client after a reload.
• Symbol Rotate animations no longer accumulate memory in the client.

Alarms, Historian and redundancy

• The active server’s runtime process stays bounded under alarm-history load on a redundant pair — a new TServer.json key, Alarm.HistoryQueryMaxRows (default 100000), sets a server-side ceiling on how many alarm-history rows a single query may load. A query above the ceiling succeeds and returns the newest rows up to it, with a warning naming the requested count, the applied ceiling, and the configuration key.
• Redundancy settings are applied when the runtime auto-starts as a Windows service after a computer restart — the runtime reads the machine’s network addresses correctly during early Windows startup, and any remaining network-timing condition is reported in the Windows Event Log instead of being silently ignored. A new optional /redundancywaittimeout:<seconds> TStartup argument waits for the network stack on machines where the network comes up slowly (default: no wait).
• Alarm History, Trend Chart, and Drilling Chart no longer fail with a SQL syntax error on branded builds.
• Documented safe automatic-failback practices and /TimeAutoSwitch tuning — automatic failback to the original primary does not pull back data the secondary accumulated while the primary was down; only a manual SwitchToStandBy triggers that reconciliation.
• See Breaking Changes and Deprecations below for the withdrawal of the handover replication drain barrier.

Unified Namespace, ontology and knowledge graph

• Ontology import reports what it actually created, not what it planned to create.
• The same ontology property produces the same member name across UserTypes.
• Ontology import keeps a class as a class instead of converting it into an Enumeration when its objects carry only a type and a name — relationships pointing at those objects are preserved.
• Ontology import resolves a relationship to an object that is not declared in the file instead of silently storing it as plain text.
• Knowledge Graph export produces HTML that renders in Firefox.
• The exported Markdown knowledge-graph diagram renders instance-of relationships.
• The exported knowledge-graph visual refers to UserTypes by their product name, not “UDTs”.

Displays and Symbols

• Display parameters used as part of a larger value track live values again — a parameter combined with a comparison, a second condition, or any surrounding expression previously compiled without complaint and then stayed frozen at runtime. A button configured to stay disabled while a condition holds now disables as configured. Applies to displays opened as pages and as popups. Known limitation: a dynamic inside a Symbol on a parameterized display is handled by separate rules and still reproduces the original behavior.
• Display geometry survives the import/export round trip across four separate paths.
• Custom symbols are preserved when migrating a solution from FrameworX 10.1.4 to 10.1.5.
• Popup displays imported with a fixed custom position keep that position.
• Dynamics Get/Apply keeps the theme binding on transferred colors (LineColor, FillColor, and others).
• The Asset Tree control no longer raises an exception in the Rich Client when Localize is enabled.
• Colors driven by an Enumeration resolve correctly.

AI, MCP and automation

• Re-importing a file or solution over existing content updates the existing objects instead of silently skipping them.
• The LinearGauge label, tick, and scale-bar colors are exposed on the JSON / MCP write path, so gauges authored from automation can match a legacy HMI palette.
• TK.PreloadObject preserves the object name’s letter case.

Designer and data

• Import Solution brings Templates and Tags in correctly — no unprefixed extra Templates, and the tags are not dropped.
• Dataset Table inserts respect SQL Server DEFAULT values on unmapped columns instead of overwriting them with NULL.
• Alphabetical sort is available as soon as the Enumerations, UserTypes, Layouts, Localization, and Units Conversion pages open.
• Import Tags Wizard loads the Solution list on the Solution selection row.

Devices and protocols

• Modbus master reads device identification data using function code 43 (Read Device Identification).

Runtime and platform

• Clients that connect while the runtime is still starting come up licensed on a correctly licensed machine.
• AutoStartClient detects a Rich Client that is already running instead of opening another window.
• A runtime running as a Windows Service no longer starts the Run Tools (TraceWindow, PropertyWatch) as hidden background processes.
• Large array and matrix tags populate immediately when a Display opens.

Mobile client

• The Settings screen connection fields are readable when the device is in Light mode.

Security and access

• A logon is refused when the server’s user check fails internally — a failure part-way through the check was previously reported as a successful check and the client was allowed to connect. The refusal is reported to the client and recorded in the audit trail when remote-connection auditing is enabled. A normal logon is unaffected, and a wrong user name or password still returns the same specific reason as before.
• Stored credential values can no longer be read or overwritten by the AI tools through the Designer grid cell edit action — passwords, API keys, tokens, and database logon passwords. Reading a protected column is refused instead of returning the stored value, and writing one is refused outright. Credentials continue to be set through the Designer security screens as before, and ordinary non-credential grid cells are unaffected.
• A security guard built on a parameterized display disables as configured — see Displays and Symbols above.

Breaking Changes and Deprecations

The handover replication drain barrier has been withdrawn. Alarm and Historian replication behavior around a redundant-pair handover is unchanged from 10.1.5c. The change introduced in Update 5d, which held a handover open until Alarm and Tag Historian replication finished draining, has been withdrawn together with its SwitchDrainTimeoutSeconds configuration key. A configuration file that still contains that key is accepted and the key is ignored. Rows recorded on the active node in the moments immediately before a handover may therefore not reach the other node.

On redundant pairs started with /autoswitch, use the existing /TimeAutoSwitch:<seconds> startup argument (default 60) to give replication time to finish before the restarting Primary reclaims the Active role. Increase it beyond the default for large Solutions, slow networks, or high alarm and data-logging rates.

Lifecycle and Support

Update 5e ships on August 31, 2026 as a free upgrade for every FrameworX 10.x customer, with the platform’s standard within-major-version 100% compatibility commitment. See Breaking Changes and Deprecations above for a redundancy behavior change that may require a startup-argument adjustment on affected installations.

Security note

This release contains security-relevant corrections. Upgrading is recommended for all installations.

One item requires action beyond upgrading: if you used the AI or MCP tooling against solutions that hold stored passwords, API keys, or database logon credentials on 10.1.5d or earlier, rotate those credentials.

Customers who need per-item detail — affected versions, severity, and required action — for patch management or supplier-assurance purposes can request it from support@tatsoft.com, along with the component manifest (CycloneDX) for the version they are running.