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
Place only ready and released paragraphs here! For contributions in preparation please use this page: /wiki/spaces/YMY/pages/320046140 Modification History Add a new line to this table and fill it whenever you edit the page.
Resistant TagsIt is now possible to assign resistant tags that are automatically transferred to the new version of an object. If a new version of an object is created, e.g., by a POST update of the metadata or the binary content file, those tags will be removed from the old object version and assigned to the new object version. As usual, the previous object version will not have any tags afterwards. However, the new version will have all the resistant tags assigned to it that were originally assigned to the previous version. Resistant Tags
|
This page provides an overview of the new features provided with the major release 2021 Summer and the 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 specify longer LIKE expressions in search queries. However, the LIKE
expressions remain limited by their number of included wildcards. Thus, a maximum number of 10 %
and _
characters are allowed in one LIKE
expression. The limit compliance is verified in the validation.
>> Usage of LIKE Expressions in Search Queries
A new endpoint POST /api/dms/objects/{objectId}/contents/renditions/text allows for the import of a text rendition.
If a content file is imported having one of the text rendition compatible formats and containing readable text, a full-text rendition will be created and stored in the Elasticsearch index. The new endpoint posts the plain text passed in the request body to the text rendition property in the Elasticsearch index replacing the current value if already filled before.
>> POST /api/dms/objects/{objectId}/contents/renditions/text
The yuuvis® Momentum core system can be used as basis for apps. Apps are additional logical units that enhance the core system. Apps can be enabled or disabled for individual tenants via app sets. There are new endpoints for system integrators provided by the API gateway that allow for retrieval, validation or update of the configuration files:
An overview of available apps can be retrieved via the following new endpoints of the API gateway:
Errors may occur in many different situations during data processing. In addition to the HTTP status code, yuuvis® Momentum core offers a well-defined structure and labeling of any thrown error. It is thus possible to easily localize the origin of the problem. At the same time, automated catching and analyzing of errors can be implemented based on the fixed error structure and error codes.
>> Error Handling
yuuvis® Momentum offers a property type for the storage of structured data in JSON format. Thus, it is possible to store interleaved data structures in a queryable way without defining each single sub-property in the schema. However, structured data properties should NOT be considered to replace the concept of a well-defined schema. They should be used only if the handling of objects' metadata via the conventional property definitions is not reasonable.
>> Structured Data Properties
>> Example Tutorial
Our set of available webhooks has now a uniform nomenclature and is extended by new webhooks.
>> Webhooks
The following webhooks are new with this release:
The following webhook is deprecated with this release:
T(java.util.List).of(300).contains(options['action'])
".The following changes were made in the naming and behavior of webhooks:
New Webhook Name | Deprecated Webhook Name | Behavior as of 2020 Winter | Behavior as of 2021 Summer |
---|---|---|---|
dms.request.import.storage.before | The import of objects (POST /api/dms/objects) always meets the webhooks with action 100 (OBJECT_CREATED). | Beside 100, 101 (OBJECT_CREATED_WITH_CONTENT) is new, depending on whether the object has content or not. | |
Tag operation endpoints meet the webhook with action 300. | Tag operation endpoints meet the webhook with specific actions instead of 300. | ||
dms.response.objects | - | The import of objects (POST /api/dms/objects) meets the webhooks always with action 100 (OBJECT_CREATED). | Beside 100, 101 (OBJECT_CREATED_WITH_CONTENT) is new, depending on whether the object has content or not. |
A content update (POST /api/dms/objects/{objectId}/contents/file) meets the webhook without action. | It comes with action 301 (OBJECT_DOCUMENT_CHANGED). | ||
The webhook cannot be triggered by a deletion. | The deletion of an object (DELETE /api/dms/objects/{objectId}) or of a version (DELETE /api/dms/objects/{objectId}/versions/{versionNr}) meets the webhook. | ||
dms.response.objects.delete | POST dms.response.delete | The deletion of a version (DELETE /api/dms/objects/{objectId}/versions/{versionNr}) meets the webhook 200 (OBJECT_DELETED). | The deletion of a version meets the webhook with action 220 (VERSION_DELETED). |
In the section for AMQP hooks within the system hook configuration file, placeholders can be used as provided by spring. They can reference values in the system environment including configuration files and command line arguments. The placeholders will be replaced by the referenced values of the environment variable during the starting process of the corresponding service.
>> systemHookConfiguration.json
The USERSERVICE is an additional service providing endpoints for access and the management of user-related information, settings and contents. The endpoints are now available in an additional API providing CRUD (create, read, update, delete) operations on the user-related data.
>> User Settings Endpoints
Since the release of the first alpha version of the USERSERVICE with version 2020 Winter, several improvements were implemented as described below.
In order to protect user-specific settings and content data, users can only access objects that they have created themselves. However, tenant administrators can also access objects stored by any other user within their tenant. The tenant administrators are identified by a configurable role. Per default, the YUUVIS_TENANT_ADMIN role is set.
Furthermore, tenant administrators are allowed to retrieve user-specific personal information.
Users can retrievee their own information by replacing /users/{userId}/*
with /me/*
in the endpoint URLs.
The paging parameters in the USERSERVICE are now consistent with our other public APIs.
Users can retrieve either the content file or only the corresponding metadata by choosing the suitable GET endpoint.
Users can retrieve a list containing all settings and content IDs that they have created themselves using a specific endpoint.
The amount of data stored via USERSERVICE is not counted against a user or tenant limit defined in other services. In order to prevent a misuse of the USERSERVICE, the storage space for JSON settings and binary content is limited per user and per object. The limits can be configured.
The storage consumption can be monitored via metrics.
If users are assigned to a group, the same configuration of roles is assigned to all members. Group assignment can be managed via the corresponding endpoints. If the group is deleted, the roles referenced in that group will be removed from all group members.
groups
is introduced into the profile.There are several new endpoints provided by the Web-API Gateway (API-WEB) allowing for the management of catalogs. The catalogs implement selection lists in metadata forms displayed in clients using our framework library. They are also included in yuuvis® client as reference implementation and can be managed via yuuvis® architect.
>> Catalog Management
Users with the YUUVIS_MANAGE_SETTINGS role are able to add new values and deactivate old values offered in catalog fields.
When users upload a content file, a selection of suggested object types is offered from which the users can choose. For each of them, the probability of fitting is displayed. The suggestions are provided by the new PREDICTION service. Whenever users choose an object type, a feedback information is delivered to the PREDICTION service and thus influences further suggestions.
In the Metadata aspect area of a displayed object, tables can be displayed. The values can be exported via the download icon. A CSV file will be created that can be used for further analyses. If decimals are among the values, they are formatted according to the language the logged-in user has set.
In the Localization view, available language configuration files can be exported as JSON files via the download icon. The configuration file contains key value pairs of technical names based on schema and form modeling definitions, and their localization values in the specific language. The values can be translated externally. The modified configuration file can be uploaded for a custom language.
>> Localization
Selection lists with pre-defined entries can be used in the forms for the properties of your business objects in your client. These selections lists are provided by so-called dynamic catalogs of the Web-API Gateway. Thus, yuuvis® architect allows you to create and modify dynamic catalogs leading to changes in the selection lists displayed in your client.
Global catalogs can be created by users with the YUUVIS_SYSTEM_INTEGRATOR role, tenant-specific ones with the YUUVIS_TENANT_ADMIN role. Tenant admins can copy global catalogs for use of tenant users.
>> Catalog Management
Users logged in as host members are now able to invite further host members that will have the same permissions to manage all organizations. This can be done via the settings menu under Account in the Members view. The listed Members and Invitations are host members.
Host members do no longer belong to an organization.
>> yuuvis® management console
Host members can edit their user-specific data E-mail, User name, First name and Last name via the settings menu under Account. Furthermore, the Language can be set there to either German or English.
>> yuuvis® management console
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. |
LIKE
expressions are allowed in search queries. The LIKE expressions remain limited by a maximum number of 10 included wildcards (%
and _
characters). The limit compliance is verified in the validation. (internal: OKTO-4686)First development steps for storing and searching structured data are planned:
The two weeks from 24 MAR 2021 to 06 APR 2021 will be our innovation sprint that allows us for trying new ideas and exploring new ways for the future. We do not plan to deliver new features in this sprint, but we will fix appearing bugs if possible.
Host and organization members can delete an empty tenant from Keycloak and yuuvis® Momentum. The tenant must not have any users or stored objects.
The API is now public.
/api/user/...
, USERSERVICE endpoints now have the new URL /api/me/...
. (internal: ERA-7771)These initially planned features could not be realized. Some of them are planned for the next version 2021 Autumn.
Users with the YUUVIS_TENANT_ADMIN role can search for users within their tenant. Users with the YUUVIS_SYSTEM_INTEGRATOR role can search for users within a specified tenant.
Technical users can be created together with a new tenant. The technical users have the YUUVIS_SERVICE role which is added to Keycloak, but not to yuuvis® Momentum. Users with this role are excluded from the user lists returned by the endpoints GET /tenant-management/api/admin/users and GET /tenant-management/api/system/tenants/{tenant}/users. Thus, in yuuvis® architect, they are not displayed in the user list of their tenant and cannot be edited.
Users can save a configured set of search conditions in order to apply it again later. A saved search can be added to favorites and shared.
Users can edit Microsoft Office documents and save the modified document in a new version.
Users with the YUUVIS_TENANT_ADMIN or YUUVIS_SYSTEM_INTEGRATOR roles can set the initial language for a newly created user. The corresponding invitation e-mail will be sent in the specified language.
Technical users with the YUUVIS_SERVICE role are not displayed in the user list of their tenant and can thus not be edited via yuuvis® architect.
Users with the YUUVIS_TENANT_ADMIN role can search for users within their tenant. Users with the YUUVIS_SYSTEM_INTEGRATOR role can search for users within a specified tenant.
|
Below you will find information about the provided hotfixes. The latest status about the atrefacts can be bound here: "Version Tags Services".
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|