This page contains a preview of the upcoming next release. |
-
All the libraries and dependencies have been updated to the latest versions.
There is a new flag on the application that enables you to restrict access to an application for users that have no role claim associated for that given application
You now can configure default role and resource assignments on the application. Upon the first access of a user to that application, the configured roles and resources will automatically assigned to them. This is a new way of assigning default rights to a user. You can also change this configuration later on and it will apply to all users that have used the given application.
All the libraries and dependencies have been updated to the latest versions.
All the libraries and dependencies have been updated to the latest versions.
The configuration file is now stored as an encrypted configuration and can only be read and changed when in possession of the local machine key. All existing configurations will be encrypted automatically.
The is_position
flag of an organizational unit has been moved to the organizational unit type where there are now three different types: legal entity, organizational unit and position.
The active
flag of an organizational unit has been moved to an organizational unit state where there are now four different states: active, inactive, deleted, activation pending
You have to account for those change in your import configuration. Instead of mapping the |
All the libraries and dependencies have been updated to the latest versions.
We are starting to migrate all Workflows from the Microsoft .NET Workflow Foundation to a new Workflow Engine
All existing workflows are still available and will be supported in the upcoming releases.
New workflows will be handled with the new Workflow Engine that enables you to perform even more actions like awaiting user feedback and more.
The new workflow designer is now web-based which allows you to configure those workflows conveniently from a browser.