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. |
|
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 Update Instructions.
Custom services running in the yuuvis® Momentum Kubernetes cluster can use a new internal endpoint of the AUTHENTICATION Service to get a valid internal JSON Web Token (JWT).
>> GET /authentication-internal/jwt/token
A new internal endpoint can be used to activate changes in the tenant configuration instead of the conventional refresh endpoint. Only changes in the authentication.oauth2.tenants
list in the application-oauth2.yml
configuration file are considered. Thus, the creation or manipulation of tenants can be carried out much faster. However, tenants that were removed from the configuration are NOT automatically deleted.
>> GET /authentication-internal/manage/refreshTenants
Secondary object types (SOTs) can be added or removed via the POST dms.request.objects.upsert.database-before webhook if they are referenced as floating in the corresponding object type definition. For the related properties, the following behavior is implemented now:
>> POST dms.request.objects.upsert.database-before
Some processes that lead to an update of the index of the search engine can be called with the new parameter waitForSearchConsistency
.
Processing | Description | Advantage | Disadvantage |
---|---|---|---|
synchronous | The success response of the corresponding endpoint is returned after the successful update of search index. | The changes are available even for search requests that are sent immediately after the synchronous processing. | The waiting time before the response is rather long. |
asynchronous | The success response of the corresponding endpoint does not wait for the update of the search index. | The waiting time for the response is far shorter. | Search requests sent immediately after the change request may be processed before the search index is updated. |
The update and import endpoints listed below accept an optional query parameter waitForSearchConsistency
. The default value corresponds to the behavior of previous product versions.
Endpoints | Default for waitForSearchConsistency |
---|---|
Import: POST /api/dms/objects | false |
Metadata update: POST /api/dms/objects/{objectId} PATCH /api/dms/objects/{objectId} PATCH /api/dms/objects | true |
Content update: POST /api/dms/objects/{objectId}/contents/file | true |
Restore: POST /api/dms/objects/{objectId}/versions/{versionNr}/actions/restore | true |
Tagging: | true |
Text rendition: POST /api/dms/objects/{objectId}/contents/renditions/text | true |
New endpoints allow for the management of the tenant-specific role set for any tenant by a system integrator:
The ARCHIVE Service can be connected to a Dell EMC ECS as repository via S3 protocol. Archive-internal retention is supported as well.
yuuvis® Momentum has been tested with Redis version 7.0.4. This version is now also used in the infrastructure Helm chart for test installations.
>> yuuvis® Momentum Requirements
yuuvis® Momentum has been tested with Elasticsearch version 7.16. This version is now also used in the infrastructure Helm chart for test installations.
>> yuuvis® Momentum Requirements
The the maintain-compare
command provided by the COMMANDER Service is improved in terms of available parameters and output data.
>> maintain-compare Command
The client libraries now use Angular 14. In case you extended your client with further libraries, please ensure that they are compatible with Angular 14.
>> Breaking Changes
It is possible to configure BPM forms such that fields containing IDs of processes display the corresponding process titles.
Comments on tasks can be added by users via the actions menu. Those comments become part of the process history to which the corresponding task belongs.
BPM variables can be displayed or hidden in the process aspect area for client users.
It is possible to specify a filter configuration for the inbox view via the filter
query parameter in the URL. Thus, you can provide a link to users that opens the inbox view with predefined filters. In the inbox view itself, the filters will be applied and visualized for the users in the graphical user interface. However, they are not specified in the URL that is visible in the browser. If the users reload the web page, the filter configuration is removed.
Users can set the following filter values:
currentUser
for fields classified with id:organization
today
, yesterday
, tomorrow
etc. for date fields Those values can be saved in the default filter configuration as well.
Two new developer libraries are available on NPM. Those libraries allow for the creation of a custom dashboard with configurable widgets. With these widgets, e.g., frequently used search requests can be saved to the dashboard.
Table properties are supported in the object version comparison.
All new library features are introduced.
The endpoints for text, form, icon and configuration management of the system-controller accept an optional query parameter tenant
now. If this parameter is set, the endpoint retrieves/updates the corresponding resource of the specified tenant instead of the global resource.
Tasks can be retrieved with a reduced set of properties in order to save processing time.
Note: The feature has been added subsequently via version fix.
>> GET /api-web/api/bpm/tasks
>> GET /api-web/api/bpm/tasks/{taskId}
Users with the YUUVIS_MANAGE_SETTINGS role are allowed to manage users of their own tenant.
>> Rights and Roles
Users with the YUUVIS_SYSTEM_INTEGRATOR role are allowed to manage tenant-specific catalogs for all tenants.
As a Beta version, the Client configuration tile is available on yuuvis® architect's dashboard. Configuration files including plug-in configurations can be managed.
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 no longer defined in the current schema.
Note: Your system hook configuration has to be adjusted manually.
>> SOTHOOK
In the default configuration, users with the YUUVIS_MANAGE_SETTINGS role are allowed to manage users of their own tenant. They have access to all endpoints /tenant-management/api/admin/users/**
. However, the following operations are not allowed for them:
>> admin-controller Endpoints (TENANT-MANAGEMENT)
briefRepresentation
is available for the endpoint GET /tenant-management/api/idm/users. The response will contain only a reduced data set in order to reduce the processing time.The two endpoints for retrieval of global or tenant-specific metrics also provide the current number of folder objects now.
It is possible to run multiple instances of the KEYCLOAK-PROXY service in parallel (horizontal scaling) in order to support very high work loads.
>> KEYCLOAK-PROXY Service
It is possible to configure the BPM Engine such that it connects to any identity provider supporting the Custom IDM API or the idm-controller endpoints of the Tenant Management API. Thus, it does not have to be directly connected to the identity provider anymore and therefore does not necessarily require Keycloak.
>> BPM-ENGINE Service
However, it is still possible to connect Keycloak or the KEYCLOAK-PROXY Service to the BPM Engine.
The Release Candidates (Alpha) provide the preliminary results expected to be ready at the corresponding date.
>> Version Tags Services - Release Candidates
The Release Candidates Alpha1-5 are for non-productive use only. |
waitForSearchConsistency
. (internal: OKTO-5204)New endpoints allow for the management of the tenant-specific role set for any tenant by a system integrator. (internal: OKTO-5243)
A new internal endpoint can be used to activate changes in the tenant configuration instead of the conventional refresh endpoint. (internal: OKTO-5273)
filter
query parameter in the URL (internal: BUD-1433)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 no longer defined in the current schema. (internal: OKTO-5235)The two weeks from 15 to 28 JUN 2022 are our innovation sprint that allows us to try out new ideas and explore new ways for the future. We do not plan to deliver new features in this sprint, but we will fix appearing bugs if possible.
maintain-compare
command provided by the COMMANDER Service is improved in terms of available parameters and output data. (internal: OKTO-5338)briefRepresentation
is available for the endpoint 'GET /tenant-management/api/idm/users'. The response will contain only a reduced data set in order to reduce the processing time. (internal: BUD-1488)currentUser
for user-specific fields, and to today
, yesterday
, tomorrow
etc. for date fields and save them as default query parameters. (internal: BUD-73)These initially planned features could not be realized. Some of them are planned for the next version 2022 Winter (LTS).
As a first step of BMP integration, users with the YUUVIS_TENANT_ADMIN role are allowed to manage processes in their tenant. The development will be continued for the next releases to provide management of tasks and process variables as well.
|
Below you can find information about the provided hotfixes. The latest status of all artefacts can be found here: "Version Tags Services".
|
|
|
|
|
|
|
|
|
|
|
|
|