yuuvis® RAD 10 Roadmap

The following information as well as the linked information is intended to outline some of our current product developments for our yuuvis® RAD 10.x.

Like everything else in life, the best plans can change over time. The following article describes the current state of work, but it is important to understand that the details are for information purposes only and are not to be understood as binding commitments.

OPTIMAL SYSTEMS reserves the right to make changes in the planning, development and release of products and their features and functions at its sole discretion.

This page provides an overview of the new features provided with the major and upcoming minor releases and the expected preliminary results provided in our minor releases during the continuous delivery process. We reserve the right to not release a certain minor version due to important reasons.

Table of Contents

Release Plan


PhaseStartEndPlanned Release
Feature Freeze05 MAR 2024-
Tests and Bugfixing08 MAR 202427 MAR 2024-
Master Artifact28 MAR 202429 MAR 2024-

Major Release yuuvis® RAD 10.0-BETA

not for productive use

28 NOV 2023

01 APR 2024

01 APR 2024
Major Release yuuvis® RAD 10.006 MAR 202416 APR 202430 APR 2024
Minor Release 10.417 APR 202414 MAY 202428 May 2024
Minor Release 10.615 MAY 202411 JUN 202425 JUL 2024
Minor Release 10.812 JUN 202409 JUL 202423 JUL 2024
Minor Release 10.1010 JUL 202406 AUG 202420 AUG 2024
Minor Release 10.1207 AUG 202403 SEP 202417 SEP 2024
Minor Release 10.1404 SEP 202401 OCT 202415 OCT 2024
Minor Release 10.16 LTS02 OCT 202426 NOV 202418 DEC 2024

The version 10.16 (LTS) is a Long Term Support (LTS) version, no further increments will be released in the previous 10.x. versions and the 9.16 LTS.


Planned Results

The following features are planned to be delivered with the 10.x release.

While developing new features for this upcoming new major version, the following objectives are our guidelines:

  1. Extending system security and increasing automated tests
  2. Improving user and administrator productivity including documentation
  3. Improving no-code/low-code procedures
  4. Improving OEM capabilities

Breaking Change

  • Implementation of a License Control
    • Starting with version 10.0:
      • Differentiation between named and concurrent user
      • Differentiation between PRODUCTION, TEST, and PROVISION (trial) system with the control of an expiration date
    • Later and step by step: Control of functions like Import/Export (ETL), Signing, OCR, ...

Highlights for version 10

  • Extending the customizable dashboards
  • Microsoft O365 integration for viewing and collaborative editing of Microsoft Office files (version 10.0)
  • The OCR-service supports the use of Tesseract as an alternative for Abbyy Finereader (version 10.0)
  • Systems integration: CMIS, Exchange Online, XRechnung/Factur-X (viewing of XML-formatted invoices)
  • Automation through AI: Automatic classification and indexing of documents
  • (mobile) data access: one-click smart indexing

Helpful minor features

  • The new object-type right Share can be configured for roles in the designer. The client offers the corresponding object-action Share only to users with this right (version 10.0, internal: ).
  • The new string property attribute Autocomplete allows the client to fetch catalog values from a custom microservice. This is an alternative to the string property with the attribute Dynamic list which cannot be used for forms in some cases due to required client scripts. (internal: TUK-19)
  • A new standard document is automatically created when attaching a new file to a process. (internal: TUK-47)
  • E-mails can be sent via Google Mail Service as well as Amazon's Simple Email Service. (internal: TUK-4102TUK-4103)

Highlights after version 10

  • Microsoft Teams integration
  • Data growth/cloud: Improved hosting (Docker), shared elastic search clusters

General

Update of 3rd Party Components

When reaching version 10.16 LTS, all parts of the system will receive updates to keep the system on track regarding support and security, especially:

  • Wildfly Application Service
  • Drivers of the supported databases
  • Spring Boot for service infrastructure
  • Elasticsearch & IntraFind Plugin

Details

O365 Integration

This feature supports users to preview and edit Microsoft Office files that are saved in yuuvis® RAD on the basis of the Microsoft O365 online platform. For editing such a document you need your own account on this Microsoft platform.

Two new microservices are added to the yuuvis® RAD service infrastructure. One is transferring the current file to and from the Microsoft O365 platform. The Dashlet Service offers a previewing interface that is integrated into the client. Collaborative editing is possible as well. The last user leaving the editing session leads the first service to write the file back as a new version.

See Microsoft's Considerations for security and privacy

License Control

This new feature is a breaking change in the general use of yuuvis® RAD. In the past, the system did not control its use by any license key. Beginning with version 10.0 the system will control its use checking a license key that has to be brought into the system. So take care having requested your key from your sales contact before updating the system. The concrete procedure will be described here in the near future.

  • The license key will contain
    • the type of use: PROVISIONAL (initial license), PRODUCTION, TEST
    • the number of named and concurrent users as well as the expiration date until the system can be used in case of a subscription or a trial system.
      • A system that just was installed will contain a PROVISIONAL license which has to be exchanged with a PRODUCTION or TEST license.
  • In the management studio, a named user license can be assigned to a user. The default is concurrent. 
  • License control
    • When the system starts the first time after installation, a PROVISIONAL license is activated and contains 5 concurrent users, 1 named user for the root user, and a maximum of 20 object types to be used. The expiration date is set to one month after the first start of the system.
    • Before the update of a production system, the license has to be requested by OS upfront to keep the downtime short.
      The license request has to include the clusterId of the system that can be fetched from the REST-WS interface in the view 'System information'. This file must be saved in the config folder of the core-system.
    • When the expiration date is reached, the system can be used for an additional 3 days but users cannot create new objects or edit existing ones. After this time, only the root user can log in.
    • Once all named user licenses have been used up in the management studio, no further users can obtain one.
    • If users log in and the number of logged-in users has reached the limit of concurrent users these users will get the info that they have to wait until another user has logged out. Each revised login is written into the security log so it is possible to get a report from it.
  • License management
    • Customer: In the REST-WS interface a new view will show license information, the current license file can be downloaded (the PROVISIONAL license file needs to be handed over to OPTIMAL SYSTEMS to get a PRODUCTION or TEST one), and a new license file can be uploaded and activated.
    • A license file will be generated by a tool that includes specific parameters. This tool will be handled by OPTIMAL SYSTEMS only.
      • After version 10.0: A portal will support maintaining the keys and the installed services can be directly connected.

yuuvis® RAD Services

  • One of the main topics will be the optimization of messaging, especially in case of unexpected environment shutdowns. 
  • The OCR-service supports Tesseract as an alternative to Finereader. (version 10.0, internal TUK-3809)
  • The extraction-service and the viewer-service support files of format XRechnung and Facture-X. (internal: TUK-4100)
  • The search-service will allow users to subscribe for specific searches. Users will receive an e-mail if new or changed objects match the saved search. (internal: TUK-99)
  • The comparison between metadata and document files in versions view is optimized. (internal: TUK-2686)

yuuvis® RAD client

  • We will concentrate on customer change requests related to usability and productivity.
  • The chart widgets will be extended with more specific ways of aggregations.
  • Additional files can easily be attached to a process.

yuuvis® RAD management-studio 10

Step by step, all features of the current yuuvis® RAD management-studio will be migrated to yuuvis® RAD management-studio ng (ng = next generation). yuuvis® RAD management-studio ng will be based on Angular just as yuuvis® RAD client. This way, it can reuse many features of yuuvis® RAD client such as the languages supported, how to extend the application with new languages, how to change the application name, logo, background image, sidebar image, and the documentation URL (OEM aspect). 

Breaking Changes

Besides the above-mentioned introduction of license control, no other breaking changes are known currently, but may come up later and then be listed here.

Major Release

10.0 – 02 APR 2024

Please refer to the /wiki/spaces/onpremise/pages/540213818 for detailed information on this major release.

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 3 months later. (internal: TUK-3662, TUK-3662)
    • 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 3 months and 5 concurrent users.
        • 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
      • 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)
        Activate staged license after upload
    • 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 1 month, 1 week, and 1 day before the expiration date is reached and informs about this situation.
  • 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

  • All services are updated to Spring Boot 3.1.8 to be future-proof.  (internal: TUK-4155)
  • 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, and the o365 service is the interface to the cloud-based OS service that transfers Microsoft Office to its O365 platform for editing.
  • 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
  • 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

  • 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). 
  • 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.

yuuvis® RAD client

  • 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)
  • 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 in 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.
  • 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)
  • It is possible to not offer the object action Share in the object action menu. (internal: TUK-3243)
  • 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)
  • Dashboard and Widgets:
    • 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, MinimumMedian, and Sum. (internal: TUK-4469)
    • For a Chart widget, the order of the partial values can be reverted. (internal: TUK-4469)
    • In the Object count widget, it can be determined whether the number should be shown although it is 0. (internal: TUK-4446)

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 certificate symbol indicates an assigned named license
    • The new object right Share is shown in the table of object type rights within the user details. (internal: ERA-9530)