yuuvis® RAD version 6.0

General

The application server of the service has been updated to WildFly 18.0.1. The new WildFly build brings the usual batch of security patches and enhancements as well as further improvements to custom logging. This version also introduces the basis for a potential upgrade of the Core Service to Java 11 or later.
PostgreSQL 11 Support. As of this version, PostgreSQL 11 is added to the list of the supported databases.
Upgrade to Elasticsearch 7.2. The Index Service, Search Service and Structure Service are based on Elasticsearch 7.2 now. This version offers more secure processing, much more performant autocomplete functionality and optimizations for search including special characters.

Just to inform: With respect to systems with more than 20 million objects some requests to the backend were optimized to reduce waiting time.
The result lists are reworked:
- The browsing through a longer result list has been changed to paging. This leads to a better system performance as well.
- The column menus are cleaned up: only the filter dialog is offered, all other functionalities are available via drag and drop.
In the settings: The enabling of the agent is optimized:
For an object, the icon for downloading its file is also displayed when the agent is connected.
Now one click allows viewing the document file in its application in Windows without being controlled by the agent. This reduces many clicks.
The dialog offered if the user decided to be always asked whether to lock or unlock the object while editing its file is also offered when clicking the pencil icon. This ensures the correct handling of the document lock when using the pencil.

The online help for yuuvis® RAD 6.0 with the Release information and info on Installation and Administration as well as for Developers and Users is now available in German in our Documentation Portal.
(https://help.optimal-systems.com/yuuvisRAD/home_yuuvisRAD_de.html). The English version will follow a bit time-delayed since it has just been handed over for translation.

Folders can be configured. Index data can be changed but without inheriting relevant data to its children.
Next step: configuration of relationships between folder types and object types.
Fields can be classified. This can be used, e.g., in clients to render URLs, e-mail addresses, telephone numbers, user/group references, object references, or catalogs as needed.