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

Application

Features

• General
  • The Data Field Information module has been extended by the SQL ID and DB schema columns. Furthermore, the data item structure is now displayed in this module.
  • By replacing the previous histogram DIs (DI023419/DI002491) and the DIs for planned effort (DI023362/DI002508) by the new DI063981 which combines the histogram bars, new tooltips (with values and bar name) and effects (lines of availability before utilization) are set for the respective data fields.
  • The stop watch in the user menu has been hidden and will be deleted in one of the upcoming releases. In order to be able to use the stop watch in the future, DA042805 can be customized and assigned to the user menu.
  • General performance improvements could be achieved (e.g. in the User Menu, Multi-Project Board) due to
    • Changes made to several Python value ranges
    • Caching of the get_global_setting() function
    • etc.
  • In the title bar of the Project, Proposal, Idea, Program, and Request panels, the functional ID of the opened planning object is displayed in addition to the panel title.
  • An option to version stakeholder data has been implemented (DT532). Since, however, initially the versioned stakeholder data is not contained in any module, an individual module must be created for this.
  • All auto numbers for process model tables and objects now contain the system license.
• R41
  • In the Project Core Data and Select Stakeholders modules, stakeholders are now displayed sorted.
  • The dialog message in the Edit Hours to be Worked module has been adjusted.
• R1
  • The problem with the wrong traffic light display in the Work Reporting module, in cases in which the hours to be worked and the reported hours worked contained decimal places, has been resolved.
• R70
  • The performance of portfolio status reports has been improved.

Bug fixes

• General
  • Problems with the display of text in e-mails when clicking the mail link in the Info module due to the use of a wrong coding has been resolved.
  • The problem, that by creating a module variant and subsequently selecting the Basic module variant, the rights of a user without modification access was changed in the Idea Core Data, Proposal Core Data, Project Core Data, and Program Core Data modules.
• R41
  • The problem, that after detaching a subproject from the project structure, the respective subproject was not displayed in the status reports that have been created before the subproject was detached from the structure any longer either, has been resolved.
  • The problem, that the baseline was missing in cost and effort trend charts after the Earned Value Analysis active parameter was deactivated and reactivated, has been resolved.
  • The problem, that drawing bars below the Overview by Type module was enabled, has been resolved.
  • The problem, that the cost and effort trend charts in the Status module were not updated after a new status report had been created in structured projects after the Update button was clicked, has been resolved.
  • The problem, that the end date deviation in the Schedule module is calculated incorrectly, has been resolved.
  • The problem, that the NPV and NPV (without subprojects) fields in the Project Core Data module were not calculated correctly, has been resolved.
  • The problem, that after inserting an individual process step in the Process Status module, the respective process phase was displayed twice in the process bar, has been resolved.
  • The problem with the incorrect sorting of the Process Status module has been resolved.
• R1
  • The problem, that submission and approval process steps in the My Activities module were opened in a process step data sheet module and set to "completed", and the process step workflow could therefore not be continued, has been resolved. Now the links open the Process Status module of the project on these process steps, in which the submission and approval process steps of the workflow can be deleted.
• R60
  • The problem, that additional colored frames were displayed below the bar symbol in the Schedule module are not displayed in the Activities section, has been resolved.
  • The problem, that the deactivated Risks and Opportunities of a program were furthermore displayed in the Status and Program Status Report modules anyway, has been resolved.
• R70
  • The problem, that the release could be canceled for project status reports that were already used in portfolio status reports, has been resolved.
  • The incorrect calculation of the percentage deviation (DI061249) in the Effort area in the Portfolio and Portfolio Period modules has been corrected.
  • The problem with the Python error message when deleting an evaluation criterion in the Evaluation Criterion module has been fixed.
  • The error message which occurred in the Portfolio Status Report module after clicking on the Report as a PDF (with planning object reports) button has been resolved.
  • The problem, that when attempting to cancel the creation of a portfolio status report PDF file (Cancel button in the save dialog) the file was created anyway, has been resolved.

Customizing and Technology

Features

• General
  • Due to the changes made to the customizing of histogram DIs, the sorting of the child data items is changed in the parent data item. Now, the child DIs are firstly sorted by the Further parameters, secondly by the Pos. parameter, and thirdly by the DI ID (SUBDI).
  • When reinstalling the database (for security purposes), the AFTER LOGON ON DATABASE log-on trigger is no longer created by the system. The functionality has been replaced by the AFTER LOGON ON SCHEMA trigger. It must be created by the local database administrator him/herself once after the installation. Further information).
  • For many older standard DIs, missing column types have been replenished.
  • The Data areas without Assignment module has been renamed Data Areas not Assigned to Modules and is available in the Customizing Objects without Assignment panel along with the Modules not Assigned to Work Areas and Exits not Assigned to Data Items modules.
  • The option to include data tables in the status report creation without requiring the data tables to have the project ID in their primary key.
  • New mi and mo data field behaviors for mark down data fields have been implemented.
  • Several improvements and extensions in the Object Use module, e.g.
    • The retrievability of the searched objects has been improved
    • Status messages have been implemented
    • The output of the search results in Python code has been extended.
  • In the Filter Criteria module, the Filter from and Filter to values and their values for virtual data items are stored in red, in order to distinguish them from the real data items, analogously to the Option Module for MV and Data Areas modules.
  • In the Filter Criteria module, no data items on which filtering is not possible (DIs with DF behavior "a", "c", "ba", "hk", "d", "py".) are displayed even if the Filter criteria checkbox has been activated for them in the customizer.
  • In the Option Module for MV module, the reference module and the selected module variant are displayed in the module title as well now, just like in the Filter Criteria module.
  • The previos Log work area has been renamed Performance
  • Both the Python profiling dialog and the Python profiling itself have been revised. The workflow now works via a dialog module. The option to let the performance counting run along has been replenished. The results of the profiling can be analyzed in PLANTA project in the Python Profiler module.
  • The Performance History Evaluation module has been revised. Modules are now linked.
  • The new System Environment enables you to check the latency to the database.
• PLANTA link
  • The log is extended by causes for non-imported individual subclasses or mapping functions in PLANTA link. If several mapping functions are used, respective log entries can possibly be created multiple times in a row.
  • The performance of PLANTA link has been improved at several points. In the Generate Definition module, users with customizing rights can measure the performance of PLANTA link using the Execute benchmarks button.
  • The error treatment in PLANTA link has been improved.
    • The wording of particular dialog messages has been improved (made more explicit).
    • If PLANTA link cannot read a certain value from the corresponding data field, e.g. because a computeOutput value range has been customized incorrectly, this field is now listed in the log file.
    • A message has been implemented, which indicates that no CSV file was written since no data has been exported. The message is written in the log file.
  • PLANTA link now also accepts system variables as parameters. In this context, the template for the Employee import interface is adjusted insofar that the default value @15 is automatically set for all fields that have a start and end date, if no value is delivered for them. The same applies to the Fast Creation of Employee Data module. Since the behavior is depicted in the mapping, it can be adjusted individually or removed if it is not desired as it is.
  • A new parameter has been implemented in PLANTA link (Log type) via which you can configure whether the log is to be written in a PLANTA data table, or in a file.
  • In PLANTA link, a new standard interface has been implemented: Import absence. The respective configuration template and the new module class are available now.
  • The new Load data from source to target via pool transaction type has been implemented. As a result, the data is loaded from source to pool first, and if this step has run through smoothly, it is subsequently sent from pool to target.
  • The new Position parameter which defines the order of the parameters in the configuration and the mapping has been implemented. The configuration and mapping parameters are now displayed in the order in which they are registered in the code. See also the A_AddInterfacePositionField and B_MigrateInterfacePositionData migration packets.
  • The MtsModule class in PLANTA link can now be used without setting the da_name parameter, if the module only has one data area.
  • The da_name parameter is replaced by the sending_da and receiving_da parameters in the MtsPoolModule Python module subclass. Due to the inheritance, this change also has an impact on the MtsExportPoolLoadModule Python module subclass. Data of already existing interface configurations is automatically migrated during an update. Individual classes that inherit from MtsPoolModule are lifted up to the latest stand. Details of the new Interface Library parameter.
  • The Source module, Pool module, and Target module fields in the Configuration module have been adjusted and now contain listboxes via which the Modules of the last 30 days as well as Re-usable modules can be selected.
  • New enrichers LeftStripper and RightStripper have been implemented.
  • The parameter fields in PLANTA link are now equipped with listboxes, which show helpful proposals if possible. Since the proposals for module parameters are based on the parameter names, this may lead to wrong proposals for individual module subclasses that have the same parameter name as a standard object. The mapping parameters are filtered via the class names of the objects.

Bug fixes

• General
  • The problem, that the Modified on and Modified by fields in the Symbols module were editable, has been changed.
  • The problem, that the DeleteStandardConstraintsAfterDBImport migration packet failed due to non-deleted data, has been resolved.
  • The problem, that the dash record check and correction under MSSQL failed, has been resolved.
  • The System error: String was not recognized as a valid date time, which occurred when using US American language settings, has been resolved.
  • The problem, that when using the object protection check option, the consistency check erroneously allowed for the virtual DIs as well when checking the DB pos., has been resolved.
  • The values of the Bumber structure rule and Counter from / Counter to parameters have been adjusted for several data tables (their length was adjusted).
  • Incorrect specification for structured Dis in the Function listbox in the Data Items module.
  • The Python error message in the variable dialog (to be opened via the Show variable content button in the Variables module) when clicking on the OK button without a value being entered, has been resolved. In the course of this, several messages have been implemented which indicate the incorrect input of variables (of the variable type or the variable ID).
• PLANTA link
  • If an interface is run and no log records are created in this process, the No log records available message is no longer displayed.
  • The problem, that no subprojects can be selected in the Open Transactions module, has been resolved.
  • The selection list of the data tables in the listbox on the Pool table field has exclusively been restricted to the pool tables.
  • The problem, that in the Interface Parameters module several evaluation criteria cannot be deleted at once, has been resolved.

Migration Packets

Category	Packet name	Function	Type
Help packet	ShowConcurrentDAPos	Logs all modules with double data area positioning in order to be able to filter multiple usage after an update.
Help packet	ReplaceHistogramDIS	Replaces the previous histogram DIs (DI023419/DI002491) and the planned effort (DI023362/DI002508) via the new DI063981 which combines the histogram bars. As a result, new tooltips and effects are set on the data fields.
Mandatory packet	CreateDialogueColumns	Creates new columns for dialog modules as a preparation for a later function
Mandatory packet	FixReportColumnLengths	Increases the length of DI022962 Further parameters
Mandatory packet	AddStakeholderReportTable	Adds new stakeholder report data tables
Mandatory packet	RemoveObjectProtectionFromLoggingTable	Removes the object protection columns from the interface logging table
Mandatory packet	B_MigrateInterfacePositionData	Migrates the new Position parameter to the older interfaces
Mandatory packet	A_AddInterfacePositionField	Adds the new Position column to the parameter tables of PLANTA link
Mandatory packet	LicenseProcessIDs	Extends all auto numbers of process model objects which are used in projects by the system license.
Mandatory packet	SetOwnerLicenseForCustomSchema	Changes the license of the customer schema to the customer license.
Mandatory packet	ActivateAndMoveCustomerTablesToCustomerSchema	Activates and moves customer tables to the correct schema.
Mandatory packet	DeleteNullRecord	Solves the problem that the A_CreateConstraints migration packet failed due to an old standard record.
Mandatory packet	DeleteDummyData	Updates tables that contain dash records which no longer exist.
Mandatory packet	DeleteLinkData	Deletes PLANTA link data which is no longer required.
Mandatory packet	AddSapPspElements	Preparatory schema adjustment for future features.
Mandatory packet	AddUUIDColumnsToKDB	Adds missing UUIDs in tables DT150-DT154.
Mandatory packet	AddCostCalcTime	Replenishes DT461 by DI063979 Date last cost scheduling and DI063980 Time of the last cost scheduling, which enable you to save date and time of the last cost scheduling.
Mandatory packet	FixEVABaseline	Solves the problem, that baselines were not considered in the cost charts after activating the Earned Value Analysis in the Status and Info Board modules.
Mandatory packet	CorrectCustomerOLEs	Adjusts the Use 39 setting of individual OLEs.
Mandatory packet	AddInterfaceFileLoggingField	Replenishes DT560 by DI063846 Log type name, which enable you to define the output of the logs.
Mandatory packet	AddDateShiftProcedure	Completes a procedure for use within PLANTA.
Mandatory packet	ChangeLoadReportIndex	Adds the cost type to the index of the DT827 table.
Mandatory packet	AddProfilingTables	Adds required tables for Python Profiling.
Mandatory packet	AddLatencyTable	Adds required tables for Latency Measuring.
Mandatory packet	MigratePoolModuleConfigurations	Migrates the new sending_da and receiving_da parameters of the PLANTA link.