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

Release NotesUpdate 5b → Update 5b - Detailed Release Notes


FrameworX 10.1 Update 5b — Released June 5, 2026

Resolved from Update 5

New Features and Enhancements

Improvements

OPC UA

ControlLogix

Bailey Driver

TraceWindow

Displays

Trend Chart

Reports

Designer

Runtime

Alarms

Scripts


FrameworX 10.1 Update 5 — Released May 26, 2026

Platform Foundation

.NET 10 (LTS) Runtime
FrameworX 10.1 Update 5 ships on .NET 10 Long-Term Support — Microsoft’s latest and most performant runtime baseline. Every server deployment, Web Contents target, and Designer Web host benefits automatically. The upgrade is handled entirely by the installer; no solution changes or manual steps are required. .NET Framework 4.8 continues to be supported for environments where it is needed.

Within-Major Compatibility
Every 10.1.x solution opens and runs on Update 5 without migration, code changes, or rework. Solution Center’s multi-version routing allows 10.1.4 and 10.1.5 installations to coexist side-by-side during phased rollouts.

Platform Reliability

Enterprise IT, Security, and Deployment

OIDC / OAuth2 Single Sign-On
FrameworX now integrates with enterprise identity providers through OIDC/OAuth2, with out-of-the-box support for Keycloak, Auth0, Microsoft Entra ID, and login.gov. Per-provider configuration dialogs, LDAP dispatch, and industry-standard JWT validation (RFC 8725) are all managed by the runtime. The SSO sign-in button on the client logon surface is available from Update 5b onward.

Runtime REST API v1.0
A new data-plane REST API (port 3101+) exposes live tag values, alarm state, historian queries, and aggregated history — purpose-built for enterprise IT integrations and partner systems. Authentication is via Bearer-GUID. Update 5b adds tag write support.

SolutionCenter API v1.0
A management-plane REST API (port 10108) covers the full solution lifecycle: solution management, file operations, license control, and machine-level administration. Secured with JWT/OIDC and documented via a published OpenAPI 3.0 specification.

Kubernetes-Native Deployment
TServer and TWebServices expose /health and /ready HTTP endpoints fully compatible with Kubernetes liveness and readiness probes, making container-native and cloud-hosted FrameworX deployments first-class citizens.

PowerShell and CLI Tooling

Security

Historian, Alarms, and Runtime Stability

Historian — Full Nested Path Support
Historian can now be enabled for tags in any AssetTree subfolder structure with full path fidelity. When enabled via Tag Properties, the complete qualified path (e.g. Folder1/Folder2/Tag) is stored and used for history retrieval — ensuring that deeply nested assets are historised, queried, and displayed with complete accuracy.

Upgrade note: Tags previously enabled with a leaf-only name will appear as “not enabled” when Tag Properties is reopened on Update 5. Re-enabling via Tag Properties registers the correct full path. Existing historical data is not affected.

Historian and Canary Compatibility
Canary Historian maintains continuous logging through v9.2-to-v10.1 solution upgrades. The AssetTree path is preserved consistently when enabling Historian, Alarm, or Device for nested tags.

Runtime Stability

Alarms

Trend Chart and DataHub

Devices and Protocols

OPC UA

ControlLogix

Siemens

MQTT

Other Drivers

Scripts and Automation

Script Engine

New Script APIs

Visualization, Displays, and Reports

New Controls

Display Authoring and Runtime

TWebBrowser

HTML5 Web Client

Reports

Mobile