Release Date: June 30, 2026

OL Hub Core v5.1.18 · OL Hub DTF v3.0.33

✨ New Features

Enforce OPA per Tenant on New OpenAPI Contracts

Tenant administrators can now enforce OPA (Open Policy Agent) validation on every new OpenAPI contract created within their tenant. When enabled, the OPA option and validation toggle are pre-selected and read-only for developers, and the admin can set default OPA parameters that users may override. Applies to both UI and CLI workflows.

Filter & Search Projects

The project list now supports a unified search box that filters across multiple fields — project name, creator name, description, and technology. Matching keywords are highlighted inline so users can immediately see why a project appeared in results (e.g., a search for "Joe" highlights the creator field). Labels remain filterable via the existing dedicated filter. When no results match, a helpful empty-state message suggests alternative search terms.

Terminal Trail Screen Notes

Screen notes captured during an ol-terminal recording session are now displayed in the Hub snapshot viewer. A notes button appears when notes exist for a snapshot; clicking it reveals positioned note icons on the screen and lists general (whole-snapshot) notes below the viewer.

Copy Assets Between Modules

Assets can now be copied between modules directly from the Hub UI — a capability previously available only via CLI. The target module must be of the same type as the source (e.g., screen-to-screen); cross-type copies are blocked.

🔧 Improvements

H3270 Multiline Vendor Field Handling

Fixed a runtime error (NoSuchElementException) when processing H3270 screens with multiline vendor fields. The engine now recovers gracefully from malformed field data and emits a warning log with diagnostic details instead of failing the entire flow.

Highlight Failed Step in Test Flow

When a screen flow fails during testing, the failed step is now visually highlighted in the flow editor, making it immediately clear where execution stopped.

Failed-Step Reporting on FlowMetadata

The FlowMetadata response now includes the identity of the failed step, enabling programmatic consumers and the UI to pinpoint failures without parsing logs.

JWT Configuration Improvements

Populate from token — A new "Populate properties from a JWT token" option decodes a pasted token and auto-fills the JWT fields configuration.
Special-character claim names — Properties with special characters (e.g., URL-based claims like https://ol.tenants/fullname) are now saved exactly as they appear in the token.
Save-button clarity — The save button behavior in the JWT configuration dialog has been corrected to avoid misleading state.

JWT Filtered Claims by Field Name

JWT claim extraction can now be filtered by specific field names, giving finer control over which token properties are surfaced in the contract.