Skip to main content
inorigo® Platform
Released  

22.6.2

Draft — this release has not shipped yet. The content below describes work that is still in progress, and the date above is provisional. Do not publish until the release is marked as released and a release date is set.

Highlights​

  • Attribute used a key that has programmatic meaning in the inorigo® core have changed — review any custom solution, such as velocity that uses these types or their tables before upgrading
  • The inorigo® menus have been reworked to match the current design
  • A new API for building custom Workbench views in plugins
  • Rights Manager now generates expressions in the current variable syntax
  • Security improvements — upgrading is recommended
  • Bug fixes, including a browser freeze on logout

New features​

Simplified Workbench views for plugins​

Plugins can build custom Workbench views through a new API that hides the underlying Vaadin implementation. Plugin developers write against the inorigo® API rather than against the UI framework, so a view no longer has to track framework details to keep working.

Improvements​

Core stability​

Internal handling of partner lookups in the core has been reworked, improving stability when entity documents and group items are involved.

Changed behavior​

The following changes affect existing configuration or workflows. Review each item before upgrading.

AsUniqueKey and AsUniqueKeyPart have changed​

AsUniqueKey is not an instance of a definition, but its definitionID attribute used a key that has programmatic meaning in the inorigo® core — it marks the attribute that sets an instance's definition. Breaking that pattern meant Metagraph Builder and the Sync Tools could not handle these types. The attributes have been corrected:

  • AsUniqueKey: definitionID is renamed to ownerID.
  • AsUniqueKey: ownerID has the fixed type AsDefinition.
  • AsUniqueKeyPart: variableID has the fixed type GsVar.
  • AS_UNIQUE_KEY: the DEFINITION_CLASS column is no longer used.
  • AS_UNIQUE_KEY_PART: the VAR_CLASS column is no longer used.

The generic typing that DEFINITION_CLASS and VAR_CLASS supported was redundant, since these attributes can only address AsDefinition and its GsVar attribute type. Both columns remain in the database so that existing custom solutions do not break on upgrade.

On startup the platform scans applications, filters and Knowledge Sets and replaces any AsUniqueKey reference to definitionID with ownerID. No manual work is needed for those.

Note: the platform cannot detect every usage. Custom data sources and Velocity templates are not covered by the automatic correction — check them yourself before upgrading. These types are rarely used outside the platform, but if you use them anywhere, this change affects you.

Reworked inorigo® menus​

The menus have been brought closer to the current design:

  • The separation between modules and tools has been removed — both are now reached from one list.
  • Context selection has moved into the profile menu in the toolbar.

Before this release: modules and tools in separate menus, with context selection alongside them.
After this release: a single list, with context selection in the profile menu.

Rights Manager generates expressions in the current syntax​

Rights Manager generated expressions using the deprecated at-sign variable style. It now generates the curly-brace form instead. Expressions you have already saved are unaffected — the change applies to expressions Rights Manager generates from this release onwards.

Security improvements​

This release includes four security improvements. Upgrading is recommended for all installations. Details are available in the security advisory on the inorigo® documentation portal.

Bug fixes​

  • Logging Out of an Application No Longer Freezes the Browser
    Logging out from the user menu while an application was open could freeze the browser, leaving the user neither logged out nor able to continue working.

    Now logout completes and the login view is displayed as expected.

  • Filter Components and Buttons Lay Out Correctly in Web Applications
    Filter components, buttons and related controls could render with incorrect layout when an application was opened in the web client.

    Now these controls lay out as designed.

Compatibility and system requirements​

  • Upgrade from inorigo® 22.6.1.
  • Before upgrading, check any custom data source or Velocity template that references AsUniqueKey, AsUniqueKeyPart, AS_UNIQUE_KEY or AS_UNIQUE_KEY_PART. See AsUniqueKey and AsUniqueKeyPart have changed above.
Last updated on