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

Application

Features

• Project
  • The Working Time/Working Hours Reporting function has been revised completely. For details, see here.
    • The central module for Time Recording has been changed:
      • all recording variants are now in one module, controlled via global parameters #22886 #22888 #22889
      • improved handling #22695
      • new My Time Recording Favorites area for separate listing of objects on which you report periodically or particularly often. #22696
    • The time recording option from other modules (Project Core Data, My Activities) has been adjusted as well. #23404
    • The option to record time on process steps has been removed. #23405
  • The reverse posting function has been revised completely and standardized for hours, costs, and revenues. A global parameter which controls reverse postings has been implemented (posting_cancelation). #21730 #23403 #23588
    • In the course of this, the option to view reverse postings for working hours in the Progress and Check Reported Hours modules for project managers, and in the Actual Hours and ILV modules for department managers as well as the option to view reverse postings for costs and revenues in the Cost Posting and Revenues Posting modules. #23466
  • In PLANTA Standard, the Splitting parameter is now deactivated by default. #23171
  • Due to the requirements of the stakeholder property applicable to the creation of watchlists, a message has been implemented which indicates to the user that the watchlist function can only be used if the stakeholder property is available. #22998
  • In the Users module, a module variant has been implemented which only shows users that have already left the company, i.e. for the persons of which a Leaving date has been set which lies in the past or is equal to today. #22968
  • In PLANTA Standard, the notification functionality has been restricted to e-mail dispatch. In the course of this, the Info module has been removed from the employee board and all items affected have been adjusted respectively. However, the individual use of the old functionality remains possible. If you wish to use the old functionality, please refer to your PLANTA consultant.
  • The maintenance of email addresses for the persons created in PLANTA and their properties like user and stakeholder has been restricted to one field: E-mail in the Persons module. The e-mail address entered here is also used for the corresponding user and for the stakeholder of the person.
  • The procedure for creating todo items in the Todo Items module has been changed. #22764
  • PLANTA master data modules as well as the Planning Objects (in Table Form) module have been streamlined. E.g., rarely used or obsolete columns like contact and address columns have been hidden.
  • The structure of the user menus for the Multi-project manager and Portfolio manager roles have been improved and have been arranged more clearly.
  • A message has been implemented which is displayed if there is no data which is to be assigned to an object. #22898

• Portfolio
  • The Portfolio Simulation function has been improved and extended
    • An indicator has been implemented which gives a signal if another than the latest status report has been selected in the assignment of status reports to planning objects. #22913
    • The Simulate parameter has been implemented which enables (de)activation of projects in the simulation. #22909
    • In the Simulation module, an option has been implemented to copy simulations and thus to create different variants of a simulation. #22911
    • A new data table has been implemented in which the overload of the resources can be saved per simulation. See also the OverloadPerSimulation migration packet. #22934
    • The criteria for selection and display of the departments in the Simulation module has been changed. When making a selection, the resource structure itself is now considered and not the resource structure code. Thus departments the child resources of which are planned in portfolio planning objects are listed even if their resource structure code does not correspond to that of the department. This is also the case if the resource structure codes are not used/maintained. #22716 #22912
    • Another traffic light for overload display has been inserted in the simulation period as a boundary to the traffic light which signalizes the existence of overload in the entire planning object, i.e. also overload which occurs outside of the period selected for simulation. #22914

Bug fixes

• Project
  • The problem that persons the leaving date of which lay in the future were filtered from the base variant in the Persons module and were displayed in the Persons left variant has been resolved. Now persons are only moved to the Persons left variant when their leaving date lies in the past or is today.
  • The performance when initially loading the Overview: Time Recording module has been improved.
  • When creating the working hours in another employee board (department manager funtion), now the project selected for time recording is inserted in the board of the employee for which hours are recorded and not in the employee board of the reporting user.
  • Improvements in PPT export:
    • The probability of occurrence of the risks is now copied correctly. #23314
    • Risks without measures are now exported as well. #22902
  • The Filter Criteria menu item has been deactivated in the Further... module as well as in several overview and analysis modules. #22932 #23008
  • The sorting criterion in the Todo Items module has been changed. The tasks are now sorted by technical ID. #23350
  • Wrong sorting sequence of the process steps in the Standard process models has been corrected. #21991
  • The cause for the Python error message when trying to run the Assign stakeholder action in the Process Status module on process steps to which this action is assigned has been eliminated. #22800
  • The traffic lights for hours to be worked with "yellow" display in the Time Recording module now work correctly #23143
  • The incorrect names of the load profiles in the Load Profiles module have been corrected. #23127
  • The button for deletion has now been removed from the project core data of the subprojects again. Thus the correct behavior (incorrect in DB versions 11-12) that subprojects cannot be deleted via their own core data as long as they form part of a project structure has been restored. #22897
  • The maximum working hours per day check when recording time for stakeholders from the Project Core Data module has been implemented and now works correctly. #23113
  • The problem that the Overview: Time Recording module was emptied after double-clicking on the refresh button has been resolved. #23250
  • The behavior of the mandatory data fields in the Resource Data Sheet module has been corrected. Now fields which are marked with a * behave like actual mandatory fields, i.e. you cannot save in the module as long as these fields are not filled. #22986

• Portfolio
  • In several portfolio modules the option to move records to other areas via shift+drag has been blocked since data logic does not does not allow moving. #23521
  • The traffic lights in the Edit Period:  now work correctly again. #22973

PLANTA Hybrid

Features

• Via the link_allow_self_signed_certificates parameter you can now configure whether PLANTA link accepts self-signed certificates or not. #23345

Bug fixes

• In user synchronization with pulse, users which have no e-mail address stored in pulse (e.g. an API user) are now skipped and no error message is displayed. #22548
• Errors which occur when opening PLANTA pulse are now logged more clearly in PLANTA link.#23554

Customizing and Technology

Features

• The Python version used now is 3.6.0. It is contained in the delivered server 39.5.27 by default. We explicitly recommend to retain this setting and to not switch to a lower Python version.
• The procedure for inserting a default Python macro when creating new modules in the Modules module has changed. The default macro is not inserted automatically but must be inserted explicitly by clicking on the Insert template button. #21289
• The values (a2, a4, a5) for the Action on OLE behavior implempemented with server 39.5.27 and C39.5.26 are now contained in the listbox on the DF behavior by default. #23380

Bug fixes

• The cause for the CreateMSSQLViews migration packet (DB 39.5.11) to fail has been eliminated. #23034
• The incorrect hql-statement in the DeleteLinkData migration packet (DB 39.5.8) has been corrected. #23030
• The cause for the ForceCtgCleanup (DB 39.5.11) migration packet (DB 39.5.11) to fail has been eliminated. #23215
• AttributeError exceptions in Python module subclasses are now no longer blocked. #23605
• DI001561 now counts correctly again: it specifies the number of times the DI occurs as a child data item in DI structures. #23439

Migration Packets

Category	Packet name	Function	Type	WI
Mandatory packet	UpdateDistributionTypeInDT527	Changes the info dispatch type (51 - pop-up, 53 - pop-up & e-mail) to 52 - e-mail	Feature	#22890
Mandatory packet	FixColumnLengthsForResourceRequest	Adjusts the lengths of the fields which are required for future resource request process	Feature	#23435
Mandatory packet	Z_ResourceRequestDBObjects	Adds the views and triggers required for future resource request process	Feature	#23088
Mandatory packet	PfSimuActivateProjects	Adds the new DI065086 in DT093 for (de)activating the planning objects in simulations	Feature	#22909
Mandatory packet	PfSimuDepartmentSelection	Makes changes with respect to department selection in the simulation view based on the resource structure and not as before based on the resource structure code	Feature	#22912
Mandatory packet	OverloadPerSimulation	Relocates the calculation of resource overload during simulation from the resource table (DT467) to a special simulation table (DT099)	Feature	#22934