22.6.0
Release Notes — 22.6.0
PostgreSQL Support
inorigo® can now run on PostgreSQL as a fully supported database, alongside the existing SQL Server option. Both drivers ship with the server and are selected via the JDBC connection string. This gives organizations greater flexibility in their infrastructure choices and reduces dependency on a single database vendor.
Comments
Comments can now be added across the platform, making it possible to document the intent behind any change at the point it is made. Comment support is available in:
- Metagraph Builder — comments travel with every save event and are accessible via the API, supporting audit trails and integration workflows
- Application Builder — comments support documentation of application configuration and expression logic
- Sync Tool — comments can be added to synchronisation operations, giving context to what is being promoted and why (available when the Sync Tool add-on is released)
- Expressions — inline block comments ( /* ... */ ) can be added directly inside the expression editor across all builders, making complex logic easier to read, maintain, and hand over.
Together these additions make traceability a first-class part of working in inorigo® — reducing reliance on external documentation and making onboarding to existing models significantly easier.
Data Grid for Core
Data Grid for Core is a new add-on that lets users edit and create multiple entities in a spreadsheet-style matrix — without building or opening an application. It uses queries to retrieve datasets and offers the same base editing capabilities as Data Grid for Applications, making it suitable for efficient bulk editing directly from the grid.
Data Grid for Core is accessible from the Launcher menu.
New Capabilities
Defined Attributes Data Source
A new Data Source type is available in Knowledge Set Builder that lets you query attribute metadata directly — no custom SQL required. It returns all defined attributes for a given definition type, including inherited ones, across all data contexts. This simplifies reporting and model documentation scenarios that previously required manual workarounds.
GET Endpoints for Knowledge Set Execution
Three simplified GET methods are now available for Knowledge Set execution: execute, execute objects, and count. These are well-suited to straightforward queries without parameters or custom sorting, and reduce integration overhead for consuming systems. The existing POST methods remain available for more complex scenarios.
Log Download from System Management
Server Admins can now download log files directly from System Management by right-clicking a file in the log list — no file system or SSH access required. File sizes are now visible in the list, making it easier to identify which logs to pull during troubleshooting.
Third-Party Licence Export
A download button in System Management lets administrators export the full list of third-party licences as a CSV file. This is useful for compliance reviews, procurement processes, and internal audits.
Built-in Data Connections for Integration Folders
Three pre-configured data connections are now available out of the box: Inorigo Integration Folder, Inorigo Import Folder, and Inorigo Export Folder. They are managed dynamically by the inorigo.io.integration system setting and require no manual setup — reducing configuration effort for common integration scenarios.
Application Rights Enforcement in Filter Boxes
Editing actions in filter boxes are now controlled by the rights set on the Application itself, making Application Builder applications behave consistently with other tools such as Knowledge Set Builder. This is opt-in and configurable via a server setting (verso.runtime.apply.rights=true), so existing behaviour is unchanged until explicitly enabled.
Changed Behavior
The following changes affect existing configuration or workflows. Review each item before upgrading.
User Settings Architecture
User settings are now stored in a dedicated database table (UN_USER_SETTING) and managed through new Core API endpoints. The Preferences panel has been redesigned. Default values are controlled via server configuration. Two new events are introduced: UserSettingEvent (when a user setting changes) and SystemSettingEvent (when a server configuration parameter changes).
Themes Moved to Generic Context
Themes now stored in the Generic data context — All themes are now saved to the Generic data context. The Theme Editor has been updated accordingly. Existing themes are automatically migrated to the Generic context on upgrade.
Auto-Created Users Default to Read Only
Users created automatically via external authentication without a group specified are now placed in the Read Only group by default. This ensures provisioned accounts receive minimal access until explicitly granted more. Configurable via authentication.external.inline.group.id in server properties.
Launcher Download Link
The Download Launcher link in the info menu now points to the inorigo® Launcher in the Microsoft Store. The URL is configurable via client.win.launcher.url. The previous client.launcher.enabled setting is retired and can be removed from server configuration.
Legacy SMTP and Graph Mail
Legacy SMTP configuration no longer interferes with Graph Mail settings. The two are now fully independent. If you are migrating from legacy SMTP to Graph Mail, verify your mail configuration after upgrading.
Security
This release includes two security improvements. A server-side vulnerability has been patched and data connection credentials are now encrypted at rest. Upgrading is recommended. Details are available in the full security advisory on the inorigo® documentation portal.
Bug Fixes
42 issues have been resolved in this release, spanning API behavior, filter boxes, Metagraph Builder, Knowledge Sets, access control, and UI display. Full details are available in the change log on the inorigo® documentation portal.