Preview
CoreOne Admin User Interface
Some of the auto complete controls on various masks returned incomplete search results. This behaviours has been fixed.
The performance of the context resolvers, mainly the organizational unit context, has been improved.
CoreOne Application Service
The Swiss UID response mapper had a wrong mapping. It mapped the
activeflag of the HR status to theactiveof organization units. Therefore companies without a HR entry could not be registered. This issue was fixed.There is a new setting that allows you to specify specific backend servers to only run scheduled tasks. All other servers will only run fast-tracked tasks, coming from user interactions over the UIs. To take full advantage of this features, you should point your UI servers connection to those backend servers, that do not run scheduled tasks. Fore more details see here.
The
name_keyof an employment is now available in both the string expression designer and in the template dictionaries.
CoreOne Authentication Services
There is a new Permission API that can be used to read the provisioned permissions
Breaking Change: Ressource Assignment with the context “Current Core Identity” used to be provisioned without a context to the CoreOne Authentication service. To better suite the Permission API requirements, this behavior was changed and they now also have a context provisioned. This is only a breaking change if your application requests the
roles_with_contextscope. Instead of an empty context, you will now get the user itself as the context.
CoreOne Database Services
Support for MariaDB 10.9 and greater was added.
CoreOne OpenLDAP System Connector
A bug in the password validation implementation prevented the propagation of password changes over the connector. The bug has been fixed.
CoreOne Self-Service Portal
Editing a delegations with the start date in the past resulted in an UI validation error immediately upon clicking edit. This issue has been resolved.
CoreOne Workflow Runner
It’s now possible to encrypt the workflow options stored in the database, so that any sensitive data within the workflows are protected beyond the database. This new setting can be activated via installer or in the configuration file.