FrameworX 10.1 Update 5d is a planned release, scheduled for August 5, 2026, as a free upgrade for every FrameworX 10.x customer. It follows Update 5c (June 22, 2026) and concentrates on AI-driven authoring and automated testing, display and symbol import fidelity, the Scripts and Code Editor experience, ontology round-tripping, and redundancy reliability.

Release Notes → Update 5d

FrameworX 10.1 Update 5d — planned for August 5, 2026

The Update themes:

• AI authoring and automated testing — author complete display configuration from automation, update a display’s code-behind without touching its canvas, full-fidelity JSON display import, and drive suppressed Designer dialogs, electronic-signature workflows, and running operator clients from automated tests.
• Display and symbol fidelity — symbol size, rotation, and legend now survive a JSON display import; theme-color symbol rendering corrected in the Designer editor; drawing-tool cancel no longer leaves orphan shapes or phantom undo entries.
• Scripts and Code Editor — multi-line string literals and interpolation with Tag/Info references compile correctly, IntelliSense recognizes newly created classes and namespaces, Find All References is enabled in the Script Class editor, and the editor keeps cursor and scroll position across tab switches and saves.
• Unified Namespace and ontology — RDF/OWL imports create object relationships and the asset-tree hierarchy, the ISA-88 import template’s mapping rules are applied, and a UNS graph round-trips through export and re-import with its hierarchy intact.
• Devices and protocols — new PEER Protocol Driver, store-and-forward buffering for the Azure IoT Hub / MQTT driver, Siemens tag import extended to PLC tag tables, and OPC UA UDT array members now sent by the OPC Server.
• Alarms, Historian and redundancy — redundancy replication keeps up on large projects, diagnostic tools can connect to the standby server, and Alarm Viewer respects a custom alarm-history table name.
• Web client — significantly faster HTML5 load through compressed delivery and browser caching.

See Update 5d - Detailed Release Notes for the complete item-by-item list.

AI, MCP and automation

This release makes AI-driven authoring safe to use on existing solutions and closes the gaps that blocked automated testing.

• Display authoring from automation is complete — legend, connections, chart orientation, child-display links, and themes can all be configured programmatically.
• Content-only display updates — a display’s code-behind script can be updated without altering the drawing canvas.
• Full-fidelity JSON display import — nested groups, dialog settings, and exact layout are preserved.
• Automated testing reaches the whole product — suppressed Designer configuration dialogs, dialog content and prompts, electronic-signature and security workflows, and the running WPF and web operator clients can all be driven and observed from automated tests.
• Concurrent AI sessions are isolated — exported solution files are no longer overwritten by a parallel session, and Designer instances started by the AI tools are reused and shut down cleanly instead of accumulating.
• Security secrets written through the AI tools are stored encrypted, with password fields protected on every tool surface.

Displays and Symbols

Symbol properties now survive the JSON display import round trip — size, rotation, and legend were each being reset to defaults. Library symbols with a theme-color FillColor dynamic render correctly in the Designer editor, fill color is applied to the intended object when another object is clicked immediately after, and selecting a button whose Action script method was renamed or deleted no longer silently clears its Action target.

Scripts and Code Editor

A broad pass over the scripting experience: multi-line string literals and string interpolation with Tag/Info references compile correctly in both Scripts and Display CodeBehind; IntelliSense exposes every class in a Script Namespace, refreshes for newly created classes, and survives tuple destructuring in a foreach header; namespace creation no longer duplicates using directives; and third-party DLLs in Script References load correctly when the product bundles a same-name library.

Unified Namespace, Tags and Ontology

Ontology import and export round-trip correctly: RDF/OWL imports create object relationships and the asset-tree hierarchy, the ISA-88 template’s mapping rules are applied rather than silently ignored, and an exported UNS graph preserves its asset hierarchy on re-import when entities carry a source IRI. In the asset tree, GUID tag initial values are retained, case-only tag renames work, and folders and tags list in order after importing an existing solution’s UNS.

Devices and protocols

Adds the PEER Protocol Driver and store-and-forward local buffering for the Azure IoT Hub / MQTT driver. Siemens tag import now covers PLC tag tables (Input/Output/Memory), not only Data Blocks, and no longer fails with a “file not found” error on TIA Portal (local). OPC UA UDT array members are sent by the OPC Server, Modbus TCP master frames are well-formed, and the MQTT Client Connector no longer escalates CPU on invalid broker credentials.

Alarms, Historian and redundancy

Historian and Alarm redundancy replication keeps up on large projects, so the standby database synchronizes fully. Diagnostic tools can connect to the standby server, the standby no longer starts the Devices module Running when a device is Reserved or Remote, and Alarm Viewer respects a custom alarm-history table name.

Breaking Changes and Deprecations

The SolutionCenter API can no longer be enabled on a released build. The API has shipped disabled by default since 10.1.5 GA, pending security hardening work on the underlying service surface. Until this update, an operator could override that gate by setting both SolutionCenterApi.Enabled and SolutionCenterApi.AcceptRiskOnOldBuild to true in MachineSettings/TWebServices.json. That override is no longer available in a released build, and no configuration setting re-enables the API in the 10.1.5 line. Installations that had enabled the API this way will find it stops responding after this update. The API remains planned to become available in a future release once the hardening work completes.

Windows-Authentication logins relayed through a Secure Gateway now require the gateway’s Windows-Authentication mode. The runtime no longer accepts a Windows-Authentication claim as proof of identity; it is honored only when the connection itself was Windows-authenticated. If you run TSecureGatewayService with WA=false, set WA=true so the gateway relays over the runtime’s Windows-Authentication port — otherwise Windows-authenticated users through that gateway are refused after this update. Password-authenticated users through the same gateway are unaffected. The runtime must be started with /wa on .NET Framework for the Windows-Authentication port to exist.

Lifecycle and Support

Update 5d is planned as a free upgrade for every FrameworX 10.x customer, shipping with the platform’s standard within-major-version 100% compatibility commitment — every 10.1.x solution opens and runs without migration or rework. See Breaking Changes and Deprecations above for two configuration-level changes that may require an adjustment on affected installations.

The full lifecycle policy, version support phases, and end-of-support dates for older FrameworX and FactoryStudio versions are documented on the Product Lifecycle and End of Support page.