Release Plan

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 (10.6 - done)

• Microsoft O365 integration for viewing and collaborative editing of Microsoft Office files (10.0 - done)

• The OCR-service supports the use of Tesseract as an alternative for Abbyy Finereader (10.0 - done)

• Systems integration with Insiders smartfix: XRechnung/Factur-X (extraction & viewing)

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 (10.0 - done).

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

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

Highlights after version 10

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

• Systems integration: CMIS (alternative for SAP^® ArchiveLink for SAP^® S4/HANA), Exchange Online (yuuvis^® RAD MAS)

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

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

Open

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.

Next Minor Releases

In the following section, only highlights will be listed.

10.8 – 23 JUL 2024

The focus for this minor release was on bug fixing, so only the following few features can be mentioned:

yuuvis® RAD client

• The client is upgraded to Angular 18 to keep it future-proof.
  (Breaking change: Custom clients must be adapted concerning other used 3rd party components.)

• The version compare area informs the user if table data were changed (bug-fix).

yuuvis® RAD services

• In the servicewatcher-sw.yml file, the web resources are referenced by the variable ${enaio.data.path} instead of the actual path which reduces the administration effort.

10.10 – 20 AUG 2024

yuuvis® RAD client

• The forms are extended with a new form control for the new auto-complete feature which is a better alternative than the dynamic list control. While the dynamic list elements are prepared via form script which is not available in a saved search form and the context search form in the search dialog, the auto-complete elements are prepared in an auto-complete plug-in of the client-service (see this documentation: Auto-complete Plug-ins ). These auto-complete controls are working well in saved search forms and in context forms of the search dialog.
  Two example plug-ins will be delivered as well. The first plug-in reads the list of elements from objects so responsible users within the client can maintain these. The second plug-in reads the list of elements from a JSON file which can contain hierarchical structures.

• When releasing a document lock, a security dialog is offered to inform who locked it and when.

  • If an administrator releases the lock because the user who has locked is not available an audit entry is written.

• When dropping a file on the client, the favored folders and the last opened folders are offered as destinations too.

• In the search dialog, the object count for abstract object types is provided too.

• The widget Signature statistics provides privileged users with the count of given signatures for specified object types, signature types, status, and a time range. The count can be aggregated for a given object attribute.

More new features to come in one of the next minor releases

In this section, other features are documented that can’t be planned for a specific minor release yet but are planned to be delivered with version 10.16 LTS at the latest.

yuuvis® RAD client

• When searching, simple range searches can be used in a date field like yesterday, today, tomorrow, this week, last week, next week, this month, last month, next month, this year, last year, and next year.

• In the inbox, it is possible to return all accepted tasks.

• To reduce the list of object actions for the user, it is possible to configure the client not to offer such depending on custom business logic.

• For compliance regulations, it is possible to add a comment when a document is shared.

yuuvis® RAD services

• The search-service API offers the possibility to search for properties with ‘NOT the given value’ and with 'has a value'.