| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
Resources & Remarks
Modification History
---- This is moved to time after 2021 Summer, so taken out again: yuuvis® client as reference implementationStandard Configurations (as of Release Candidate Alpha5)The tenant-specific standard settings for column configurations and filters are now saved in the CONFIG service via the new Web-API Gateway POST endpoint ../api/admin/resources/config and read with the GET endpoint instead of using the USERSERVICE. Action: After the update, the old settings are read from the USERSERVICE unless new configurations are saved again. So, there is nothing to do. But if you save such settings using a different application, from now on you should save using the above-mentioned endpoints instead. |
Each yuuvis® Momentum version update introduces changes in the system. In general, we try to deploy such changes in a non-breaking way. If this is not possible, you will find all necessary and vital information on this page. The following breaking changes changes are incompatible changes we had to deploy into operation, and therefore you—as you—as a yuuvis® user—need user—need to be aware of them and take action accordingly.
Preview - Product Version 2021 Winter (as of November 12, 2021)
yuuvis® client as reference implementation
Follow-up
As of Release Candidate Alpa2, the Inbox, My processes and My Follow-ups views are extended and therefore the process model for a follow-up has been refactored as well. Models of previous versions are not supported anymore. Processes defined via deprecated models will appear without subject and attachments.
Action: Delete all processes defined via deprecated models of previous versions either in the client application or directly via Web-API Gateway.
Product Version 2021 Autumn (as of August 20, 2021)
Core
Token Handling for Custom Services
The internal tokens (JWT) created by the AUTHENTICATION Service are now signed.
Actions:
- If you are working with Java custom services using the annotation
com.os.services.core.security.EnableServiceSecurityfrom the libraryservices-security, you need to update the library to version 5.7.0. - If you are working with Java custom services using the library
com.nimbusds:nimbus-jose-jwtfor parsing of incoming JWTs, you have to use the classcom.nimbusds.jwt.SignedJWTinstead of the classcom.nimbusds.jwt.PlainJWT.
Object Creation Permissions
In role sets, permissions can now be set for the creation of objects by introducing the action create. So far, the object creation was enabled together with the edit permission via the action write. Additionally, the role YUUVIS_CREATE_OBJECT had to be assigned to users in order to enable object creation via API Gateway. As of now, this role does not affect the functionality of the API Gateway and is not part of the global default role set anymore.
>> Access Authorization and Permissions
Actions:
- In each of your existing role sets, add
<action>create</action>to each permission including awriteaction that should allow for object creation further on. If the permission includes a condition, ensure that no CONTAINS statement is involved. Use the endpoints for managing permissions.
Remove the following lines from section ### API-endpoints in authorization.accessses in the configuration file authentication-prod.yml:
| Code Block | ||
|---|---|---|
| ||
- endpoints: /api/dms/objects
method: POST
access: hasAuthority('YUUVIS_CREATE_OBJECT') |
Tenant Management API
Assignment of the System Integrator Role
In previous versions, the endpoint POST /tenant-management/api/admin/users that is accessible with the role YUUVIS_TENANT_ADMIN allowed for the assignment of the role YUUVIS_SYSTEM_INTEGRATOR to other users. This is not possible anymore. Only the endpoint POST /tenant-management/api/system/tenants/{tenant}/users that is accessible with the role YUUVIS_SYSTEM_INTEGRATOR allows for the assignment of the role YUUVIS_SYSTEM_INTEGRATOR to other users.
Product Version 2021 Summer (as of May 28, 2021)
Web-API Gateway
URLs (as of Release Candidate Alpha5)
The endpoint URLs have been changed to match the structure of other service-specific endpoint URLs. The new URLs are used by yuuvis® client as reference implementation and yuuvis® architect.
...
| title | Open the list of all Web-API gateway endpoint URL changes... |
|---|
The endpoints are grouped consistent with the Web-API Gateway Swagger-UI. The changes are highlighted in bold letters in the new URL.
...
An update to a new version that skips some of the previous versions is possible and does not require updating to each version in between. However, in this case, you must carry out all actions in the order in which they are listed below. Starting with your current version up to the version you want to update to.
Product Version 2020 Winter (as of March 05, 2021)
...
Action: Please remove the prefixes from table column names referenced in the localization, in forms and in scripts.
Product Version 2020 Autumn (as of October 30, 2020)
yuuvis® client as a reference implementation
...
The values are set for each update by the new sothook, which has to be installed and configured. It writes the current leading object type IDs into the property.
>> "Referencing the 'appClientsystem:leadingType' Object Type" | "/wiki/spaces/YM20WI/pages/319784094"
...
The Search Service API supports rapid development of custom clients and is part of the API-WEB service. It is used by our reference implementation: yuuvis® client. The API has been changed and a query's result is now an array instead of an object.
>> "Search Service API"
Product Version 2019 Winter (as of December 13, 2019)
Renaming of system properties from "enaio" to "system"
...