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

• When reinstalling DB 39.5.6 with MSSQL and Server 39.5.14, the following script is to be run immediately after the installation in order to guarantee performance improvement.

Features

• The name of a project request cannot be changed manually. When creating a project application, the "Project Application" string is automatically entered in the name field.
• The Project dependency exists checkbox in the Portfolio module is now displayed as deactivated for programs since programs cannot have any dependencies.
• In the Check Database Consistency module the filter criterion that only filters by database instances of the xxB schema has been removed. From now on, all activated database instances of the current license are displayed.
• In the Mapping Parameters module, a link has been implemented on the name of the mapping function that opens the parameter description in Wiki.
• The display control of the resources in the Absence of the Department module has been changed. This is no longer done via the @32 variable on the Resource structure code field, but via @L80 on the Parent resource field.
• If e-mail dispatch was selected when sending a message in PLANTA project, but no e-mail address was selected for the respective user, the The recipient has not specified an e-mail address is output.
• The Resource Plan module for quick view and editing of the resource assignment of the project has been added to the Project panel.
• The module listbox in the Modules module and the Modules Of The Last 30 Days and Macros of the Last 30 Days modules show all modules to which changes have been made in arbitrary areas (e.g. Changes to header data, submodule assignments, data area assignments, etc.).
• Listbox values from the Portfolio data area cannot be deleted if they are already used in the evaluation criteria or risk checklists.

Bug fixes

• The problem, that when using the manual cost input = parameter, the annual values in the Budget module was not summarized to project level, has been resolved.
• The Python error message, that occurred in the Roles module when clicking on the Module column, has been fixed.
• The problem with the incorrect display of the % deviation values in the % deviation field on cost type group level, has been resolved.
• The problem, that a technical module is displayed when trying to assign a project to a portfolio, has been resolved.
• The problem that OS fields are filled incorrectly in DT285 has been resolved.
• Various problems with structure projects have been resolved, e.g., changing the availability of the subprojects in the Check Reported Hours module and the inheritance of the HPR-Status to TPRs, etc., in the watchlist.
• The problem, that in the Evaluation Criteria module several evaluation criteria cannot be deleted at once, has been resolved.
• The Python Exception Python error message, that has occurred due to the non existing entry in the plan_working_hours parameter in the Global Settings, has been fixed.
• The problem, that after creating new projects and carrying out the capacity scheduling without a schedule or single tasks having been created in the Dashboard module, the number of tasks is displayed anyway, has been resolved.
• The problem, that when defining the hours to be worked in the Edit Hours to be Worked dialog module it is not copied from the dialog module to the Resources module, has been resolved.
• The problem, that in the Budget module the values are overwritten on sum level although there are no values in the yearly tranches, has been resolved.
• The problem, that during calculation of the budget of the programs that contain one or more projects with status=9 (Archive) the The following planning objects have been excluded from the calculation because their status has not been set to "active" message is displayed although the values of the respective project are included in the program, has been resolved. The message is no longer displayed.
• The problem with copying schedules has been resolved.
• Missing data in the Cost budget approved active SB total field are now displayed.

Migration Packets