Roadmap 10.x

 

This roadmap is not a binding commitment.

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.

Release Plan

Phase

Planned Release

Phase

Planned Release

Major Release yuuvis® RAD 10.0-BETA
(not for productive use)

02 APR 2024

Major Release yuuvis® RAD 10.0

30 APR 2024

Minor Release 10.2

skipped

Minor Release 10.4

28 May 2024

Minor Release 10.6

25 JUN 2024

Minor Release 10.8

23 JUL 2024

Minor Release 10.10

20 AUG 2024

Minor Release 10.12

17 SEP 2024

Minor Release 10.14

15 OCT 2024

Minor Release 10.16 LTS

18 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 results are planned for the 10.x release:

  1. Extended system security and increased automated tests

  2. Improved user and administrator productivity, including documentation

  3. Improved no-code/low-code procedures

  4. Improved OEM capabilities

Breaking Changes / Deprecated Features

Breaking changes and deprecated features are documented in this section.

Planned features/updates for version 10

Highlights

Major highlights

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

  • One-click smart indexing: A click or touch on a string in the PDF-based preview transfers it to the focused form field.

Other helpful 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.

  • A new standard document is automatically created when attaching a new file to a process.

  • E-mails can be sent via Google Mail Service as well as Amazon's Simple Email Service.

Highlights after version 10

  • Automation through AI: Automatic classification and indexing of documents

  • Microsoft Teams integration

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

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

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

 

image-20240418-095749.png
Architecture

 

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_UPDATE license which has to be exchanged with a PRODUCTION or TEST license.

    • The clusterID of the system is created while the database is set up during the installation.
      Remarks:

      • If the database is set up again, another clusterID is created and a new license file is needed.

      • In all of the following cases, no new license file is needed:

        • Change of the number of CPU

        • Change of the RAM memory

        • Change of the network MAC address

        • Addition/removal of the network card

        • Relocation of the virtual machine to another physical server

  • 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 5 object types to be used. The expiration date is set to one month after the first start of the system.

      • In case of an update, a PROVISIONAL_UPDATE license is activated and contains 1000 concurrent users, 1 named user for the root user, and a maximum of 200 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.

Planned Features/Updates per Component

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)

  • The extraction-service and the viewer-service support files of format XRechnung and Facture-X.

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

  • The comparison between metadata and document files in the versions view is optimized.

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

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

Release Notes of version 10.0

For the complete feature set coming with version 10.0 consult this article:
https://yuuvisdevelop.atlassian.net/wiki/spaces/onpremise/pages/701431811

Planned features/updates for version 10.4

yuuvis® RAD client

  • When creating a Chart widget with an Attribute for aggregation of type number, appropriate Starting point, Interval, and Partial values are offered.

  • For a line Chart, a number attribute can be selected for aggregation.

  • In the folder view, strg + left mouse click on a list item of Most recent changes or Latest edited opens it in a new browser tab.

  • The position of notifications is changed so they do not overlap the form buttons.

yuuvis® RAD designer

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

Hot Deployment

  • The service-manager setup offers a hot deployment of the managed services. This means that if only the managed services have to be updated it is no longer necessary to stop the service-manager first. So there is no real downtime in this case. The administrator is informed whether the service must be stopped or not.

Planned features/updates for version 10.6

yuuvis® RAD client

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

  • In the object aspect Summary, the context fields of the folder are shown.