What Is New 9.0
What Is New in yuuvis® RAD 9.0
yuuvis® RAD 9.0 is the newest major version of our rapid application development tool for content-centric applications. It brings several new functions and technical improvements.
Technical Improvements
We updated the WildFly application service as the basis of our core-service to version 27.
We updated the current drivers of the supported databases:
- Microsoft® JDBC Driver 10.2.1 for SQL Server 2019 and former versions
- PostgreSQL JDBC Driver 42.5.1 for PostgreSQL 15 and former versions
- ORACLEDB JDBC Driver 21.8.0.0 and former versions
We updated the search-service, index-service, and structure-service for Elasticsearch version 7.17.8 and the IntraFind Linguistik-Plugin 17.6.2. The installed Elasticsearch must be updated as well.
We updated all microservices to SpringBoot 2.5.8 version with SpringDoc and Swagger-UI, and adapted all services including the admin-service. In the future, we will waive the OS look and feel of the corresponding user interfaces here.
The name and icon of the service-manager executable are changed now.
New Features
Please refer to the Technical Release Notes for a detailed overview of all new features of this major release.
Breaking Changes
- Version 9.0 introduces a new field type: Sets of elements. In previous versions, the Set functionality was provided by single-column tables. When updating to version 9.0, the single-column tables will be automatically converted to sets, both for in-server schema and object instances.
Please note that just as in the previous major version updates, locally saved projects are not automatically updated when installing yuuvis® RAD designer 9.0 (we prefer to give users full control over versions of the projects kept locally on disc). So, in order to obtain the new schema definition for further use in yuuvis® RAD designer, the core-service needs to be updated to version 9.0 and then a new snapshot has to be created in yuuvis® RAD designer 9. - A bug fix (internal: ERA-9302) corrected the previous behavior in endpoints for project management and model information. Previously, if endpoints would be invoked with unknown API parameters, they were silently ignored, leading API users to the conclusion that they have an effect in the call. Beginning with version 9.0, this behavior was corrected and the server will respond with the message '
400 Bad Request'if the request contains unknown parameters. - A bug fix (internal: ERA-9303) corrected the behavior of endpoints for suspending (POST bpm/process/<processId>/suspend), resuming (POST bpm/process/<processId>/resume), and terminating (POST bpm/process/<processId>/terminate) of a process instance. Previously it was returning the number of affected processes (this was always one). From version 9.0, no payload is returned and instead the HTTP codes communicate the outcome of the operation: 404 if process not found, 409 if process in illegal state for the operation, 200 if operation was successful.
- A bug fix (internal: ERA-8889) GET /processes and GET processes/<processId>/history return a 200 with empty list if no processes / no history entries for a process are found, to make it consistent with remainder of API. Previously, a 204 NO CONTENT was returned.
- A bug fix (internal: ERA-8888) was implemented so that returned HTTP response codes and error codes are consistent with the remainder of the API. We recommend our customers to doublecheck whether their custom components or scripts are affected by these changes.