Valid from 30 APR 2024

Always check: Breaking Changes / Deprecated Features 10.x

yuuvis® core-service

License Management

• After the installation or an update from version 9, a named license is assigned to the user 'root'. This license cannot be removed (internal: TUK-3665).

• The core-service generates a GUID for the environment when starting up the first time and creates the initial license file based on it. This license is of type PROVISIONAL with 5 concurrent users and an expiration date set to 1 month later. (internal: TUK-3662, TUK-3662)
  A system which is updated from version 9.x or earlier will contain a PROVISIONAL_UPDATE license (1000 concurrent users, 1 named user for root user, max. 200 object types, expiration date one month) which has to be exchanged with a PRODUCTION or TEST license.

• When the updated core-service starts, a new license file can be read, validated, and activated. This license file can be requested by OPTIMAL SYSTEMS days before the update by handing over the cluster ID of the system which can be found in the REST-WS interface in the Monitoring view System info. (internal: TUK-4105)

• An OS-internal tool with a CLI (command line interface) supports the creation of license files that are based on the initial license and the necessary parameters. A business process will be introduced for delivering requested license files. (internal: TUK-3663)

  • Three types of licenses are handled:

    • PROVISIONAL: This is a trial license for 1 month, 5 concurrent users ,1 named user (= root user), maximum of 5 object types.

    • PRODUCTION: This license is for productive use, has an expiration date in case of a subscription, and differentiates concurrent and named users.

    • TEST: This license is for test and demonstration use and has an expiration date that allows the use for one year.

    • After reaching the given expiration date, the system can be used for another 3 days. During this time, objects can be searched for and the document files can be downloaded but no new objects can be created or existing ones edited.

  • Later in time, a web portal will be available for the interaction between the requester and OS and if possible between an installed environment and the web portal.

• A new License menu item is added to the Monitor menu in the REST-WS interface where an administrator can download the saved license file, upload and activate a new one, and see current license details like (internal: TUK-3666):

  • the amount of available named and concurred licenses

  • how many concurrent licenses are currently in use

  • the expiration and grant date: when the expiration date is reached the users can search for documents and download the file but can't create new objects or update existing once until the grant date is reached

  • whether it is a PRODUCTION, TEST; or PROVISIONAL license

Click image to enlarge

Open

Type of license

• It is possible to compare the parameters of a new license file with the current one before activating it in the REST-WS interface. (internal: TUK-4256)

Click image to enlarge

Open

Comparing license parameters

• If a new license has a lower number of named users than currently assigned, it cannot be activated. (internal: TUK-4637)

• New REST endpoints are available with a Swagger UI that shows the license data as well and allows to download the saved license file and upload a new one.

• A new REST-WS PUT endpoint ../organization/update/{userid}/named?state=true is available. It allows to change the status of the named license for the specified user. If the status is set to true and the amount of named licenses given in the license file is exceeded, an error is responded and the status is not changed. (internal: TUK-3665)

• The Sessions monitoring view of the REST-WS interface shows information about the active concurrent users. (internal: TUK-4092)

• In the license view of the REST-WS interface, it is possible to initiate a check for a new license against the License-Management-Service and to stage it. (internal: TUK-4268)

• It is possible to get a report about the revised logins for concurrent users who could not log in because no more licenses were available. (internal: TUK-4108)

• The core-service checks a login whether a concurrent user license is available and responds with an error if not.

• After having reached the expiration date, all users can log in for an additional 3 days, but cannot create objects or edit existing ones. Objects can be retrieved or downloaded. Only the root user can still log in. (internal: TUK-3672)

• It is possible to get a list of users with an assigned named license via the REST endpoint GET ../organization/query by using the new parameter namedlicense = true.  (internal: TUK-4098)

• Admin e-mails are sent in the last 30 days before the license expires at the interval defined in the scheduled task "System event information" in Management Studio.

Miscellaneous

• The new object right Share is introduced, so that the object action Share in the client is differentiated from the former coupled right Edit. After the system update, the roles have mapped the Edit right to the Share right. If you want users not to be allowed to share via the object action you have to adapt their relevant roles. (internal: ERA-9530)

yuuvis® services

License Management

• The login page of the gateway-service informs a concurrent user if login is not possible because no more licenses are available. (internal: TUK-3670)

O365 Integration

• Two new services are installed with the service-manager setup:

  • A dashlet-service offers the viewer component that is shown in the client.

  • The o365 service is the interface to the cloud-based OS service that transfers Microsoft Office to its O365 platform for editing.

Miscellaneous

• All services are updated to Spring Boot 3.2.3 to be future-proof.  (internal: TUK-4155, TUK-4375)

• After installation of the service-manager, the OCR service starts up using Tesseract. It is possible to configure that Abbyy Finereader is used instead of Tesseract. The trained languages which are supported after installation by default are the same that can be configured for Elasticsearch (see the packages for Europe & USA as well as for Asia).  (internal: TUK-3809)

• During the service-manager installation, the IP-whitelist is configured in the application-prod.yml instead of the dms-prod.yml, so it affects all services. (internal: TUK-2357)

• The search API supports metrics in sub-aggregations. How to do this and how the results look like can be read here: Useofsub-aggregationcombinedwithmetrics . (internal: TUK-3710)

yuuvis® RAD designer

License Management

• If the designer needs a connection to the backend a user account should be used with a named license to avoid login issues. If a connection is established and no further license is available no login is granted.

Miscellaneous

• In the roles section, an additional object-type right Share is introduced that provides control over who can share documents in a system. In version 9, the object action Share was offered to users with the right Edit. (internal: ERA-9530).

yuuvis® RAD client

License Management

• If a user without an assigned named license logs in and all concurrent licenses are in use, the user is getting a notice and will not be able to open the client. (internal: TUK-3668)

• The client shows a notification if a PROVISIONAL or TEST license is used. If the license has an expiration date, a notification with this date is shown during the month the license expires. (internal: TUK-4030)

O365 Integration

• If a Microsoft Office file should be previewed, the new O365 Integration services are supporting the user. In the preview area, a dashlet is offering the rendition that is based on Microsoft Office sources.

• Users with edit permissions for the corresponding object are offered an edit action that opens a new browser tab with the file opened on the Microsoft O365 platform. More users can enter and work collaboratively on this file. If the last user is closing this O365 tab the file will be saved back as a new version for the object. The client will refresh the object details, so the preview will show that new version as well.

Dashboards and Widgets

• It is possible to reset the dashboard to default. (internal: TUK-4671)

• The Hit list or hit count widget is split into two widgets: Hit list and Hit count. (internal: TUK-3934)

• In the Hit list widget, it is possible to determine the properties to be shown as the first, second, and third label. (internal: TUK-3627)

• In the Chart widget, two new chart types Line - straight and Line - curve are offered for a Property for aggregation that is of type date or datetime.  These chart types connect the dots with straight or curved lines. (intern: TUK-3911)

• The Chart widget can be configured with a selected Attribute for aggregation of type decimal by specifying an Interval size like 100.0 and a Starting point like 10.0 to be shown. (internal: TUK-3695)

• The Recently edited and created objects widget can be configured and the results previewed. It can be decided whether to show only the recently edited or the recently created objects or both, the number of objects to be listed, and the sorting can be reverted. (internal: TUK-4284)

• It is possible to set up Chart widget legends for the x-and y-axes as well as for the chart. (internal: TUK-4404)

• When creating a Chart widget with an Attribute for aggregation of type number, appropriate Starting point, Interval, and Partial values are offered. (internal: TUK-4322)

• The Chart widget supports sub-aggregations for Attributes for metrics of type number. The following Metric can be selected: Average, Maximum, Minimum, Median, and Sum. (internal: TUK-4469)

• For a Chart widget, the order of the partial values can be reverted. (internal: TUK-4469)

• For a Chart widget, a threshold can be set to not show counts that have less objects. (internal: TUK-4500)

• In the Object count widget, it can be determined whether the number should be shown although it is 0. (internal: TUK-4446)

• The Task list widget is optimized regarding its look & feel and especially regarding the saving of its data. In version 9 that data was only stored in the local browser cache. So the data was not available on other workstations. The widget of version 10 saves data centrally now so that it is available on other workstations or browsers as well. However, when updating from version 9 to 10, the old data will get lost. (internal: TUK-4532)

• The Image widget is optimized regarding UX. (internal: TUK-4612)

Miscellaneous

• The Angular framework that is used has been upgraded from version 15 to 17, the 3rd party component ag-grid has been upgraded from version 22 to 31. (internal: TUK-4229)

• Beginning with this version, the object action Share is only offered to users if they have the new right Share. In version 9, this action was offered to users with the right Edit.  (internal: TUK-3243)

• In the hit list view, after saving the changed object metadata, the corresponding hit list row is updated. (internal: TUK-4044)

• In the search dialog, the order of the object groups can be changed by clicking on a forward or backward icon. This feature increases the productivity of the users who have many object groups and often have to scroll through the search dialog. (internal: TUK-3125)

• In the object details header, an icon indicates whether this object is part of an active process. (internal: TUK-3415, ERA-9583)

• The sorting for a form table as well as for the table in the edit dialog is remembered locally. (internal: TUK-2479)

• In the settings, the Cache part is removed and a Reset to default button is added to the part Local settings (internal: TUK-4399)

• Users can get specific information on how to fill a form field. This description can be changed via form script. (internal: TUK-4577)

• The responsiveness of the app bar is optimized. If the width of the browser gets smaller the symbols are vanishing: first, the license information, then the symbols near the profile image, and at the end the logo. (TUK-4769)

yuuvis® management-studio

License Management

• In the Organization view, the actions Assign named license and Remove named license are offered for a user who is not 'root'.

• If the given amount of named licenses is reached, assignment will not be possible (a notification is displayed).
  In the list of organization elements and in the header of the user details, a symbol is indicating an assigned named license. (internal: TUK-3665)

• The operation License check supports continuous requests to the new cloud-based OPTIMAL SYSTEMS License-Management-Service. It queries whether a new license file is available for this system and informs you by email. This helps to shorten the process of adding a new license to the system, if allowed. (internal: TUK-4259)

• The new object right Share is shown in the table of object type rights within the user details. (internal: ERA-9530)