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

• Programs have been added to the Overview by Type module and the new Programs submodule has been added to the Projects, Proposals, Ideas, and Programs panel.
• The new Assignment: User to Role module has been added to the Administration panel.
• The Refresh button has been delted from the Portfolio Status Report module.
• The Recalculate button in the Budget module carries out a capacity scheduling as well now.
• In the Work Reporting module, the tasks finished in the current week are displayed separately below the Finished tasks of the current week heading.
• If a Left on date is set for a resource, the End period field is automatically filled with the same date.
• If a module does not yet contain a Python macro and if the Python Macros module or the Python editor from the Modules module is opened for this module, you can define whether a macro template is to be copied in or not by confirming the Yes/No query in the displayed dialog message.

Bug fixes

• The error message which occurred when trying to create a status report in a program without carrying out a budget scheduling while the projects assigned to the program contained budget data, has been resolved. Reason: Missing data in DT835
• The problem with saving newly created notes and dashboard entries in the Documents (Project) and Documents (Program) and Documents (Request) modules has been resolved. For this purpose, see also the SaveNotesIsNotPossibleInModuleDokumente migration packet.
• In the Cost Posting module (formerly Material Cost Posting), only cost resources (resources with Resource Type=9) can be selected now.
• The problem, that only 4 standard categories are displayed in the Evaluation data area (company risks) in the Project Core Data module and no individual ones, although individual ones have been created in the portfolio master data and included in the required checklist in the Risk Checklist module.
• The validation of the e-mail address has been deactivated in PLANTA project so that when sending a password to an e-mail address with invalid characters, no Python error message is displayed.
  • Since e-mail addresses are no longer validated, PLANTA project administrators must make sure that the e-mail address is entered correctly, otherwise the recipients in question do not receive any e-mails (e.g. in the case of a password change).

Migration Packets