Release Date: February 23, 2026

OL HUB Core Version 5.0.155 · OL HUB DTF Version 3.0.24

✨ New Features

PL/I Support Enhancements in Hub

• PL/I parsing in mainframe modules (UI)
  The Hub UI now supports parsing PL/I sources in mainframe modules, similar to COBOL with copybooks. You can:

  • Parse PL/I files with or without associated PLIN files.
  • Add additional PLIN files, analogous to copybooks, to complete the structure.
  • Define separate input and output PLIN structures, similar to copybook-based parsing in CICS.

• PL/I input/output identification in Hub “Add Source from Hub” flow
  When importing PL/I sources from the Hub UI, you can now specify which structures are inputs and which are outputs. This is done via configurable input and output field patterns, aligning the UI capability with what is already available in the CLI (regex-based identification of input and output fields).

MCP Server support for No-Code Services

Enable AI agents (like Claude, ChatGPT, Cursor, etc.) to discover and execute flows from the Hub no-code runtime.
This will allow customers to integrate their backend flows with AI-powered applications and assistants.

🚀 Enhancements

Roles & Permissions for Modules and Connections

We’ve introduced role-based access control (RBAC) in Hub for Modules and Connections to improve security without limiting visibility.
Everyone can still view all Modules and Connections, but only Owners, Admins, and Shared Users can edit them, and only Owners and Admins can delete them.
If you suddenly can’t edit a connection you used to work on, it’s likely due to these new guardrails—ask the Owner to add you as a Shared user.

ETL Project - Contract Configuration

Defined and implemented a standardized ETL Contract Configuration within Hub.
This brings consistency to data extraction, transformation, and loading across integrations.

Environment Variable Support in Low-Code / No-Code Configurations

• Richer environment variable usage in connection and consumer properties
  Environment variables can now be used more flexibly in configuration:

  • Environment variables can be used as placeholders within property values, not just as full-value replacements.
    Examples:
    • host: http://${envVar}.openlegacy.com
    • jdbc-url: http://${env}.company.com/${dbName}
    • user: ${user}
    • password: ${pwd}
  • Environment variables are now supported both in connection properties and in additional properties.
  • The same capabilities are available when configuring via YAML.

• Environment variables in consumers
  For consumers, environment variables can now be used in:

  • Enrichments
  • Additional properties
    This is also supported via YAML configurations, providing a consistent experience across runtime definitions.

🐞 Bug Fixes

Date Format Enforcement in Hub

• Consistent date format validation
  A problem where date formats were not being enforced on input parameters has been resolved. Previously, fields intended to enforce specific date formats accepted inconsistent values. With this fix:
  • Date-format-defined input parameters now correctly enforce the specified format.
  • Inputs that do not match the required date format are rejected or flagged, ensuring data consistency and reducing downstream errors.