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.29

Attention

• The installation of Server 39.5.29 requires the configured license file which is stored on the server. See also the first entry under features.

Stable 5

Attention

• This stable is no overlay but an outright stable. It contains all previous stables and can be installed without having to import another stable first. However, a reversal migration packet must be run after installation. For further information on this, please refer to the readme file for stable 5 in the download directory of server 39.5.29.

Feature

• Oracle Driver has been updated to OJDBC10. The note in System Requirements for supported DBMS of versions 18c and 19c, that databases for these DBMS versions are to be compatible with jdbc6 therefore is thus omitted. #25355

Bug fixes

• When using SSL for webservices (ssl_generic_enable =true parameter), the host entered in the web.ini now works correctly. #25358
• The cause of the javax.persistence.EntityExistsException error message which occurred when deleting resource assignments has been eliminated. #25340

Stable 4

Information

• For a detailed installation guide for stable 4, please refer to the readme file in the stable 4 download folder.

Bug fixes

• A class cast exception of PLANTA server thread which occurred during web requests has been fixed.
• An error which occurred when deleting records which are associated with events, e.g. when deleting particular resources, has been resolved. #25171

Stable 3

Attention

• The installation procedure for stable 3 deviates from the usual procedure.
• This stable is a so-called overlay stable. An installation of stable 1 or stable 2 is required for the installation of stable 3 (the basic installation of Server 39.5.29 is not sufficient in this case), which only contains exchange files as well as a migration packet which should be downloaded and run manually.
• For a detailed installation guide for stable 3, please refer to the readme file in the stable 3 download folder.

Bug fixes

• Problems with memory leaks, which occurred during the communication of the PLANTA Server via web interfaces, have been resolved. #25003
• Data events are now also executed when saving via webrequests #25045
• Manual and automatic reverse postings are now supported in time recording of PLANTA Hybrid in versions from DB 39.5.16 as well. #25220
  • This requires the execution of the AddSuccessorBookingColumn migration packet in the stable 3 folder as well as the exchange of some files.

Stable 2

Bug fixes

• Installation under Windows no longer fails on some Windows systems if the "Checking if MS C++ Redistributables are valid" step is carried out. #25073

Stable 1

Feature

• In the case of an exceedance of the license limit, all users are now repeatedly (every 10 minutes) informed on this exceedance by a respective message. #24966

Bug fixes

• An error, which caused that no data was displayed in the case of some rare, complex file constellations which contained many SQL parameters and a fulfillment in their customizing, has been fixed. #24959
• In a mere server update (without DB update), it is no longer erroneously presupposed that the system has an outdated customizing which forces Python 3.4.3. #24956

Base

Features

• The output of license information in the License level field in the System Information module (CTRL+B) now contains specifications on the licensed and currently exhausted volume. If overrun is about to occur, the customer will now be informed on this by respective messages. #7485 #24758 #24737
  • Warning: The components licensed by the customer and their volumes must be specified in the license.conf configuration file and be stored on the server. This step is only obligatory from Server 39.5.29. * If no customer-specific license file is stored, the server accesses the file stored by PLANTA by default with standard values. This file may fall far below the volume licensed by the customer. If you have any questions, please contact your PLANTA consultant.
• For Linux systems, SAP-dll (nwsaprfcutil.cpython-36m-x86_64-linux-gnu.so) has been added, which is compatible with Python 3.6.0. #24833
• Greater performance gain in SQL statements and in large amounts of data were achieved. #24894
• Performance improvement in Drag&Drop operations has been achieved since listboxes are now only checked if they are set to “listbox only”. Incarnations are no longer taken into account. #24936
• Preparations on the server side for the implementation of the freely programmable events were carried out. They are to offer an option to open arbitrary functions (in Python, Jython, or Java) with fixed parameters and thus to ensure further flexibility of the customizing. #12399

Bug fixes

• The error, that after closing the client session a thread remains in the storage if the schedule_enabled parameter in the planta_scheduler.conf config file is activated, has been fixed. In the case of Java memory errors, a head dump is now created automatically. #24366
• In the case of a client crash during scheduling, locks on resources (in the storage & on the database) are reset correctly. #24385
• Persistent DB sessions are now functional again. #24629 More Information

Migration Packets

Category	Packet name	Function	Type	WI
Mandatory packet	PortNewLicenseVisualization	Enables the visualization of the license information from the license.conf	Feature	#24758