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

Application

Features

• General
  • When reinstalling or updating the database, the system title is no longer set/updated. In the system bar, only the PLANTA project product name is displayed.
  • When updating the database, the following migration packets are no longer executed automatically: ItextCheckPacket and HyperlinkCheckPacket
  • The user menu for the Multi-Project Management, Project Management, Resource Management, Program Management, Employee, and PM Administration roles has been structured more clearly and new panels have been added. The planning and analysis modules are now summarized separately according to their respective function in the Planning and Reports work areas.
• R1
  • In the My Activities modules, no locked todo items and risk and opportunity measures of the projects are displayed.
• R41
  • The new SAP WBS (Application) and Create SAP WBS Elements (Administration) modules have been implemented, which can be used to
    • assign the SAP WBS elements imported from PLANTA link to PLANTA tasks. On this basis, budget, cost, and effort adjustment between SAP and PLANTA project becomes possible.
    • create the alternative project structures. In this case, the creation of the individual elements is done manually.
  • Charts of the Earned Value Analysis in the Status Report module are already displayed before the release of the report.
  • For evaluation and analysis of the project and program opportunities, opportunity matrix diagrams have been implemented in all relevant modules analogously to the risk matrix diagrams (e.g. the Risks/Opportunities module). See also the AddingProbabiltyAndSuccessDimensionDIs_812_872 migration packet.
  • In the Progress module, a new module variant has been added (Costs), in which costs are shown on tasks, and only cost and revenue resources were displayed on resource assignment level.
  • The Project, Idea, Proposal, and Program panels have been streamlined. Several modules have been outsourced to the new Further... module (for projects, ideas, and proposals) or to the Further... module (for programs). Next to the links to the modules of the panels, links to evaluation and overview modules are listed centrally.
  • In the Outline Plan module, the Generate WBS code button has been implemented analogously to that in the Schedule module.
  • Diverse changes have been made to the Schedule module:
    • Changes have been made to module variants.
    • Links on the task ID / WBS code in the Task field have been implemented
    • A Button for generating the WBS code has been implemented.
  • Gates show the intervals to the main milestone in tooltips in the Schedule and Milestone Overview modules for projects, and in the Schedule and Milestone Overview modules for programs. In structured projects with more than 2 levels, only the gates of the main project, and possibly of the program, are displayed.
  • Via the project_parameter_heredity global parameter, you can define whether and which project parameters are inherited from the main project to the subproject when creating a subproject.
  • In the Resource Plan module, some parameters of the resource assignment have been outsourced to the new Resource Plan Complete module variant.
  • In the Project Core Data module, the option to have the reporting of hours worked for a project member done by a person responsible from the Stakeholder area, without having to switch to the employee board of the project employee. For more information, click here.
  • When copying a schedule, the values of the Description and Necessary Requirements fields corresponding to the task are copied as well.
  • After successful creation of the required controlling reports in the Controlling Reports module, a respective note is displayed in the status line.
  • In the Planning Objects (in Table Form) module, fields that are not required have been hidden.
  • The < Critical Projects Projects module has been extended by the My Projects module variant which only shows the projects for which the logged-on user is the project manager.
  • The Budget module has been extendeed by the option to copy costs and effort from the Total costs (without subprojects) or Total effort (without subprojects) columns to the Cost budget requested (without subprojects) or Effort budget requested (without subprojects) columns at once (one arrow more above the Requested (without subprojects) column).
  • In the Deviations module, the Refresh button has been implemented, which is displayed if changes are made in other modules which have an impact on the display of the data in the Deviations module while the Deviations module is still opened.
• R50
  • In the Request module, a functionality that enables you to add stakeholders has been added.
• R60
  • The order of the fields for the evaluation of the objective contribution in the Program Core Data have been adjusted to the Project Core Data.
  • In the Program Core Data module, stakeholders can be generated and assigned from the Schedule.
• R70
  • The user menu of the portfolio manager has been extended by the New Program entry.
  • In the Portfolio module, the summarized risk and opportunity values have been removed from the header area since there is a separate area for risks with detailed information in this module.
  • The procedure (workflow) for the creation of the portfolio status reports has been changed. The configuration of the data (estimations, comments, assignment of status reports to planning objects) is done in the Portfolio Status Reports module. The Edit Portfolio Status Report and Configure Portfolio Status Report are no longer used. For more information, see the Create Portfolio Status Report tutorial.

Bug fixes

• General
  • The size of the Model and Model Parameters module has been optimized.
  • The error message that occurred when clicking on the Home button if no Startup macro was stored for the logged-on user has been resolved.
  • The problem, that invalid date entries in the Approved on, Completed on, and Requested on fields in the Change Request module could not be removed due to their incorrect value range type, has been resolved.
• R41
  • The problem, that the matrix diagram in the Risks and Opportunities module showed incorrect values, has been resolved.
  • The Python error message that occurred in the Earned Value-Analysis module when the module was opened anew and a new status report had been created in the meantime, has been resolved.
  • The problem, that the is not a valid MODE message was displayed when exporting to or importing from Microsoft Project in the Outline Plan module, has been resolved.
  • The problem, that after reloading (F7) the Resource Plan module the links to other modules only opened empty modules, has been resolved.
  • The problem, that the wrong traffic lights were displayed for new tasks in the Dashboard module, has been resolved.
  • All parameters (except calculated dates) of the Milestones/Master milestones module variant in the Schedule module have been set to "input". Furthermore, the Milestone parameter has been included to visualize which of the displayed tasks are milestones and master milestones.
  • The problem, that in the Inactive Projects module variant in the Projects module, archived projects were displayed as well (Status = 9), has been resolved.
  • The problem, that a change to the value in the Forecast field in the Progress module was not represented in the correct color, has been resolved.
  • The problem, that in the Edit Hours to be Worked module, data could be specified in the Hours to be worked: start period and Hours to be worked: End period fields outside the periods defined for the respective resources, has been resolved.
  • The Python error message that occurred when using MSSQL when releasing a phase in the Process Status module, has been resolved.
  • The problem, that no data was displayed in the Budget, Costs, and Revenues (Delta View) module, has been resolved.
  • The problem, that the specifications in the Fast Creation of Employee Data module were partially not copied during transfer, has been resolved.
• R60
  • The problem, that it was possible to insert the dependencies in the Project List module, has been resolved.
• R1
  • The problem with the reselection of the values in the absence listbox of the Absence module, has been resolved.
  • The problem that the Absence+Vacation: sum field in the My Activities module were not displayed for past periods, has been resolved.
• R70
  • The problem, that the Portfolio use field in the Projects, Proposals, Ideas, and Programs modules was not displayed completely in Portuguese, has been resolved.
  • The error in the Portfolio module that occurred when selecting the Delete assignment context menu command on an assigned planning object, has been resolved.
  • The error message which occurred in the Objective Evaluation Criteria when deleting individual criteria, has been resolved.
  • The representation of portfolio status report data in PDF has been improved.
  • The problem, that charts in PDF files, which were created from the portfolio status reports, contained incorrect scale values, has been resolved.
  • The problem, that risk and opportunity charts did not contain any data in PDF documents of a portfolio status report, has been resolved.
  • The order of the planning objects has been corrected.

Customizing and Technology

Features

• General
  • In the Option Module for MV module, the option to filter via the buttons has been implemented analogously to the Filter Criteria module. Furthermore, in both modules the option to reset the changed filter criteria to the default settings (Reset and filter button_).
  • In the Modules module, the opening procedure for old macros has been changed. They are no longer opened via the Edit macro button in the module form, but via the Edit macro lines context menu command.
  • The new Assignment of Print Areas module replaces the previous call of the Modules module and only contains the data areas that are required for the print areas with Positioning = 3 (Print area: header) or 4 (Print area: footer).
  • Deactivated data items and deactivated sub-data items are displayed in gray in the Data Items and Data Areas modules.
  • The listbox in the Language field in the Users module lists all available languages.
• PLANTA link
  • For using alternative project structures with SAP-WBS elements, new Interface Templates have been created for import and export.
  • The PLANTA link modules have been reorganized and structured more efficiently with the new Interface configuration, Interface administration, and Special functions work areas.
    • The Generate Definition module has been renamed Generate Interface Definition.
    • The Configuraation panel has been renamed Configuration and Execution.
    • The Open Transactions and Archive modules have been renamed Open Configurations and Completed Configurations.
  • In the Open Configurations and Completed Configurations modules, the filter criteria has been moved to the lower module area. Furthermore, the functionality to delete log entries and configurations has been implemented.
  • The Configuration and Execution modules have been extended by the Abort threshold (%) and Abort threshold (seconds) parameters.

Bug fixes

• General
  • A problem which occurred when generating automatic numbers for individual tables has been resolved.
  • An error which prevented the analysis of Python profiling data under MSSQL has been resolved.
  • The problem, that the CreateDialogueColumns migration packet failed if the columns to be created already existed, has been resolved.
  • The error message which occurred when clicking on the Project and Report fields in the Edit Status and Status Report Data module has been resolved.
  • The problem, that the link of the Role field in the Object Use - Work Area module displayed all roles instead of the required roles only, has been resolved.
  • The problem, that newly created records were displayed in gray the Data Areas module, has been resolved.
  • Structure errors when saving Python profiler data have been resolved.
  • The error message which occurred when opening the Modules module if the button in the Module was clicked on and the macro contained particular outdated macro commands has been resolved.
  • The problem, that the number of used tasks was not calculated correctly in the License Level module if projects with Status = 2 existed, has been resolved. Only Status = 9 leads to a reduction of the number of tasks. The number of users used is displayed.
  • The problem, that the AddDateShiftProcedure migration packet failed when updating from DB 39.4.4.0 with S 39.5.19 to DB 39.5.8 with S 39.5.20, has been resolved.
  • The problem, that the EnableConstraints migration packet did not run through correctly if constraints could not be activated due to incorrect data, has been resolved. Errors that have occurred are listed in the log. With the help of the SQL statements listed there, the data inconsistencies responsible for the failure of the migration packet can be checked.
• PLANTA link
  • A problem which could cause the interface to hang up on MSSQL systems when transferring several records, has been resolved.
  • The Python error message that occurred when the import of German holidays was carried out by a user for whom "English" was set as the system language has been resolved.
  • The problem, that log entries at the end of a page in the Logging module were displayed again on the following page, has been resolved.

Migration Packets

Category	Packet name	Function	Type
Mandatory packet	ZZZSetDatabaseVersion	Sets the database version to 39.5.9.	Feature
Mandatory packet	SetObsoletePacketToSucceed	Resolves the problem, that the FixViewColumnLength migration packet failed when using MSSQL databases on Linux systems.	Bug fix
Mandatory packet	MoveLogUnsupportedKoAGrCU	Adjusts the Python path of LogUnsupportedKoAGrCU in the migration table. The LogUnsupportedKoAGrCU migration packet is then displayed in the After DB Import area of version DB 39.5.9.	Feature
Mandatory packet	MigrateUsersToCorrectPLANTALinkRole	Changes the role for PLANTA link users which was erroneously used to 01100028.	Bug fix
Help packet	LogUnsupportedKoAGrCU	Logs all modules that use cost type group DIs that are not supported. Fails if any are found.	Feature
Help packet	ListIndividualModWithStartEndPeriod	Lists all individual modules which use DI001230 Start period or DI001231 End period.	Feature
Mandatory packet	FixEmptyCharts	Enables the Earned Value analysis in status reports to display data in the charts even before the release of the status report.	Feature
Mandatory packet	DeleteTargetFolder	Resolves the problem that the MigrateCostsAndBudget migration packet failed if the target directory in the server directory was not deleted during a migration and created anew.
Mandatory packet	AddPSPImportTimestamps	Completes the timestamp columns in table DT461 in order to enable the display of date and time of the last import of the SAP WBS elements.	Feature
Mandatory packet	AddingProbabiltyAndSuccessDimensionDIs_812_872	Adds the required columns for the display of the opportunity matrix in DT812 and DT872.	Feature
Mandatory packet	AddCancelThresholdColumns	Completes required columns in the database for Abort threshold (%) and Abort threshold (seconds) fields in the Configuration module.	Feature