See also:

Release Notes: Version Overview Release Notes: all Database Versions Release Notes of individual database versions:

DB 39.5.16 / DB 39.5.15 / DB 39.5.14 / DB 39.5.13 / DB 39.5.12 / DB 39.5.11 / DB 39.5.10 / DB 39.5.9 / DB 39.5.8 / DB 39.5.7 / DB 39.5.6 / DB 39.5.5 / DB 39.5.4 / DB 39.5.3 / DB 39.5.2 / DB 39.5.1 / DB 39.5.0

Version DB 39.5.16

Attention

• If you use web interfaces and have updated to DB 39.5.16, please replace the serviceprovider.jar, which is located under /jars/webservice_infrastructure in the server directory, by the new one, which is made available in the Serviceprovider.jar folder on the PLANTA transfer server.

Application

Features

• General
  • The preparations which are required for the implementation of the extended time recording function (recording on PLANTA pulse and PLANTA project elements) when using PLANTA Hybrid, have been made on the part of PLANTA project.

• Project
  • The layout of the status and status report modules for projects and programs has been stretched resulting in an optimized print output. #24891
  • In the Projects: 2 Groupings module you can now expand structured projects in order to have a closer look at the subprojects. #24784
  • When creating the person attributes, e-mail-addresses are now automatically transferred from the person to the "User" and "Stakeholder" attributes. #25100
  • In the Program Applications module of a program, the date of the project status reports is now displayed as well. #24832

Bug fixes

• General
  • Reverse postings in the load_creation_variant = 1 and load_creation_variant = 2 time recording variants with existing remaining effort on the resource assignment now work correctly. #25028

• Project
  • The check for "inactive" project status in time recording now works correctly. Projects which are set to "inactive" with postings in the selected week are now listed correctly under "Not postable objects (selected week)". #25037
  • The cause of the Python error message which occurred when opening the All resources module variant in the Resource Planning module has been eliminated. #25099
  • The link on the Project status report field in the Program Status Report module now works again. #24994
• Portfolio
  • Subprojects can no longer be assigned to portfolios. #24914

PLANTA link / PLANTA Hybrid / Jira Interfaces

Features

• The necessary preparations for the implementation of automatic reverse postings in the Jira interface have been made. The complete functionality is provided with S 39.5.30. #24926
• Transformer in PLANTA web interfaces now support relative parameters analoguously to the mapping parameters in PLANTA link. For more information, see here. #24986
• The UUID listbox in the Web Interfaces module has been designed more clearly. #24971
• The attributes of a web entity now have a consistent order which is also reflected in the order of the .json fields in the standard GET implementation. See also the AddWebAttributePositionColumn #24973
• Transformers in the PLANTA weblink can now distinguish whether they transform a value which stems from an external system for PLANTA project, or whether they transform a value from PLANTA project for an external system. This change does not apply to existing transformers. They function equally in both directions, just like before. #24978
• On a web attribute you can now distinguish between a mandatory field for a POST or for a PUT request. As a result, the same web entity can be used for different methods. See also the AddNewWebAttributeMandatoryColumns #24979
• When a task is synchronized to PLANTA pulse, its calculated dates are now applied as due dates for the respective board. #24945

Customizing and Technology

Features

• When using time recording variant 3 (postings directly in posting records), reverse postings are now controlled automatically via Jython events.

Bug fixes

• Sporadically occurring problems with data field positions when using PosRefresherApplicator have been resolved. #24941
• The problem with corrupt data after update due to incorrectly defined constraints in older position conflicts no longer occurs. See also the ChangeConstraintOnConflictMapping and GetRidOfOldPosConflicts migration packets #24961 #24958
• The cause of the error message which occurred when clicking on the Display work area button in the Object Use module has been eliminated. #25094
• The "today" default value on the up to field which was displayed when importing the employee data via the Fast Creation of Employee Data module has been removed. 25025
• On several bar DIs in DT466, which represent the project code, the correct default symbol 001265 is used now. #24891 #17707
• The event tables are now considered in updates to a new DB version instead of being skipped. #24981
• The constraint_exists method of the SQL packet class now also finds DEFAULT constraints under MSSQL #24976
• An error which occurred in the license check when using "0" as a value, has been fixed. Furthermore the permitted exceedance limit is no longer displayed in the License level field. #24965

Migration Packets

Category	Packet name	Function	Type	WI
Mandatory packet	AddIndexForSlowEndpoints	Adds indices for particular end points (relevant when using web interfaces)	Feature	#25054
Mandatory packet	GetRidOfOldPosConflicts	Removes possible old corrupt position conflicts	Feature	#24961
Mandatory packet	ChangeConstraintOnConflictMapping	Adds 'on delete cascade' to constraints	Bugfix	#24958
Help packet	CreateP21	Creates user P21 if it does not exist after update	Feature	#25067
Mandatory packet	AddPrimaryKeyConstraintToEventsTable	Inserts missing primary keys for the EVENTS tables.	Feature	#24966
Mandatory packet	ChangeNameOfConstraintOnTypeColumn	Changes the constraint name of the TYPE column in DT123	Bugfix	#24974
Mandatory packet	AddWebAttributePositionColumn	Sets the position for attributes of a web entity.	Feature	#24973
Mandatory packet	AddNewWebAttributeMandatoryColumns	Declares web attributes as Mandatory field PUT and Mandatory field POST if the Mandatory field field was active before.	Feature	#24979