2026-07-23

New Features

• Read flow address rows on a custom data contract now take their Virtual Path and Tag Name from a single dropdown listing the fields defined by that contract's data model, so a value the contract does not define is caught while editing instead of at deploy. Save & Deploy stays blocked until every custom-contract row holds a valid selection. Rows on the built-in _historian and _raw contracts keep free-text input
• For users testing the new historian feature, the topic browser shows copy-ready Grafana and TimescaleDB queries for a selected tag when the historian feature flag is enabled, so you can paste them straight into Grafana or a database connector. (ENG-5306)

Improvements

• A Historian bridge no longer asks you to type a connection host and port; they are filled in read-only from the instance's configured Historian, so the bridge's health check targets that database and can't be pointed at the wrong host. If you later change the Historian's address, the bridges that use it follow it automatically.