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

Stable 1

Bug fixes

• Fixed a problem that occurred when processing calendar and resource periods during scheduling, which could lead to an incorrect calculation of durations. #22089

Base

Attention

• If the update to Server 39.5.25 is to be part of a complete update including database update, the update must not be carried out in one step, but in two individual steps, as described below:
  1. First update the database to the last released DB version, DB 39.5.10 (db.install = yes and server.install = no).
  2. Subsequently update the Server to Release S 39.5.25 (db.install = no and server.install = yes). #21785

Notes

• The update from Venus on Earth to Venus CANNOT be carried out with the S 39.5.25 update packet.
• When updating from Venus on Earth to Venus, the first step must necessarily be initiated from the DB 39.5.10 update packet.
• When updating from Venus to Venus , it is irrelevant whether the two steps are initiated from the DB 39.5.10 or S 39.5.25 update packet. However, the order must be adhered to.

Features

• BETA the new Longest critical path scheduling parameter, with the help of which tasks are marked which lie on the critical path. For more information, see also the CreateCriticalPathDI migration packet. #21471
  • The Longest critical path parameter as well as the Critical path parameter introduced with S 39.5.24 can only be used if the scheduling afterrun in the planta_scheduler.conf is activated.
• The new data field behavior *5 for buttons, links, and context menu entries for direct method call of a Python macro module or a module sub-class has been approved. For more information, see also the PortNewDFBehaviourListboxValues migration packet. #21255
• PLANTA now supports MSSQL Server 2016. See also System Requirements. #21557
• It is now possible to create links between tasks in different data areas graphically, e.g. between gates and task bars in the project schedule or between program tasks and tasks of the program projects in the program schedule. However, in order to use this option with the mere S 39.5.25 server update, you will have to make customizing adjustments. For further information, see here. #21416
  • The Change bar: link bar parameter must be activated in the following modules:
    • In the Schedule module in data area 052104 for DI061285
    • In the Schedule module in data area 054452 for DI002951
• Scheduling Performance Improvements #21437
• By means of keep alive mechanisms with timeout on all connections between the server components, it is avoided that part of a session lasts long beyond its termination. #21054

Bug fixes

• The sporadically occurring problem, that web interfaces under MSSQL did not use the correct UUID has been resolved. #21528
• The problem that there were deviating values in Load (Remaining load) and Period (Planned) after replanning has been resolved. This error sporadically occurred in connection with external links if
  • the TA successor had an actual start date,
  • the TA successor had no split, and
  • the link type was SS or ES. #21588
• Removed the obsolete PortCAPRasterCurves migration packet including the database links. #20794
• A performance problem in connection with groupings in listboxes has been resolved. #21571
  • Now, an already entered part string is also used as an additional search criterion on these fields in the database query if part string search and copying values are set for different data fields.
  • If copying values is set on the determining data item (DDI) of a grouping area, the part string is passed on to the database query of the source area, given that the source area contains a data field with the DDI of the grouping area.
• The problem that the FixPeriodAggregationQuery migration packet failed in some source systems when updating to Server 39.5.24 has been resolved. #21476
• An SQL error which occurred when manually entering the archive_dir interface parameter has been resolved. For a workaround for versions < S 39.5.25, see here. #19622
• If both a group resource and an individual resource have PM profiles set as load profiles (e.g. PM_MONTH), the posted effort of the individual resources is allocated correctly to the group resource or subtracted from its remaining effort. #21545
• The crash which occurred during replanning when there was a project that had cycle structures has been resolved. #21646
• For systems for which the Database changeset field is not filled, no migration is carried out. #21468
• The problem of deviating values in Load (Remaining load) and Period (Planned) after replanning has been resolved. This problem could occur sporadically in connection with external links if the successor TA had an actual start date or no splitting as well as no SS or ES link type. #21588
• The DatabaseError: 'de.planta.server.proto.HandlerException: Error while processing request exception has been resolved. #21500
• When copying records (e.g. via Drag&Drop copying) which contain I-texts, all foreign-language entries are copied as well. #15169
• Resolved the problem that the server crashed when there were mismatching relations to parent areas and reformulated the error message which occurred in this context in a more informative manner. #21799
• The problem that under Linux the server is started with the wrong Java version if the start scripts in <Server-Verzeichnis>\yajsw\bat are started from another directory has been resolved. #21242
• Fixed the Python exception during scheduling which occurred when the checkbox for the Work parameter was activated. #20672

Migration Packets

Category	Packet name	Function	Type	WI
Help packet	FixLoadPeriodDeviations	Corrects possible planned effort deviations between DT472 Load and DT468 Period, which may have come about due to particular constellations when using external links (see also WI19863 in S 39.5.24 and WI21588 in S 39.5.25) . Since the packet uses period summarization and replanning, manual execution should take place within a maintenance window (e.g. following the server update). The packet must be run manually and requires DB 39.5.7. Please consult PLANTA before execution!	Feature	#21127
Mandatory packet	CreateCriticalPathDI	Creates new DIs for the longest critical path in DT463 and 824 (DI064921 and DI064924), with the help of which scheduling marks the tasks which lie on the critical path.	Feature	#21471
Mandatory packet	PortNewDFBehaviourListboxValues	Adds the new DF behavior *5 to the listbox and to the value range on the DF behavior DI.	Feature	#21255
Mandatory packet	MaintainIndexOnDt468	Adjusts the indexes in DT468 for performance improvement.	Feature	#21588
Mandatory packet	ChangeMissingTrafficlightDialogMessage	Corrects the dialog message for missing traffic light DIs.	Bugfix	#20996
Mandatory packet	UpdatePythonIDOfDIsInDT153	Corrects wrong Python IDs in DT153.	Bugfix	#21191