What's new in 5.2.0
Release date: 2022-05-18
Important updates to system requirements:
Dropped support for PostgreSQL 9.6 and added support for PostgreSQL 12.
- Important changes to the Deployment profile.
- The recommended archive storage/profile quota limit on installation is increased from 200 MB to 10 GB in 5.2.0.*
- New StartTLS and other mail related configuration parameters added to support the user name/passphrase functionality.
Changes to the platform REST API:
- Made it possible to specify the state in 'CDIServer - Create access', and thereby create platform-managed accesses without activating them immediately.
Added a new API for activating an invited platform-managed access
Added a new API for retrieving a user agreement that is to be accepted and signed when activating an invited platform-managed access.
Changed the 'agreementTemplateId' property for 'ExternalRole' to ‘mixed’Improvements to the REST API documentation to facilitate implementation.
Updates to the Lequinox console:
The dependency on Lequinox professional ID has been dropped.
Users sign up and sign in to the console via user name and passphrase.
- Each platform customer gets a unique SLA-related license number which can be presented in the console.
- Naming of system administrator roles and console administration levels have been updated for enhanced clarity.
- Substantial improvements to the console user interface.
- The statistics service has been removed awaiting feature improvements.
- Transaction content cannot be accessed via the Lequinox console. Event meta data is presented, but the actual content must be handled by a Lequinox-enabled application via the platform API.
- Bug fixes and performance optimisations.
...
Lequinox platform versions
5.1.0
* Important information for customers currently on 5.1.0
In 5.2.0, the recommended archive storage/profile quota limit on installation is increased from 200 MB to 10 GB. If you have not set a value of your own, 10 GB will be the applied valid value, which might affect the need for available storage. If you have set a value of your own, that value stays valid. If so, make sure it still suits your environment.
...
| Title | Description | ||
|---|---|---|---|
User name and passphrase functionality added | You now sign in to the Lequinox console via user name and passphrase. With this comes a much smoother on-boarding and user experience, and the ability to reset your passphrase. | ||
| Dependency on Lequinox professional ID removed | With a focus on platform-managed role accounts, with accounts managed by the organisation platform, the dependency on Lequinox professional ID to sign in to the console and participate in transactions has been removed, and with that, the need for references. | ||
| Organisation suffix added | A unique organisation suffix has been added and is included in each role account user name in the platform. | ||
| Platform license numbers | Each platform customer is provided with a license number, which can be added in the Lequinox console for easy access in interactions with Support centre. | ||
| System application items separated from added items | In the Lequinox console, system items like the Console service and the Archive service have been separated from Added services (Lequinox-enabled applications). This applies to Applications and the related items Server accounts and User groups. | ||
| Names of first administrator roles updated | The names of the first system role created for platform and organisation administrators have been updated. Previous ‘Lequinox admin’ is now ‘Platform administrator’ and ‘Organisation admin’ is now ‘Organisation administrator’. | ||
| Console administration levels updated | The console administration levels have been updated for a clear distinction between system role names and console administration levels. Previous ‘Lequinox admin’ is now ‘Platform manager’, ‘Organisation admin’ is ‘Organisation administrator’, and ‘Regular user’ is ‘Organisation user’. The level ‘Role admin’ has been dropped. | ||
| User agreements relocated in the Lequinox console | In the Lequinox console, user agreements are now found under the Applications dropdown menu, available for user group creation, and applied for the accesses in each user group. | ||
| Statistics removed in the Lequinox console | Awaiting improvements and new features, the statistics service has been removed from the Lequinox console. | ||
| Transaction content not viewable in the Lequinox console | You are no longer able to access transaction content via the Lequinox console. You can view transaction event meta data but the actual content must be handled by a Lequinox-enabled application via the Lequinox platform API. | ||
| General user interface improvements | The user interface has a more unified layout, and detailed information rarely used is been placed in expandable sections for a cleaner experience. Content in toasters and popups have been improved for a more uniform experience. | ||
Access management enhanced in the platform API | When creating an access via the platform API, the state can be set to ‘invited’ in addition to ‘active’. The ‘invited’ state leaves it up to the application to activate the access before it can be used. The application can also retrieve and present a user agreement for the user to accept before their access is activated. | Maybe we should leave this out. There are similar changes made that we are not specifying in RN. Updated agreementTemplateId property in ExternalRole | Changed the agreementTemplateId property from ‘required‘ to ‘mixed’, where the permitted value depends on the API request. |
Improvements to the REST API documentation | Various additions and amendments to the REST API documentation, including possible responses, to facilitate application implementation for customers. |
Bug fixes
Title | Description |
|---|---|
LEQ-1861 (now public) No warning when leaving New organisation page | When leaving the page for creating a new organisation, the user is now warned that changes made will be lost.LEQ-1872 (now public) |
Update button for accesses always active | The Update button is now dimmed and inactive until any changes have been made. |
...