See also:

Release Notes: version overview Release Notes: all Server versions Release Notes of each Server version: S 39.5.29 / S 39.5.28 / S 39.5.27 / S 39.5.26 / S 39.5.25 / S 39.5.24 / S 39.5.23 / S 39.5.22 / S 39.5.21 / S 39.5.20 / S 39.5.19 / S 39.5.18 / S 39.5.0 up to S 39.5.17 Beta features BETA are not approved for use in a productive system.

Version S 39.5.20

Server

From this server version, there must be a UUID in all data tables. In all existing data tables, these UUIDs are created with the CallOldUuidPacket migration packet.

Features

• BETA Via the new basic technology for web services, generic REST based interfaces can be accessed.
• Performance optimizations have been made in various fields, a.o. to the garbage collection, to the schema validation, etc.
• The behavior of the Reload system customizing menu item and the reload_server() function has been changed and the menu items have been renamed Restart PLANTA service.
  • Note: If you click on the menu item, all open client connections (sessions) are closed. During restart, new client connections are not possible.
• Automatic numbers, that have been generated but not saved, as well as automatic numbers of deleted records can be used again after resetting the counter.
• Relational deletion of parent projects in structured projects has been implemented. It is no longer required to resolve the structure (e.g. in a macro), in order to delete a parent project.
• A Java installation is no longer required, since the PLANTA Server now comes with an own Java version. See also the System Requirements
• At the end of migration, the migration framework outputs whether all migration packets have run through, or at least one migration packet has failed. In case of critical errors, the installation is canceled.
• Foreign Key constraints of history tables now have readable names instead of system generated names.
• Since PLANTA supports Microsoft SQL Server 2014 from S 39.5.19, the MSSQL compatibility mode is set to 100 by the automatic installer upon creation of the DB user.
• The rights for the installation of the PLANTA user via automatic installer under Oracle has been revised.

Bug fixes

• The problem, that the installer possibly got stuck when switching back and forth between installation steps, has been resolved.
• The problem, that the AddServices migration packet erroneously failed, has been resolved.
• The problem, that errors occurred when installing an MSSQL database under Linux, has been resolved.
• Code generated data table aliases now use the ID of the data table instead of the variable name. The appended level suffix therefore does not exceed this very limit for variable names that are close to the maximum limit (Oracle: 30 characters). As a result, the ORA-00972: identifier is too long error message no longer occurs in case of long variable names.
• The Violation of the 'PK_DT503’ PRIMARY KEY restriction. A double key cannot be inserted in the dbo.DT503 object. error message, which occurred when saving module variants in modules that were copied several times, has been fixed.
• Problems with individual Python packages have been resolved.
• The input-file parameter in the import scripts of the Customizing Deployment has been removed.
• The problem, that in special constellations the installation log files were no longer available after installation, has been resolved.

Migration Packets

Customizing Hotfix

Features

• Upon update, the UpdatePeriodAggregationQuery, PortPeriodSchemaChanges, and UpdatePeriodAggregationQuery migration packets now write the current progress in the PlantaServer.log and install.log logfiles.

Migration Packets