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

Stable 1

• Due to corrections made to the installer, an exchange of particular files is no longer required during installation / update after the server has been fully unpacked. Please use new download files for your installation. #24993

Attention

• Before an update to DB 39.5.15, please consider a known issue with the deletion of synchronized objects, and before an update from DB 39.5.14 to DB 39.5.15 in particular, please consider a known issue with PosRefresherApplicator!
• If you use web interfaces and have updated to DB 39.5.15, please replace the serviceprovider.jar, which is located under /jars/webservice_infrastructure in the server directory, by the new one, which is made available in the Serviceprovider.jar folder on the PLANTA transfer server.

Application

Features

• General
  • The interface between PLANTA project and Jira has been implemented. Thus, PLANTA provides a connection to yet another agile system. For detailed information, see here. #24639
  • The default value of the posting_cancelation global parameter has been changed to 11, so that automatic reverse postings remain active, but the "fixed" effect of the key date is retained. #24689
  • The background color of the activated input fields has been changed in order to make the entry more readable. #24492

• Project
  • The functionality of external links in schedules has been extended and improved. #24682 #24143 #24362
    • External incoming links are now also displayed in the schedules (in addition to the already existing outgoing links).
    • In the barchart of the respective project, the respective OLEs show whether external links exist, and if so, of which type (incoming, outgoing, or both), both on project level and on task level. See also the MigrateAOBIndicatorDataitems migration packet.
    • External links (incoming and outgoing) are displayed in their own area now instead of being displayed together with the internal links.
  • In the Schedule module, resource todo items are no longer displayed in a separate area, but together with the other todo items. #24336
  • The representation of the utilization modules (e.g. Utilization) has been improved. As a result of color adjustment, the amount of, e.g., basic load and availability can be identified more easily. #24469
  • The Used DIs (Used (without subresources) and Used) are now calculated anew on data table 468 if you adjust the periods of the resource. #24179
  • The Task module has been restructured and extended. E.g., scheduling parameters are now displayed in bundles and external links can be viewed and edited. #24762
  • In the Status module of a program, the date of the project status reports is now displayed as well. #24729

• Portfolio
  • Since in PLANTA Standard ideas no longer dispose of schedules, no quality gates are used for ideas, and the most recent ones are no longer listed in the Quality Gates module. #24482

Bug fixes

• General
  • When periods are deleted via the context menu in the Resources module, periods of resources with incomplete periods are deleted as well. #23716
  • In reverse postings, the export flags are now set correctly. #24258
  • If a new person is created and its person attributes are created subsequently without saving, the name of the person is now also copied to the person attributes (not only the code) and will be displayed immediately without a reselection being required. #10493
  • Persons with a Leaving date are now no longer displayed in the Person listbox in the Resource Data Sheet. #21612
  • Process rules 011000012 and 011000017 have been adjusted insofar that the first rule now only controls the planning object type change, and the second rule controls the planning object type change and initiates the creation of a baseline in addition. #24349
  • In the allocation of a Code for a person, it is checked for all person attribute tables in question, DT516, DT511, DT525, DT526, DT467 (not only the person table DT516), whether the code is already used. This becomes relevant if existing resources, which are not person-related, have a particular code and you simultaneously try to create a new person with the same code. #24642
  • Improved performance in the recording of reverse postings.

• Project
  • An error which occurred in MSSQL systems when canceling loads stemming from PLANTA pulse has been resolved. #24441
  • The cause of the Python error message which occurred when carrying out the Send info action on process steps in the Process Status module has been eliminated. #23186 #23487 #24475
  • It is now possible again to select skills in the newly assigned skill records in the Resource Data Sheet module. #24457
  • The check for the Resource to be planned parameter has been extended insofar that it only checks the planning of the resource in projects and tasks in which the resource assignment does not yet have an Actual end date. #24466
  • The cause of the Python error message, which occurred when creating a yearly tranche in the Budget module while no yearly tranche was selected, has been eliminated. #24430
  • The rights check is now correct when switching the module variant in the WBS module. #24275
  • The Resource to be planned checkbox can now be deactivated again. #21435
  • The traffic light on the Opportunity field is now displayed correctly in the module variants of the Risks/Opportunities module. #20044
  • In the Resource Plan module you can now assign resources via the Assign resources function again. #24800
  • The rights check on the Copy forecast function in the Progress module works again now. #23254

• Portfolio
  • The cause of the Python error message, which occurred when the Edit Period module was closed while the Budget module had already been closed, has been resolved. #24727
  • The problem, that after carrying out a simulation in the portfolio with newly included projects, the utilization data of the existing projects in the period table (DT468) were deleted, has been resolved. #24561
  • The rights check in the Budget module now works correctly.

PLANTA link / PLANTA Hybrid

Features

• In the course of the implmentation of another interface (to Jira), the interface between PLANTA project and PLANTA pulse has been optimized and improved, a.o, those projects/tasks already synchronized with PLANTA pulse can no longer be deleted in PLANTA project. Furthermore, the procedure for task synchronization has been changed. For further information, click here . #24691
• In PLANTA link it is now more difficult to delete ones mappings unintentionally. #24736

Bug fixes

• An error which occurred when validating interfaces with corrupt parameters has been resolved. #24420
• A problem which occurred when creating lines in tables with automatic numbers via web interfaces has been resolved. #20949
• Problems in the synchronization of working hours in PLANTA Hybrid have been resolved. #24424

Customizing and Technology

Features

• The object use function has been extended. Now, individual customizing objects cannot only be checked for use in the Object Use module but also from different customizing modules, i.e. decentrally. #18475
  • In the following modules, the respective objects can be checked on their use:
    • Modules, Data Areas, Data Items, Object Use, Colors, Effects, Formats.
• The new conflict management procedure can now also be used for updates from Venus on Earth to Venus. #24212
  • Furthermore the procedure has been extended by PosRefresherApplicator, which is used to identify and adjust data item position changes. Furthermore, a respective module has been implemented (Position Conflicts), which serves to take a look at identified critical projects and to edit them. #24282 #23793
• When setting/changing the fulfillment rules in the customizing of a particular module (in the Modules module) they will now be validated automatically, and if incorrect, they will be highlighted in red color. #23227
  • When setting the wrong fulfillment rules in application (in the Filter Criteria module), validation will, however, not be carried out.
• In the Listbox Values module you can now automatically create a new listbox module from a listbox category. #21062
  • For this purpose, three new parameters have been added to the Global Settings:
    • dataarea_module_listbox_variant: ID of the listbox module variant of the Data Areas module.
    • listbox_generation_template: Module ID of the template module which is used for copying.
    • listbox_generation_work_area: ID of the work area to which the newly created listbox module is assigned.
• In the Modules module, two new fields have been implemented, which show the standard or user specific module variants of the module which has just been selected: Number of standard module variants or Number of user-specific module variants #24580
• The DesignSetNewWhiteMenuPointIcons migration packet from DB 14, which replaces the black PLANTA icons by white ones, has been extended by the missing white OLEs for print preview and is reconfigured to the extent that it is not filtered out if it is set to completed but can be executed again.
• The license check is now carried out automatically via a new server component. If the customer exceeds the volume licensed by him/her, he/she will now be informed on this via respective messages. A list of the licensed components and of their volumes is set out in the license.conf configuration file and can be viewed by users via the System Information module (CTRL+B), or by customizers in the License Level module. #24735

Bug fixes

• The cause for various error messages in the Object Use module has been eliminated. #24908
• The Heading parameter, which was erroneously activated in particular data areas, has now been deactivated. In doing so, the problem that headings were displayed at unwanted positions could be resolved. #24518
• Now, the Edit Board Settings module is no longer displayed empty when you refresh via F7. #24779

Migration Packets

Category	Packet name	Function	Type	WI
Mandatory packet	UpdatePulseTable	Adds the External system column for the selection of an external system for a project to DT 597 and DT 461 each.	Feature	#24369
Mandatory packet	MigrateAOBIndicatorDataitems	Sets the DF behavior of the link data items to "a” everywhere, so that the respective OLE is displayed.	Feature	#24362
Mandatory packet	RenamePulseTable	Renames different tables and columns, so that the pulse-specific tables can also be used for other features	Feature	#24781