Everything within this section is only visible while editing. Use Page Properties ID "STUB", "REFACTURE", "PROGRESS", "rDEV", "rDOC", "rLANG" and "DONE". Everything contained within the table is displayed in the (INTERNAL) Reports page.
Resources & Remarks
Modification History Add a new line to this table and fill it whenever you edit the page.
|
This page provides an overview of the new features provided with the major release and the expected preliminary results provided in our release candidates during the ongoing building process. The Release Candidate are for non-productive use only. |
Find our docker images and Helm Charts linked here:
>> Version Tags Services
|
Here you will find some of the new release's highlights. Check out the Change Log for further information on all changes.
Please also pay attention to the Breaking Changes and some Update Instructions.
It is now possible to operate multiple instances of the AUTHENTICATION service that use the same session state. Thus, in case one instance is not available for some reason, a parallel instance can step in and continue the running process without any interruption.
>> AUTHENTICATION Service - Running Multiple Instances
To allow the storage of individual user session states in the designated Redis database, the AUTHENTICATION service configuration must be adjusted:
>> Update Instructions 2022 Spring
The length limit of the string tag names is extended to 128 characters.
>> Tagging
Internal requests within the yuuvis® Momentum cluster are authenticated via a valid JSON Web Token (JWT). The expiration date is now validated as well. Thus, it is no longer possible to authenticate with a token if its expiration date is exceeded.
>> Validating Internal JSON Web Tokens
Keycloak version v15 is supported and is available via Docker image for test installations.
>> yuuvis® Momentum Requirements
It is possible to restore an old version of an object via a new API endpoint.
>> POST /api/dms/objects/{objectId}/versions/{versionNr}/actions/restore
An endpoint allows for the creation of audit trail entries for individual objects.
>> POST /audit/api/dms/objects/custom
If the value for the system:parentId
property is changed, added or removed, an audit entry with the specific action code 340
is created in addition to the usual audit entry corresponding to a metadata update.
>> Audit Trail - an "Object's History"
A new endpoint retrieves information on the installed product version.
>> GET /api/dms/info
The input and output data for each webhook can be monitored via loggers.
>> Loggers for Webhooks
In order avoid system bottlenecks, the time a called webhook may take to process can be limited.
>> Configuring Webhooks
Services within the yuuvis® Momentum Kubernetes cluster can use certificates in order to internally send authenticated requests instead of conventional user name and password credentials.
>> /wiki/spaces/YMY/pages/320050690
At runtime, the CONFIGSERVICE applies all changes to configuration files to its local resources first. At regular intervals of 5 minutes, the remote resources on the git server are synchronized. The procedure of collecting and summarizing changes reduces the number of commits that have to be managed by the CONFIGSERVICE in case of a high frequency of change requests.
>> CONFIGSERVICE
This leads to some breaking changes that have to be taken into consideration during the version update.
>> Breaking Changes
A new endpoint provided in the dms-controller retrieves the permissions of the currently logged-in user according to the assigned roles and their definition in the corresponding role set.
>> GET /api-web/api/dms/permissions
For the retrieval of user account-specific data, the user-controller endpoints call the Tenant Management API instead of the USERSERVICE now. This enables the usage of the Web-API gateway in combination with other identity providers than Keycloak. User-specific configurations and contents are still managed via the USERSERVICE.
Note: The API-WEB service requires a running instance of the TENANT-MANAGEMENT service.
>> Breaking Changes
Metadata and binary content files of previous versions of a DMS object can be restored via a new endpoint.
>> GET /api-web/api/dms/objects/{id}/versions/{Nr}/actions/restore
The new Swagger UI provides the Spring Boot Actuator endpoint of the API-WEB service in order to directly retrieve monitoring information. The configuration file authentication-prod.yml configuration file has to be manually adjusted.
>> Breaking Changes
The schemata are cached to allow for a faster startup of client applications.
The search endpoint allows for negation in conditions now. Thus, e.g., it is possible to search for objects for which a specific property does not have the value null
.
>> Search via Web-API Gateway
The USERSERVICE is now only responsible for the management of user-specific settings and contents. The retrieval of account-specific data belongs to the responsibility of the TENANT-MANAGEMENT service. Thus, the user information endpoints GET /userservice/api/users and GET /userservice/api/users/{userId} are removed from the USERSERVICE's API.
>> Breaking Changes
In order to retrieve a DMS object via URL (e.g., a saved search, a bookmark or an e-mail), a valid authentication session has to be active in the user's browser. If no valid session is open, the user is redirected to a configurable log-in page. After successful authentication, the desired DMS object is retrieved.
switch
in order to be represented via a switch control.main.json
configuration file to be used for this purpose.Metadata and binary content files of previous versions of a DMS object can be restored via client application. A new endpoint of the Web-API gateway is called.
>> DmsService of Core Library
The new commands library offers a QuickAccessComponent
that simplifies the navigation through the application via keyboard.
>> Custom Client Build with Libraries
The functionality provided by the OFFICE365 and DASHLET services is integrated via plug-in configuration in combination with the VIEWER Service in a library-based client. Thus, it is possible to offer preview and editing possibilities for Microsoft Office content files in your client application.
>> Integration of Office 365 Functionalities
The standard column and filter configuration as well as its plug-ins cannot be managed any longer via the client application but via the Web-API Gateway instead.
>> Structure and Features of the Client
Our tenant management solutions use the Keycloak version v15.
>> Requirements for Tenant Management Services
The Tenant Management API can be connected with other identity providers than Keycloak via a custom microservice. This connection allows only for reading user data but not for updating them. The Tenant Management API is called by the API-WEB service and the BPM-ENGINE service.
>> TENANT-MANAGEMENT Service
The new Swagger UI provides the Spring Boot Actuator endpoint of the TENANT-MANAGEMENT service in order to directly retrieve monitoring information. The authentication-prod.yml configuration file has to be manually adjusted.
>> Breaking Changes
The delegation-related functionality of the endpoint for applying actions to individual tasks is extended. Especially, the following actions allow to apply changes to variables as well:
delegate
resolve
>> POST /bpm-engine/api/tasks/{taskId}
The Release Candidates (Alpha) provide the preliminary results expected to be ready at the corresponding date.
The Release Candidates Alpha1-5 are for non-productive use only. |
null
value we are offering a crossed-out box.boolean
can be classified as a switch
.system:parentId
property is changed, added or removed, an audit entry with the specific action code 340
is created in addition to the usual audit entry corresponding to a metadata update. (internal: OKTO-4876)A title/name and a description property should be assigned to all objects that are managed via a library-based client as they are used in the object details header and the mixed result list. It is now possible to configure the properties in the main.json
configuration file to be used for this purpose. (internal: BUD-819)
QuickAccessComponent
simplifies the navigation through the application via keyboard. (internal: BUD-560)These initially planned features could not be realized. Some of them are planned for the next version 2022 Summer.
A tenant including all saved objects can be deleted from the yuuvis® Momentum system.
A form field of type string and classification id:organization
can be configured such that it is available only for users with a specified role.
System integrators cannot only maintain tenant-specific resources of their own tenant but can select a target tenant now.
Administrators are supported to model schemata via the graphical user interface of yuuvis® architect. As a first step, is possible to edit the properties of existing schema files via a self-explanatory form. Alternatively, the XML structure can be edited via an ASCII editor.
Administrators can set up the standard column and filter configuration for their client application as well as its plug-ins.
An example custom IDM Proxy Service demonstrates how to connect a different identity provider than Keycloak that supports the idm-controller endpoints. The example microservice connects the web identity management system Auth0.
|
Below you will find information about the provided hotfixes. The latest status about the atrefacts can be bound here: "Version Tags Services".
|
|
|
|
|