What Is New in yuuvis® RAD

...

7.0

yuuvis® RAD 67.0 is the newest major version of our rapid application development tool for content-centric applications. It brings several new functions and technical improvements. Here is a brief overview:

• Update of the application server for more fault-tolerance database drivers
• Update of Elasticsearch 
• Update of the search engine for a better and more secure search
• With PostgreSQL, we are supporting a major open-source database engine, reducing total operating costs significantly
• Improved performance through refactoring (core DMS and import, workflow)
• Complete web-based administration
• Improved client and customizing options
  
• client and its libraries to a newer version of Angular
• Optimizations of system maintenance 
  

Technical Improvements

We have updated the application server powering the core service for document management in yuuvis® RAD 6 to the newest available version. Apart from performance gains and security improvements, you can also benefit from new fault-tolerance options such as clustering.

Our search engine Elasticsearch also got a version upgrade in this release. We now provide a faster search, better ranking, and easier cluster management as well as encrypted communication.

We are pleased to announce that we support another relational database engine as of yuuvis® RAD version 6: PostgreSQL. With this state-of-the-art open source database, you can significantly reduce your operating costs for yuuvis® RAD and still enjoy the usual performance.

For version 6, we took some time and performed several refactoring procedures which resulted in more performance in the document management core (faster document import, better scalability in systems with lots of object types and object instances) as well as in the workflow engine (better, faster and more reliable communication when notifying the client). They all result in a smoother experience in evolving systems in which the amount of data and processes increase every day.

Web-based Administration

With this version, we are able to offer you a fully web-based administration of a yuuvis® RAD system. The administration tool enterprise-manager has been discontinued as of this version and its complete functionality is now available in the well-known web-based tool yuuvis® RAD management-studio. Now, you can comfortably administer your system using an easy-to-use web interface. yuuvis® RAD management-studio has all the necessary features supporting you in this version which makes a switch between two tools no longer necessary. Furthermore, thanks to yuuvis® RAD management-studio communicating using REST only, you can now administer hosted or cloud installations remotely with much more comfort.

New Client Functions

The end user experience is very important to us, so we introduced several improvements to our client as well.

The yuuvis® agent for integration with the Windows desktop has been completely reengineered to remove known stability issues. There is no need for “pairing” anymore to enjoy a comfortable integration with the operating system and Office applications. 

New features such as exporting the complete result list into a CSV file or referencing objects as well as searching for the objects to reference (“quickfinder”) enable further analysis of data stored in yuuvis® RAD and improve the productivity by increasing work efficiency. It is now also possible to better compare index data of different object versions in the client. Many further improvements, mostly increasing usability, are also included in this version.

We did not forget about the developers: many smaller but important improvements in the customizing framework have been introduced, such as improved scripting, catalog manipulation in the form scripts. Also lodash.js and moment.js are now available in custom actions. We also made it possible for developers to change the client style without the need to develop a custom client.

For a more complete list of new features and functions in yuuvis® RAD 6, please read the technical release notes accompanying it, visit help.optimal-systems.com and consult the change logs or reach out to your designated OPTIMAL SYSTEMS contactcurrent drivers of the supported databases:

• Microsoft® JDBC Driver 8.4.1 for SQL Server 2019 and former versions
• PostgreSQL JDBC Driver 42.2.18 for PostgreSQL 12 and former versions

We have updated the Search Service, Index Service, and Structure Service for the Elasticsearch version 7.9.3. No reindexing is necessary, but your installed Elasticsearch must be updated as well.

We have updated the client including its library to Angular 11. Be aware that you have to update your custom client and adapt your own components as well.

Performance improvement of the BPM-Service due to upgrading the core-service to Java JDK Version 11.0.9.11. 

Technical Changes

• The URL for calling yuuvis® RAD client as well as yuuvis® RAD management-studio has changed. See here what to do while updating to version 7.0: How to upgrade to yuuvis RAD 7.0
• Changed body for OperationService.listRunningTasks and OperationService.getRunningTask. The produced JSON schema is available as endpoint documentation (REST-WS).

Changes of Labels

• Some labels were changed due to user feedback.

New Maintenance Features

• The session handling is optimized. Current sessions can be monitored on the REST-WS status page. To avoid DOS attacks, the maximum number of sessions for one user can be configured in yuuvis® RAD management-studio.

• You can monitor the technical update tasks on the REST-WS status page.

New Features in yuuvis® RAD designer

• A workflow model can be saved with a single click including all changes in all scripts and forms.

New Features in yuuvis® RAD client

• The decimal values in the CSV export for form table data are formatted according to the language the user has set.
• It is possible to format the process variables that are shown in the title and/or description of a business process, in the same manner as for DMS fields in the title of a document. The default formatting for some fields may be changed in comparison to yuuvis® RAD 6.16, so we advise to doublecheck the titles and descriptions of existing models and processes.
• After successfully saving metadata, no notifications are displyed any longer and do not block certain buttons for a short preiod of time.

Deprecated Functions and Removed Features

• With version 6.0 we announced to deprecate the ETL functionality with version 7.0. It is still available for the SAP integration, but the XML file extraction and script execution functionalities have been removed. You have to migrate your import process to a Talend import process.
  Notice: If you try to import with your old process, you will see an error stating the "Driver can not be loaded" in the ETL log.
  With version 8.0, the entire ETL functionality will be removed because the SAP integration will not rely on ETL anymore.
• Binary fields have been deprecated, since it is better to keep binary content as document payload (its content is searchable, can be rendered) of an object, so its use in projects was extremely rare. Projects that use this type will receive a deprecation warning. The field type will be removed with the next major version of yuuvis® RAD.
• The deprecated functional rights "Assign global roles" and "Edit roles related to global domain" have been removed. These rights will be automatically removed from the server during an update to version 7.0. and they will no longer be included in  system snapshots created from an updated server. However, they may still exist in older projects located on local filesystems. In case that they are still present and an administrator attempts to activate such schemas, the schema and role set validation will show an error – they must be removed from the rights system prior to activating the schema and role set in a yuuvis® RAD 7.0 system or later (or a snapshot of an already updated system should be taken in order to create a project without these rights).
• BPM Script: the deprecated script property process.responsible has been removed. It had been deprecated with the introduction of process.owners which can also be changed (unlike process.responsible which was read-only).
• BPM-Service
  • The deprecated optional parameter "maindoc" has been removed in  the following endpoints of the bpm-service:

    • GET api/bpm/process/{processId}/file - get process file

    • POST /process/{processId}/file/{elementId} - create process file

    • PUT /process/{processId}/file/{elementId} - update element of process file

    • POST api/bpm/process"- get list of process instances that include documents (parameter of call) in their files

  • The following deprecated methods have been removed:

    • GET /api/bpm/process

      • The method GET /api/bpm/processes should be used instead 

    • GET /api/bpm/process/user 

      • core-service method BpmProcessService.getProcesses should be used instead 
• Core-Service

  • The locationinfo parameter for DmsService.getItem has been removed. Use the contextinfo parameter instead.

  • The renditionType parameter for MediaManagementService.assignBinding has been removed. This parameter is no longer necessary and has not been handled in previous versions.

  • The csmeta parameter for ResultService.getEsqlResult has been removed. Use the datameta parameter instead.

  • The internal endpoint InterProcessResourceService.getRendition has been removed.