See also:

Release Notes: Version Overview Release Notes: all Server Versions Release Notes of individual database versions: 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.28

Please take the workaround for the problem with persistent database connections into account.

Base

Features

• The license level information has been extended (used languages, extended specification on PLANTA link and PLANTA portfolio) and outdated information has been removed. #24232
  • In the course of the new database release (DB 39.5.14), the display of the license level has furthermore been included in the System Information module. For further information, click here.
• The "urllib" Python module can now be used in Jython files. #24082
• The value range on the DF behavior parameter has been adjusted insofar that symbol 000984 is automatically entered on the respective field and a DF height = 40 is allocated when selecting a DF behavior = "a..." This adjustment serves to optimize the OLE visualization. #23477
• If you try to install a new server into an existing one, or to carry out a plain DB update installation in a directory which does not contain any server, the installation is now aborted and an error message is displayed. #23836
• User accounts can temporarily be activated/deactivated by filling the from/to fields. #7193
• A better error treatment for the installer has been implemented as well as log messages which display precisely when a sub-installer (server/DB, etc.) is terminated. #16511
• The hibernate version used by PLANTA has been updated. Now version 5.3.8 is used. #23473
• When inserting a button DI in a data area, the DF behavior of the respective data field is set to "c4" by default. #24128

Bug fixes

• The input check on the DF behavior field, which is carried out via the value range (due to the removal of input only via listbox in version S 39.5.27), is now complete and correct.
• If you manually run a migration packet which does not fulfill its dependencies with server 39.5.28, no more error occurs in Venus on Earth or Venus systems < DB39.5.6.
• If a module which has overwritten its save function is left with unsaved changes and the following Do you want to save?' message is confirmed with Yes, the overwritten save function is opened again instead of the standard save function. #23961
• No more server error when reading CLOB fields with wrong data. In this case, the data is cut off at the broken character and a log message is written. #24255
• After recreation of the periods and subsequent replanning, the used values (Used (without child resources) and Used) which were deleted along with the periods are now displayed correctly again.
• The problem, that when calculating an individual project the free capacity of a resource was not always determined correctly and therefore overload was displayed incorrectly, has been resolved. The successful run of the CreatePeriodOverloadDI migration packet is a requirement for the new, correct calculation to take effect. For details on both the new and the former calculation procedure, see here.
  • If you update to server 39.5.28, a replanning must be carried out mandatorily afterwards in order for the previously saved overload values to be recalculated and the newly implemented field is filled correctly and thus a correct basis for possible further individual calculations.
  • The new calculation procedure can, be turned off in the planta_server.conf durch by setting the DISABLE_SCHED_FIXES = PERIOD_CAPACITY_CALCULATION_INCLUDING_OVERLOADS if required.

Migration Packets