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

Attention

• For the use of DB 39.5.14, S 39.5.28 and C 39.5.27 are required.

Application

Features

• General
  • The new design PLANTA project design has been implemented in accordance with the new PLANTA-CI. In the course of this, colors and symbols were changed or newly added.
  • A quick access to planning objects from the User Menu has been implemented: #23911
    • Favorites and
    • Recently viewed.
  • In the Calendar master data module, buttons have been added to move the calendar by several weeks or years. #19286
    • Furthermore you have the option to update the calendar.
    • For this purpose, the calendar_shift_years_past und calendar_shift_years_future parameters have been added to the Global Settings to enable editing of the update period.
  • The license level list, which up to now could only be viewed in the License Level module, is now also available in the System Information module which can be opened from the ? menu or via STRG+B. #24234
    • In the course of the new server release (S 39.5.28), the display of the license information has furthermore been extended. For further information, see here.
  • Due to the changes made to the hour recording procedure (no more from/to entries), the usage_actual_load_reporting global parameter is no longer used and is no longer contained in the Global Settings. #23740
  • The planta_link_hostname parameter has been added to the Global Settings via which the host name which is to be used in web interfaces by PLANTA link can be configured. #23589
  • The function for importing holidays via web services, which was deactivated in PLANTA Standard in DB 39.5.11, has been reactivated. #23719
  • The e-mail addresses entered for the respective person are now consistently used for e-mail dispatch for both stakeholders and users to guarantee the reliability of e-mail dispatch. With the DifferingMailAddresses help packet you can find all stakeholders and users in your system the e-mails of which deviate from those of their persons. The deviating e-mail addresses must be standardized manually.
    • Note on correction: both e-mail address fields (DI025746 E-mail and DI041531 Internal e-mail) are located in the user and stakeholder record of the Persons module and are hidden by default, i.e. they must be displayed for correction. #23687

• Project
  • The Time Recording module has been extended and designed more user friendly.
    • The Remaining value is automatically updated immediately after input of actual hours. #6767
    • It is now possible to record presence (times of arrival/leaving). #22698 #23650
    • The recording of prognoses has been outsourced to a dialog module. #23372
    • Day view has been implemented so that you can now switch between a week view and a day view. #23610
    • Newly added tasks are automatically focused so they are found more quickly. #23884
    • The Without forecast and With request process steps module variants have been removed. The With request process steps variant can be opened via the customizer user (P20) and be used for individual modules. #24085
    • The former Finished tasks area has been extended so that it displays all objects which contain actual data but on which no more working time can be recorded. The area is now named Not Postable Objects (Selected Week). #23318
    • Time Recording favorites are now marked with a favorite star. #24131
  • In the Projects module, the Overhead cost projects module variant has been implemented which only displays projects with posting type = 1. #14685
  • Individual status reports can now be exported to PowerPoint. #20919
  • The new Read out task chain function has been added to the Program Schedule. #21518
  • The Read out task chain function has been extended by the Direct predecessor and Direct successor functions. #21519
  • In the My Activities module, a utilization diagram has been added. #22982
  • In the My Activities module, new variables are now used for the period filter so that there is no more interaction with other modules that use the period filter. #23935
  • The manager of the project is now automatically created as a stakeholder and inserted in the "New" category. Resources from the Schedule module are displayed in the "New" category as well if they are created as stakeholders via the Generate team from schedule button in the Project Core Data module. #24058 #17795
  • In the My Department module in the number legend below the utilization diagram, additional areas have been implemented (Use and Utilization). #19498
  • For structured projects, subprojects are now displayed below the main projects in the Projects module and can be expanded if necessary. #24138
  • In the Actual Hours module, the from/to fields have been added, via which the period can be entered. #23708
  • The procedure for creating new yearly tranches in the Budget module has been facilitated. #20567
  • The new Check Reported Hours module has been added to the Project panel and linked in the Further module. It displays the hours of the current project. #23688

• Portfolio
  • In the portfolio you can now expand the projects below the programs belonging to the portfolio. #21457
  • The portfolio simulation has been extended and improved. Inter alia, the following options have been implemented:
    • to simulate capacity and effort (month wise) #22960,
    • to simulate the project runtime (change month wise) #23614,
    • to compare two simulations in the Compare Simulations module. #23615
  • When creating a portfolio, the current user is automatically entered as a manager in the Portfolio Core Data module. #23384
  • Users who are no portfolio managers now have the option to change the grouping and sorting of the planning objects displayed in the Planning Objects module. #20958
  • The procedure for creating new yearly tranches in the Budget module has been facilitated. #20567
  • In the Planning Objects module, the Prioritization module variant has been added. #23984

Bug fixes

• Project
  • Automatic reverse postings are now already created when at least one of the values contained in the affected record is changed: Actual load or Cost type or Load date. #24223
  • The Python error message which occurred when using object filters in MSSQL systems if the limit 2100 for bind variables was overrun has been replaced by a respective message: Results of the object filter too numerous. Filtering canceled. Change the filter or contact your customizer. #24242
  • The key date now behaves equally again, whether reverse postings are activated or deactivated. #23910
  • Data table DT532 Stakeholder/Report is now considered when the person Ids are changed. #24061
  • The comments contained in reverse postings are now treated properly: The comments of the reverse postings remain with the reversed posting while new comments are displayed in the new posting. #24313
  • The key date check which did not behave correctly in DB 39.5.13 now works correctly again. #23915
  • Manual recording of remaining load records in the future using the PM-MONTH load profile is now possible again. See also Known Issues. #23616
  • Double reverse posting of actual hours, which occurred when the respective record was opened in two sessions simultaneously, are mo longer possible. #23634
  • The rights check for the Process Status module has been corrected, so that users without respective rights can no longer select or cancel process models. #22040
  • The cause of a Python error message, which was displayed when trying to open a resource from the Resource Structure module while another resource had already been opened, has been eliminated. #23784
  • The traffic light which displays the adjustment of the posted actual hours against the hours to be worked now works reliably. #23692
  • The cause of the Python error message which occurred when carrying out the Summarize costs and effort action in the Cost Types module has been eliminated. #23243
  • The link on the Allocate Costs to Cost Centers project ID now leads to the correct project. #21856
  • In the Revenues Posting and Cost Posting modules, no more reverse postings are displayed if you switch from the Including reverse postings module variant back to the base variant. #23639
  • The GET implementation for web interfaces contained in the delivery now supports UUID fields. #22028
  • The incorrect calculation of the DI059759 summarized % utilization has been corrected. #13118
  • The cause of the Python error message which occurred when deleting in the Documents module has been eliminated. #23139
  • The cause of the Python error message which occurred when opening resources from the Resource Structure (Display) module has been eliminated. #24004
  • The display of incorrect values in the Send Info module have been corrected. #23797
  • It is no longer possible to open the Time Recording module from the My Activities module for (master) milestones since you cannot record time on them. #23997
  • The wrong listbox in the Group 1 field in the Planning Objects (In Table Form) module has been corrected. #23798
  • The use of different number formats in cost data fields has been corrected. #23806

• Portfolio
  • The values for "other projects" which were considered in the simulation traffic lights are now calculated correctly. #23092
  • The activation of the Copy QG template automatically checkbox in the Portfolio Core Data module no longer prevents the assignment of the planning objects to the portfolio. #23274
  • The occurrence of incorrect project values in the portfolio simulation when using non-active status reports has been resolved. #23775
  • New projects in the portfolio of the Edit Period module are no longer marked as approved automatically. #22039
    • For this purpose, the new DI065513 Budget approved in the portfolio has been implemented. See also the ApprovePortfolioBudgets migration packet.
  • The cause of the Python error message which occurred when opening a project from the Risks/Opportunities area in the Portfolio Status Report (Display) module has been eliminated. #23928
  • The overload traffic light of projects deactivated in the Portfolio Simulation module now works correctly and no longer switches to green. #23062
  • Planning objects for which the Simulate parameter is deactivated are no longer displayed in the Simulation module. #23744
  • The Approve and Delete buttons in the Portfolio Status Report module are no longer displayed after approval of a status report. #22449
  • The date scales in PowerPoint and in the Simulation module are now sorted uniformly. #22256

PLANTA link / PLANTA Hybrid

Features

• Web interfaces in the PLANTA link now use the Fully Qualified Domain Name (FQDN) as an address by default. If it is not available, the host name of the machine is used. If it is not available, the IP of the machine is used. You can define an explicit host name with the planta_link_hostname global setting. #24075

Bug fixes

• An error in web interfaces which occurred when using a transformer with default parameters has been resolved.
• A new 'Decoder' transformer with "encoding" parameter has been implemented, which resolved the problem with umlauts in time recording comments in PLANTA pulse. #23917

Customizing and Technology

Features

• A new conflict management procedure for DB update has been implemented, which replaces the manual writing and execution of the ICOU and therefore significantly reduces effort, runtime, and error probability of manual activity in database update.
  • For the moment, this procedure only applies to updates within the Venus versions. If you want to update from an Earth or a Venus on Earth version to Venus, you have to use the old database update procedure.
• Colors and symbols are displayed grouped in the new Colors and Symbols Grouped module, so that the exchange of colors per group is faster than an exchange per object. See also the FunctionalSymbolGroups migration packet #23967 #23979 #24053
• The individual listbox values for modules and macros (x1 and x4) in the DF behavior listbox was merged into one value (x4). See also the MergeDFModuleMacro migration packet.
• The length of the system name has been increased to 200 characters. #23140
• In the Text Constants module, the new Python code DI has been added, which generates the Python entry of the constant. #23972
• DI028101 has been renamed OLE preview and now also shows the preview of mouseover OLEs in the OLEs module. #23379

Bug fixes

• The cause of the loss of newly customized data fields with DF behavior a2-a5 which occurred after the respective data area was closed and reopened, has been eliminated. #24324
• PLANTA link interface templates are no longer affected by the "Delete open configuration" and "Delete completed configurations" functions. #23943
• The cause of the error message which occurred when attempting to open several data areas from the Object Use module has been eliminated. #22706

Migration Packets

Category	Packet name	Function	Type	WI
Mandatory packet	AddAttendanceTable	Creates a new data table for the recording of presence times (arrival/leaving) (DT203)	Feature	#23650
Mandatory packet	FunctionalSymbolGroups	Sorts individually created colors and symbols in the respective areas in the Colors and Symbols Grouped module	Feature	#23967
Help packet	CorrectLinkDfs	Generates automatic SQL statements which display lists of data areas and data items which contain incorrect symbols (e.g. on link data fields), DF behavior, etc. The respective position must be checked and corrected by means of the results.	Feature	#20067
Help packet	DesignSetNewWhiteMenuPointIcons	Replaces the black menu item icons by white ones in line with the new PLANTA design. This packet replaces the black icons which are implemented with the DesignSetNewIcons help packet. This means that the executed DesignSetNewIcons packet is a prerequisite for the DesignSetNewWhiteMenuPointIcons packet. This also means that the DesignSetNewWhiteMenuPointIcons packet does not automatically replace the old colored menu item icons.	Feature	#24002
Mandatory packet	AddDbUpdateRole	Assigns the new DB update role to all users with customizer rights	Feature	#24186
Mandatory packet	MergeDFModuleMacro	Merges the individual module and macro DF behavior to a module/macro	Bug	#23205
Help packet	DifferingMailAddresses	Logs all stakeholders and users the e-mail addresses of which deviate from those of the respective persons	Bug	#23687
Mandatory packet	UpdateYNType	Sets all Y/N-IDs DIscwhich have "Zero" as a value to value = 0	Bug	#22367
Mandatory packet	ApprovePortfolioBudgets	Approves the already approved portfolio budgets, since DI023278 has been replaced	Bug	#22039
Mandatory packet	RemoveMPseperators	Removes the obsolete second separator in the ? menu, which was contained in customizing and was visualized by the new client	Bug	#24184
Mandatory packet	EnhanceDT947Produkt	Adds Python IDs in DT947 and extends the product ID	Feature	#20967
Mandatory packet	AddManagerAsStakeholder	Creates the manager as a stakeholder in all active planning objects except ideas	Feature	#17795
Mandatory packet	DeleteRoleAssignment	Removes the assignment of role 01100119 (Technical Administration) in DT518	Feature	#22546
Mandatory packet	UpdateDistributionType	Changes info dispatch type 190 = "No info" to 52 = "Mail" for all stakeholders	Feature	#22890