Version 2022 Autumn is not yet released ...
The following information as well as the linked information is intended to outline some of our current product developments for our yuuvis® Momentum 2022 Autumn.
Like everything else in life, the best plans can change over time. The following article describes the current state of work, but it is important to understand that the details are for information purposes only and are not to be understood as binding commitments.
OPTIMAL SYSTEMS reserves the right to make changes in the planning, development and release of products and their features and functions at its sole discretion.
When updating your yuuvis® Momentum installation to version 2022 Autumn, manual configuration changes are required for some services.
Table of Contents
Breaking Changes
The following Breaking Changes are incompatible changes we had to deploy into operation, and therefore you—as a yuuvis® user—need to be aware of them and take action accordingly.
Client Services & Client Development
Developer Libraries
Angular Version Update
The client libraries use Angular 14 now. In case you extended your client with further (third party) libraries, please ensure that they are compatible with Angular 14.
Action: If necessary, update your external libraries to a version that supports Angular 14.
Tenant Management
Tenant Management API
idm-controller Endpoints
The optional query parameter briefRepresentation is available for the endpoint GET /tenant-management/api/idm/users. Per default, the response will contain only a reduced data set in order to reduce the processing time. Especially, roles and groups of the listed users are not included in the default response anymore.
Action: In order to keep the behavior of the previous versions, set the query parameter briefRepresentation=false for each request to the endpoint.
Configurations Enabling new Features
Some new features require manual configuration in order to operate properly after the update to the new yuuvis® Momentum version.
SOTHOOK
Stability Improvement
The service uses the webhook type dms.request.objects.upsert.database-before instead of dms.request.objects.upsert.storage-before. With this improvement, the service can handle old objects with metadata properties that are not anymore defined in the current schema. Furthermore, the SOTHOOK configuration is now part of the app-specific system hook configuration for the clientsystem app.
In your global system hook configuration, remove or disable the two webhooks with a value "http://sothook/*" for the "url" parameter. Add the following two webhooks to the app-specific system hook configuration, via the endpoint POST /api/system/apps/{app}/systemhooks for the clientsystem app.
{
"enable": true,
"predicate": "spel:T(java.util.List).of(100,101).contains(options['action']) && properties['system:secondaryObjectTypeIds'] != null && properties['system:secondaryObjectTypeIds']['value'].contains('appClientsystem:leadingType')",
"type": "dms.request.objects.upsert.database-before",
"url": "http://sothook/api/dms/request/import/databasebefore",
"useDiscovery": true
},
{
"enable": true,
"predicate": "spel:T(java.util.List).of(300).contains(options['action']) && properties['system:secondaryObjectTypeIds'] != null && properties['system:secondaryObjectTypeIds']['value'].contains('appClientsystem:leadingType')",
"type": "dms.request.objects.upsert.database-before",
"url": "http://sothook/api/dms/request/updatemetadata/databasebefore",
"useDiscovery": true
}
>> SOTHOOK