This release focuses on platform stability, developer productivity, and access control improvements. All changes are backwards compatible.
Enhancements
Auto-created users added to Read-Only group by default
A new server setting controls the default group assignment for auto-created users when no user group is specified in the request. The default value is Read Only, ensuring that automatically provisioned accounts receive minimal access until explicitly granted more. This also applies when the legacy type parameter is used.
Configurable via server settings. If the setting is cleared, the system falls back to Read Only.
Role selection removed from user creation dialog
The role field has been removed from the user creation dialog to prevent inconsistencies in authentication records. Roles and permissions must now be managed exclusively through the Rights Manager, ensuring a single authoritative source of truth for access control.
Name field is now mandatory on UnUser objects
The Name field is now required on all UnUser objects within inorigo, ensuring complete and consistent user records across the platform.
Inline comment support in Expression blocks
Expression blocks now support inline comments, enabling developers to document logic directly within expressions. This improves readability, simplifies onboarding, and makes long-term maintenance of complex expressions significantly easier.
API
KS Tree endpoints restored
KS Tree endpoints, previously disabled in preparation for a GraphQL-based replacement, have been re-enabled. The GraphQL migration remains on the roadmap; however, given the scope of that work, these endpoints will remain available until a fully supported replacement is ready.
No action required for existing integrations. Endpoints behave as before.
Bug fixes
- Resolved a java.util.ConcurrentModificationException error occurring under concurrent load.
- Fixed VALUE_CLEAR primitive methods that were not functioning as expected.
- Corrected the behavior of $LOOKUP and $FINDONE in Legacy mode.
- Resolved a missing data issue in a customer's Master solution.
- Fixed a failure when creating a relation between two objects via an app or Velocity file method.
- Resolved an application crash caused by an invalid filter box structure.
- Fixed an error occurring when editing content within applications.
- Corrected an issue where the filter box tree displayed incorrectly after an entity update.
- Fixed an issue where the filter box tree collapsed unexpectedly following a data update.
- Implicit selections in a structured filter box converted to flat view are now correctly placed at the top of the list.


