Database Release Notes

Date	Version
1/19/2017	DB 39.5.9 (58431)
2/28/2019	DB 39.5.13 (65428)
2/28/2014	DB 39.5.0
3/31/2014	DB 39.5.1
4/24/2020	DB 39.5.15 (68701)
4/29/2016	DB 39.5.7 (55873)
05/09/2014	DB 39.5.2
6/6/2014	DB 39.5.3 (47813)
7/22/2020	DB 39.5.16 (69268)
7/11/2018	DB 39.5.11 (63459)
7/11/2014	DB 39.5.4 (48215)
8/5/2019	DB 39.5.14 (66998)
8/31/2017	DB 39.5.10 (60676)
8/19/2016	DB 39.5.8 (56926)
9/26/2014	DB 39.5.5 (49221)
10/12/2018	DB 39.5.12 (64241)
10/29/2014	DB 39.5.6 (49636)

See also:

Release Notes: Version Overview 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.16

Attention

• If you use web interfaces and have updated to DB 39.5.16, 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 preparations which are required for the implementation of the extended time recording function (recording on PLANTA pulse and PLANTA project elements) when using PLANTA Hybrid, have been made on the part of PLANTA project.

• Project
  • The layout of the status and status report modules for projects and programs has been stretched resulting in an optimized print output. #24891
  • In the Projects: 2 Groupings module you can now expand structured projects in order to have a closer look at the subprojects. #24784
  • When creating the person attributes, e-mail-addresses are now automatically transferred from the person to the "User" and "Stakeholder" attributes. #25100
  • In the Program Applications module of a program, the date of the project status reports is now displayed as well. #24832

Bug fixes

• General
  • Reverse postings in the load_creation_variant = 1 and load_creation_variant = 2 time recording variants with existing remaining effort on the resource assignment now work correctly. #25028

• Project
  • The check for "inactive" project status in time recording now works correctly. Projects which are set to "inactive" with postings in the selected week are now listed correctly under "Not postable objects (selected week)". #25037
  • The cause of the Python error message which occurred when opening the All resources module variant in the Resource Planning module has been eliminated. #25099
  • The link on the Project status report field in the Program Status Report module now works again. #24994
• Portfolio
  • Subprojects can no longer be assigned to portfolios. #24914

PLANTA link / PLANTA Hybrid / Jira Interfaces

Features

• The necessary preparations for the implementation of automatic reverse postings in the Jira interface have been made. The complete functionality is provided with S 39.5.30. #24926
• Transformer in PLANTA web interfaces now support relative parameters analoguously to the mapping parameters in PLANTA link. For more information, see here. #24986
• The UUID listbox in the Web Interfaces module has been designed more clearly. #24971
• The attributes of a web entity now have a consistent order which is also reflected in the order of the .json fields in the standard GET implementation. See also the AddWebAttributePositionColumn #24973
• Transformers in the PLANTA weblink can now distinguish whether they transform a value which stems from an external system for PLANTA project, or whether they transform a value from PLANTA project for an external system. This change does not apply to existing transformers. They function equally in both directions, just like before. #24978
• On a web attribute you can now distinguish between a mandatory field for a POST or for a PUT request. As a result, the same web entity can be used for different methods. See also the AddNewWebAttributeMandatoryColumns #24979
• When a task is synchronized to PLANTA pulse, its calculated dates are now applied as due dates for the respective board. #24945

Customizing and Technology

Features

• When using time recording variant 3 (postings directly in posting records), reverse postings are now controlled automatically via Jython events.

Bug fixes

• Sporadically occurring problems with data field positions when using PosRefresherApplicator have been resolved. #24941
• The problem with corrupt data after update due to incorrectly defined constraints in older position conflicts no longer occurs. See also the ChangeConstraintOnConflictMapping and GetRidOfOldPosConflicts migration packets #24961 #24958
• The cause of the error message which occurred when clicking on the Display work area button in the Object Use module has been eliminated. #25094
• The "today" default value on the up to field which was displayed when importing the employee data via the Fast Creation of Employee Data module has been removed. 25025
• On several bar DIs in DT466, which represent the project code, the correct default symbol 001265 is used now. #24891 #17707
• The event tables are now considered in updates to a new DB version instead of being skipped. #24981
• The constraint_exists method of the SQL packet class now also finds DEFAULT constraints under MSSQL #24976
• An error which occurred in the license check when using "0" as a value, has been fixed. Furthermore the permitted exceedance limit is no longer displayed in the License level field. #24965

Migration Packets

Category	Packet name	Function	Type	WI
Mandatory packet	AddIndexForSlowEndpoints	Adds indices for particular end points (relevant when using web interfaces)	Feature	#25054
Mandatory packet	GetRidOfOldPosConflicts	Removes possible old corrupt position conflicts	Feature	#24961
Mandatory packet	ChangeConstraintOnConflictMapping	Adds 'on delete cascade' to constraints	Bugfix	#24958
Help packet	CreateP21	Creates user P21 if it does not exist after update	Feature	#25067
Mandatory packet	AddPrimaryKeyConstraintToEventsTable	Inserts missing primary keys for the EVENTS tables.	Feature	#24966
Mandatory packet	ChangeNameOfConstraintOnTypeColumn	Changes the constraint name of the TYPE column in DT123	Bugfix	#24974
Mandatory packet	AddWebAttributePositionColumn	Sets the position for attributes of a web entity.	Feature	#24973
Mandatory packet	AddNewWebAttributeMandatoryColumns	Declares web attributes as Mandatory field PUT and Mandatory field POST if the Mandatory field field was active before.	Feature	#24979

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

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

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

Version DB 39.5.12

Attention

• Requirement for the use of DB 39.5.12 up to C 39.5.25.
• After installation of DB 39.5.12, the AddColumntoViewDT430DT472 migration packet must be executed manually again to refresh a view relevant for work reporting.

Application

Features

• The layout design of PLANTA project (colors, symbols, icons, backgrounds, 3D-effects, etc.) has been changed. #22660 #22438 #22437 #22680
• In the course of general design changes, the design of the menu item symbols have been changed, some of the menus were resorted, non-required menu items were removed, or menu items were renamed. Read more ... #22804 #22757 #22721
  • The Capacity scheduling and Unload menu items have been renamed Calculate schedule and Unload schedule and all dialog messages, text constants and data fields have been adjusted in accordance with these name changes. #22435
• The "Copy marked" function for the assignment of objects (e.g. stakeholder to projects) via dialog modules has been standardized system wide. Now assignment objects are now selected via a checkbox in the selecion dialog modules and subsequently copied to the source module by clicking on the respective button. E.g. Assign Stakeholders to Planning Object #14469 #22729
• The code of the persons (resources, managers, stakeholders, etc.) has been hidden in the user modules system wide (except the master data modules). #22436
  • Due to the changes mentioned above, the renaming of the master data object fields (for resources, users, cost types, etc.) was adjusted in the master data modules insofar as the ID fields now have the prefix ID in their headings and the name fields no longer contain a name prefix. E.g. resource ID = R41, resource = Daniela Hart
• In the Program Applications module, the Project status reports area has been added, in which the assignments of the program to portfolios are displayed and can be maintained. #21415
• It is no longer possible to create requested start and end dates by clicking in the scale area. However, moving remains possible on task level. Read more ... #22445
• The Resource ID Change module has been renamed Change Person ID. #22631

Bug fixes

• The performance of budget functions and modules after the update of DB versions < DB 39.5.0 to the latest DB version has been improved. #22611
• The split of the records exported from PLANTA project to PowerPoint (e.g. milestone records) per page now works correctly (there are no more overlappings with the footer). #20747
• The export of cost type group records to PowerPoint now works correctly. Now, all cost type group records (also newly created ones) are exported completely. #22787
• The incorrect behavior during PPT export, which occurred when several users tried to carry out a PPT export simultaneously, has been corrected. If a PPT export is carried out by a user, each further user who tries to export at the same time is informed by a message that the PPT template is currently used and the export is to be restarted.
• A problem has been resolved due to which loads which were exported in another session could still be changed. #22373
• The cause of a Python error message which occurred during the creation of working hours in the Reporting Hours Worked when using MSSQL has been eliminated. #22743
• In the Work Reporting module, the locked projects and tasks are no longer displayed. #22789
• The problem in the Simulations module, that despite selection of a status report for a planning object which was newly added to the portfolio the The following projects do not have a valid report assignment message was displayed, has been resolved. #22687
• In the Risks/Opportunities (Projects, Proposals, Ideas) and Risks/Opportunities (Programs) modules, listboxes have now been implemented on the Damage extent, Gross profit level, and Probability of occurrence fields in the By category and By priority variants. #20036
• The check of the user rights for deletion or changing of an ID of the planning objects works correctly again. #22653
• An error due to which empty yearly tranches were not deleted entirely by the budget scheduling has been resolved #22588
• Fields for numbers with decimal places are now listed correctly in the generated PLANTA weblink documentation.#22769
• Users who have no customizing rights but rights to archive the projects, are now allowed to fetch them from the archive. #22587
• The cause of the Python error message which occurred in the Cost Posting and Revenues Posting modules when trying to post costs or revenues has been eliminated. #22638
• The Python error message which occurred when you tried to open the Resource Data Sheet module of a resource again while it was already being opened has been resolved. #22658
• After detaching the Subprojects module from the structure, it is now updated correctly. #21749
• In the Resource Data Sheet module, the following behavior has been corrected: If the up to field was filled first and you tried to jump to the from field afterwards, an alert was displayed, informing you that both fields must be within the calendar, although the date entered in the up to field was within the calendar. Now the filling order is of no importance as long as the date entries are in line with the calendar. #22320
• The cause of the Python error message which was displayed when attempting to delete a project the cost center of which did not lie within the access area of the user, has been eliminated. #21564
• The display of the scale in the cost and effort trend analysis graphics in the Info Board and Status Report modules has been extended. Now the scale goes as far as the planning data of the project (previously only up to the end of the current year). #22470

PLANTA Hybrid

Attention

• The Synchronize with PLANTA pulse context menu command for the synchronization of PLANTA project tasks with PLANTA pulse has been hidden in the Schedule module in DB 39.5.12 and must be displayed via customizing. More information... #23031

Features

• The project manager is now always the owner of the boards associated with his/her tasks and has administrator rights. If a resource is assigned to a task and defined as a "Person responsible for the task", this resource are granted administrator rights also within the board in order for him/her to be able to invite new members. #22601

Bug fixes

• The problem, that work reporting was not possible on days the numeric date of which does not exist in the previous month (e.g. on July 31st), has been resolved. #22578
• The error which occurred when assigning a member to a board which has already been synchronized with PLANTA has been fixed. #22599

Customizing and Technology

Features

• Filter criteria and data field options have been optimized in several modules. #17515 #22527

Bug fixes

• When setting the owner license under MSSQL, the trigger now marks the code as "active" and only selects the active licenses, as it is supposed to. #22363

Migration Packets

Category	Packet name	Function	Type	WI
Mandatory packet	AddColumntoViewDT430DT472	Adds a view for DT430_DT472.	Feature	#22657
Help packet	DesignSetNewIcons	Replaces the old colored icons by the new black icons on white background and the icons in the headings by blue icons on white background.	Feature	#22721
Help packet	DesignSetNewMenuPointIcons	Replaces the old menu item icons by the new black ones.	Feature	#22721
Help packet	DesignSetNewMessageIcons	Replaces the old icons for dialog messages.	Feature	#22721
Help packet	DesignSetNewHeaderEffect	Replaces the old effect on background DIs in module header bars. The background color has been removed, the bar is now colorless and there is only a colored line on the left hand side of the bar.	Feature	#22721

Version DB 39.5.11

Attention

• For DB 39.5.11, C 39.5.24 and S 39.5.26 are required.
• When updating a DB version < 39.5 to DB 39.5.11, performance issues occur during budget migration when there are several complex project structures. Therefore, please note this before updating to DB 39.5.11 #22611
• When updating to DB 39.5.11 under MSSQL, it may occur that the UnloadAndReplan migration packet fails due to a unique sequence problem. In such a case, please run the migration packet once more after completion of the migration.

Application

Notes

• In version DB 39.5.11, the hours to be worked function in the Global Settings has been deactivated by default. If you use this function and carry out an update to this DB version, you have to deactivate the function again after completion of the update. #21515
• The import of holidays has temporarily been removed from the Calendar module. #22241

Features

• Hybrid
  • PLANTA Hybrid has been implemented
• Portfolio
  • The dynamic calculation of the quality gate and todo item dates has been implemented. Further information #21166
  • In the Quality Gates module, small functional adjustments have been made: On the Date field a traffic light has been implemented and the traffic light on the Completed field has been changed. The Completed on field, which can be filled by the project manager (for further information, see also the AddQGDoneOnFieldForPL migration packet), has been added to both the todo items and the quality gates. #21496
  • The Documents module has been extended: Portfolio documents are now created and maintained in a categorized manner. They can as well be set to completed or be archived and then maintained in the respective module variants. #19951
  • In the Costs/benefit chart in the Info Board module the planned benefit is now taken as a reference value for comparison with total costs instead of the achieved benefit. #21778
  • In the Edit Period module, traffic lights have been implemented on the planning objects which signalize whether the budget of the respective planning object exceeds the budget of the portfolio and whether the planning object is contained in several portfolios. #20197
  • In the Status module, the behavior of the TBM checkbox has been changed insofar as it is now deactivated automatically if the WBS checkbox is deactivated. However, there is no dependency in activation. #20516
  • The Administer Portfolio Images module has been optimized. #20788 #20504
  • In the Portfolio Core Data module, the Copy QG template automatically parameter is implemented, which can be used to define whether the quality gate template is automatically copied to the planning object when it is copied to the portfolio. #20552

• Programs
  • In the Programs module, the bar for the visualization of the project/program date delays have been implemented. #20952
  • All newly created tasks in programs now receive the Master milestone setting by default. #21513
  • In the Program Core Data module, the Portfolio assignment area has been added, in which the assignments of the program to portfolios are displayed and can be maintained. #20772

• Project
  • If a week is entered for direct jump (Go to button) in the Work Reporting module which lies outside the resource calendar, a message indicating this is now displayed. #21472
  • The SAP WBS implementation (Create SAP WBS Elements, SAP WBS modules as well as the SAP Project Structure Import, SAP Plan Costs Export, SAP Plan Costs Import default interfaces) has been extended by account assignment elements. #20514 #21144
  • In the Reporting Hours Worked module, several minor adjustments have been made: Among other things, an option to filter by date (Extras Filter Criteria is activated) has been implemented. #22294
  • In the Utilization with Cause and Resource Utilization by Code modules, the display of the utilization has been restricted to active projects and projects with utilization diagram in a particular period. Furthermore, tasks with actual end are filtered out completely in the first module and displayed grayed out in the second. #21955 #21981
  • The Resource Overviews (Reports) have been included in the Resource Management role.
  • An option to update period records after changes have been made to resource parameters without deleting them. This solves the problem of vacation and absence data loss. For the procedure, click here. #16105
    • In addition, an info message has been implemented which notifies the user in case of resource parameters changes that the periods are to be updated. #20400
  • The area for creation of summary reports in the Check Status Report Creation and Project Applications module has been revised. #21169
  • In the Work Reporting Overview module, an option to change the work reporting display period and the scale by making changes to the from and to fields has been implemented. #21452 #21860
  • In the Absence and Absence of the Department modules, data is now summed per year and you can scroll to previous and following years dependent on the periods of the resources. #12408 #21432
  • The scheduling performance, especially that of the budget and cost scheduling has been improved substantially. For the detailed calculation matrix of all modules in question, see here. #20208
  • For groupings in the Multi-Project Board, etc., no more text constants are used, but instead the values of the listbox implemented on the Code data field. (Listbox category 00000009). When you use individual project codes, you now only have to adjust the listbox values. #21573
  • If the user has no write rights for a planning object, the You are not authorized to carry out this function dialog message is displayed. #20888
  • A dialog message has been implemented which notifies you, when you try to activate the Status reports: collective creation parameter on subprojects, that this function is available for main projects only. #20724
  • The Projects module has been extended by the display of proposals. Furthermore, the Priority parameter has been included in the module to enable project sorting by priority. #20283
  • In the Send Info module, the Info per field has been included additionally. Thus, in case the recipient is changed, it is immediately visible in what manner he or she receives the message. #20007
  • In the Progress module, a button has been implemented which automatizes the copying of forecasts. #19807
  • In the Risk Trend Analysis and Opportunity Trend Analysis modules the Risk and Opportunity fields will be displayed in the colors of the area of the risk or opportunity matrix in which the risk or opportunity is displayed in red, yellow, or green depending on its weighting and probability of occurrence. #20670
  • With the new customizing option for creating links between tasks in different data areas, you can now create cross-functional links from tasks to gates in the Project Schedule, and graphically from program tasks to tasks of the program projects in the Program Schedule. #21526
  • In the Subprojects module, it is now possible to move subprojects. #18077 #22177

• PM Administration
  • If a Leaving date is set for a person in the Persons module, it is inherited to the child attributes (person resource, resource, user, stakeholder). #19934 #7291
  • The maximum_work_hours_per_day gloabal setting via which the maximum number of working hours per day can be defined has been added. For this purpose, the AddMaxHoursColumnToEmployeePool migration packet must be run. #22158
    • For new resources, "10" is used as a default value from now on. In order to define the maximum number of hours worked for already existing resources as well, run the SetMaxHoursPerDay migration packet.
  • Since the selection of the Internal/external employee resource type during resource creation necessarily requires the selection of a person, the Person field is now marked as a mandatory field as soon as the resource type for a resource to be newly created has been set to Internal/external employee. #20866
  • The process actions for assigning stakeholders and evaluating risk values/objective contributions have been extended, so that the actions can be carried out more easily: Assign stakeholder and click on the Evaluate button to open the risk values and objective contributions in order to be able to evaluate them. #20815
  • Process rule 011000017 Change action planning object type + create baseline has been changed, so that process models which carry out a change of the planning object type (idea/proposal/project) during phase approval are no longer reset if there are still open phases. #21269

• PLANTA link
  • The functionality of the SAP plan costs export and SAP plan costs import interfaces has been adjusted, so that the transfer of the costs/effort is now done via the account assignment element level. #20497
  • In the listbox on the HTTP method field in the Test Web Interfaces module, input only via listbox has been implemented to prevent users from making inputs which do not occur in the listbox. #22168
  • The new PPMSCSVModule module subclass for generating CSV files which can be read by PPMS 38. #21357
  • The new Administer Mapping Functions for administering the mapping functions of PLANTA link has been implemented. Here, you can add new functions to make them available for selection in the listbox of the interface configuration. #21332
  • In PLANTA link, a new standard configuration has been made available:
    • BAPI_BUS2054_GETDATA and BAPI_PROJECT_GETINFO, in order to open the BAPIs and import their data to the PLANTA SAP WBS Element Table. #21031
    • Conversion factor import for the import of conversion factors. #21463
  • The MtsModule class in the PLANTA link now recognizes value X as a valid input for checkboxes. #21575
  • The dimmer during PLANTA link transfer now shows a static text while the current status is written in the status line of the module. This causes a significant performance improvement. #21454 At all positions at which a configuration can be edited in PLANTA link, the single Configuration module is no longer displayed, but a new panel is opened instead. #20760
  • PLANTA link now writes an exact warning in the logfile if an external key field is filled incorrectly. #21087
  • The sequence of the mappings, if they are generated automatically with PLANTA link, now equates to the module customizing again. #21085
  • PLANTA link no longer runs validation checks for its configuration if a parameter is changed which is not linked to any validation step. An example for such a parameter is the filepath parameter of the CSVModule class. If an interface is opened outside PLANTA link via macro, it is no longer necessary to use a subclass which switches off the validation in order to achieve a gain in performance. #21069
  • When you try to change records which have already been transferred to SAP, a proper alert is now displayed instead of a Python error message. #21248
  • The AbsenceImportModule class of PLANTA link now writes a respective error message in the log if the module customizing does not meet the expectations of the class. #21086
  • The PLANTA link web entities now have a new, displayable VH SST attribute. The field shows how often a web entity is used in interfaces. #20152
  • The Logging module now shows the number of errors/warnings of the interface run. #22296
  • The ConvertDateToYear converter and the YearlyTrancheExists validator has been added as well as the existing MtsLiabilityModule class. For this purpose, the AddLiabilityPoolTable migration packet must be run. #20491

Bug fixes

• General functions
  • The problem that the changes made to the access rights did not immediately take effect when opening the modules for which the rights have been changed, but only in respective modules after refreshing via F7, has been resolved. #21410
  • The export to PowerPoint has been improved, a.o. as follows: #20757 #21325
    • The result of the chart export has been improved. #20843
    • The difference in the display of scales has been resolved. #20779
    • The incorrect export of planning objects (not all were exported) has been corrected. #20780
    • The display of bars and tables has been corrected. #20875
    • A message is displayed now if no charts are available. #20897
    • The error which caused the error message when exporting to PowerPoint if there was data in the clipboard at this time, has been resolved. #20901
    • The export of large data volumes has been optimized. #20674
    • When exporting a project with subprojects, the structure tasks are no longer copied along #21861
    • The problem that planned duration was exported instead of remaining duration has been resolved. #21061
  • The resource ID change can be carried out repeatedly if it has been initiated during the running scheduling. #20754
  • The project milestones in a PDF file with a portfolio status report show no other color than in the Dashboard. #21011

• Portfolio
  • The quality gate symbols are immediately visible in the Quality Gates module below the scale after the quality gates have been copied to a project. A previous scheduling run in the project is no longer required. #20890
  • The incorrect program behavior in the visualization of unsaved changes (*) and in the storage query when trying to remove an active quality gate template from the portfolio, has been corrected. #21184
  • The bars in portfolio road maps can no longer be moved. #20983
  • The problem that some cost/effort charts in portfolio status reports converted to PDFs did not contain any data, has been resolved. #21013
  • The planning object type when using filters in the portfolio info board is now considered. #20956
  • When activating/deactivating the planning objects in a budget period of a portfolio and subsequently updating the period, the data of the portfolio is always updated along. #21475
  • Cause of the error message which was displayed when attempting to export an empty simulation (without data) to PowerPoint has been resolved. #21912
  • The displayed master milestones in the Active report and Baseline lines in the planning object charts in PDFs of portfolio status reports are no longer reversed. #21010
  • The incorrect data on which the charts in the Budget and Costs per Portfolio, Project, and Year module are based have been corrected. #21370
  • Projects which contain quality gates can now be deleted. #21345
  • The incorrect display of the time interval to the master milestone on the quality gates in the Schedule module has been corrected. #20535
  • In the Quality Gates module, no more requests are displayed and no more quality gates can be copied in for requests. #21462
  • When trying to select a status report for a planning object to create a portfolio report, the respective message is displayed again and no empty dialog is displayed any longer if the planning object has no released status reports but possesses project applications. #21001
  • The cause of the Python error message which occurred in the Administer Portfolio Images module when trying to delete images, has been eliminated. #21243
  • The problem, that the Python error message which occurred in the Status module when trying to change the estimate of planning objects without status report selection has been resolved. #21268
  • The behavior of the date listboxes in the Info Board has been corrected, e.g. an input check has been implemented, so that the from date cannot be later than up to. #20861
  • The double use of the Priority parameter in the Proposal Core Data module has been corrected. #21296
  • In the Quality Gates module, the quality gate symbols disappear after opening and closing the tree structure of the tasks. #20988
  • The planning objects of the portfolio for which the WBS checkbox has been deactivated are no longer considered in the Risks/opportunities area of the respective status report. #20516
  • The Completed value of the quality gates is calculated correctly. #20986
  • When you open the Portfolio Core Data module, no more error occurs when the assigned profile image has been deleted in the mean time. #20874
  • In the Time&Budget matrix in the Portfolio Status Report, no more ideas are displayed. #20449
  • The wrong dialog message which was displayed when assigning planning objects to portfolios if the planning objects were already assigned to other portfolios, which, however, used different quality gate templates, has been corrected. 21425
  • The cause of the error message which was displayed in the Portfolio Core Data module when selecting a quality gate template from the Active template module has been eliminated. #21907

• Programs
  • The user rights check for status reports of programs has been corrected, so that users without respective rights can no longer release and delete status reports. #21073
  • Newly created programs contain the Planning early parameter and are therefore no longer set to Planning late by default. #21176
  • Newly created program applications are displayed in the Program Applications module and no longer as status reports in the Status module. #18500
  • The cause of the error message which occurred when clicking on the Refresh button in the Program Application module has been eliminated. #20879

• Project
  • The problem caused by a Python message when a resource without defined cost type (cost type = -) attempted to report hours worked to an overhead cost project, has been resolved. #22018
  • The cause of the Attempt to use a DtpRecord instance which has already been deleted! error message in the Reporting Hours Worked module when deleting several load records for a record on which the resource has previously not been planned, has been eliminated. #22119
  • The problem, that an error message was displayed when trying to report vacation for a resource which had longer periods than its parent resource has been resolved. #21638
  • The different display of revenue and cost resources in the Schedule module, depending on whether the Insert Revenue and Cost Resource or Assign Revenue and Cost Resources (dialog modul) was used, has been corrected. #19948
  • Planning objects can also be deleted if they are used in simulations/road maps. #21615
  • The problem with the display of data in the Gantt chart of the Cost Reports and Effort Reports modules has been resolved. Now both total costs and cost budget are displayed by cost type groups and with appropriate coloring. #22024
  • The approval for status reports which is created via the Summary creation: status reports function can be canceled again. #21631
  • Department resources no longer receive Work = for days for which at least one of the employee resources has reported absence or vacation. To correct the incorrect data resulting from this error, please run the 22092 migration packet. #22092
  • In the My Planning Objects and Reporting Hours Worked modules, completed projects are no longer displayed. #21721
  • In the Resource Planning module, the effort can no longer be allocated from/to periods. A message has been implemented which notifies the user when trying to allocate effort from/to a resource that allocation is not possible due to missing resource periods. #19822
  • After export of actual load from PLANTA, all records (not only the fields with actual loads) are locked for editing. Now an alert is output when you try to change the exported record in the Reporting Hours Worked module. #21727
  • In the Subprojects module, the button for changing the functional ID has been included again. #21493
  • When using the Idea and Proposal process model, another info can be sent via the approval of another phase if the dialog for conversion of an idea to a proposal or of a proposal to a project is confirmed upon approval of the project. #21231
  • When reimporting the projects previously exported from PLANTA project to Microsoft Project, it is no longer tghe case that only one task is reimported. #21601
  • In the PLANTA project vs. Microsoft Project module, quality gates are no longer displayed like normal tasks. #21211
  • Changing the value for the manual cost entry to manual now causes a respective change to the scheduling behavior again (from capacity scheduling to time scheduling). #21522
  • In the Dashboard module, milestone charts of projects which contain more than 999 tasks are displayed. #21389
  • The length of DI063942 SAP WBS element name in pool data table DT964 has been adjusted to that of the original table DT963 (50). #21576
  • The message which indicates tasks which cannot be included when partially copying schedules with links is now displayed again. #21506
  • Accessing planning objects from the Resource Planning and Skill Requests modules for the same user no longer results in different rights settings. #20041
  • For the Category listbox in the Risks/Opportunities module, input only via listbox has been activated. #21294
  • In the Programs module, the IDs of the quality gates of the superior program are displayed. #20849
  • The double availability of department resources which only occurred in DB version 39.5.10 has been resolved. #20070
  • In the module variants of the Risks/Opportunities module, the correct number of opportunities is displayed. #21063
  • For the Dashboard module, the up to filter value has been increased, so that the Activities area is displayed constantly again. #21309
  • The manual entry of the % completed value for the todo items of the quality gates in the With Quality Gates module variant in the Schedule module is possible again, provided that the value to be entered is contained in the listbox. #21057
  • In the Resource Planning module, the bars for planning objects with code E are displayed in the correct color. #20943
  • The Remaining effort field in the Resource Plan module is no longer on output, so that it can be edited by users with the respective rights again. #21090
  • In the Stakeholder area in the Project Core Data module, the correct phone field has now been included. #21099
  • The date delay in the date bar in the Budget overrun: effort of the Critical Projects module is now visualized (red bar). #20113
  • In a new program, newly created tasks remain displayed after clicking on the Update (F7) button. #20974
  • During PowerPoint export, a temp folder in which the files can be stored is now displayed. As a result, the export no longer fails in the case of missing write rights for a local folder. #21046
  • In the Remaining Effort and Costs module, the functional project ID is displayed correctly when grouping by projects. #20922
  • An error which occurred when creating subordinate employees via the Fast Creation of Employee Data module, and which caused the Factor amount/period field to remain empty, has been resolved. #20940
  • Controlling reports can now have the last released status. #20694
  • The missing links on the task IDs in the Schedule module of the program have been implemented. #20860
  • The problem, that proposals for which the Status reports: summary creation checkbox was activated were not displayed in the Check Status Report Creation and Project Applications module regardlessly, even if they did not contain any status reports in the period searched for, has been resolved. #20756
  • The error that the grouping field in the By priority module variant in the Risks/Opportunities was empty although the respective values were available in the risks and opportunities, has been corrected. #20591
  • In the Budget module, the value is now updated in the Abs. costs field in the Revenues area after recalculation and not only after reopening the module. #20162
  • In the Send info module, the decimal places of the forecast values are taken into consideration. #20506
  • In the Activities area in the Dashboard module, quality gate todo items are no longer taken into consideration. Here, only task todo items are considered. #20884
  • The quality gate todo items are displayed in the Quality Gates module variant of the Schedule module again as soon as they are set to 100 % completed. #20880
  • If a new resource is created, but no periods are defined for it at first, a period record with the creation date of the resource is created anyway; based on the entries in the Start period/End period fields which are automatically filled with today’s date upon creation of a new resource. #20916
  • In the Stakeholder area in the Project Core Data module, the road map dates are now displayed. #20891
  • When you carry out a part string search in the Object Filter module, the listbox on the Filter criteria field is no longer case sensitive. #20153
  • Status reports can be deleted again under MSSQL. The Python error which occurred during deletion has been resolved. #21422
  • The moving of subprojects in the Subprojects module is now possible again. #18077
  • If the from and to fields in the Reporting Hours Worked module is set to 0, now 0 h are calculated instead of 24 h. #21918
  • In the Reported hours worked: current week area in the Reporting Hours Worked module, the project manager now only sees the reported hours worked for the current project and not those for other projects if he/she has opened it before via the Report hours worked context menu command on a stakeholder resource in the Project Core Data module. #22297
  • The wrong sequence of the process steps in projects, proposals, and ideas after copying the template has been corrected. #22019
  • The problem which was caused by the ORA-01843: not a valid month error message which occurred when canceling a process model under particular database requirements has been resolved. #22211
  • In the listbox on the Priority field (DI006508 and DI057914) now the high, medium, and low values are displayed in a standardized manner.

• PM Administration
  • The resources for which a Left on date is set in the future are displayed in the modules which filter by Left on date again. Only resources for which the Left on date is smaller than or equal to today’s date are filtered out. #19754
  • In the Persons module, persons with set Left on date are no longer displayed in the Base module variant, but in the Persons left module variant. #21614
  • The Insert Resource context menu has been removed from the Resource ID Change module. #20809
  • After renaming a user there will be no more confusion between the former and the current name for user, stakeholder, and person resource name. #20349
  • The cause of the KeyError: 30 Python error message which occurred when deleting SAP WBS assignments in the Create SAP WBS Elements module has been eliminated. #22002
  • The deletion of elements in the Create SAP WBS Element module as well as the related dialog messages have been fixed. #21826

• PLANTA link
  • Under MSSQL it is possible to delete log files in web interfaces again. #22027
  • Clicking on the Test interface button with invalid records no longer leads to an error message. #22029
  • The incorrect behavior due to which newly created configurations which were marked as templates could be displayed and deleted in the Open Configurations module has been fixed. #21242
  • An error which occurred when opening the PLANTA link Logging module in the Calendar module has been resolved. In the course of this the PLANTA link logging was configured in a way that it is only opened if the user possesses the PLANTA link 01100028 role. #22241
  • The problem that in mappings which use several relative parameters errors occurred when using non-string data types has been resolved. #21888

• Request
  • The empty lines which were displayed for some cost centers in the listbox on the Filter criterion field in the Object Filter Request module have been fixed. #20931

Customizing and Technology

Features

• In the Overview of all Previous Runs module, packet dependencies and database system dependencies of the packet are displayed in addition to the customizing dependencies. #21423
• When setting a field to Invisible data window (window 9) in the module customizing, the Filter criteria and DF options parameters are automatically deactivated. #21060
• In the module customizing, an option to automatically set the data area positions in accordance with the defined structure has been implemented. For this purpose, a respective button has been implemented in the Modules module. #2361
• An option to display the database occupancy level for inactive data tables and data tables and views which are available in the database but not in PLANTA has been added to the 000230 PLANTA Data Table module. #20324
• Updates of older DB releases in which newer tables are still missing have been made more secure by loading the data dictionary in a first step before the data for the new tables is imported. #21733
• The values in the listbox on the Action ID field in the Data Areas module have been supplemented by frequently used macros. #20679
• A new function has been added in the Data Dictionary module, with the help of which columns which do not yet exist in PLANTA project can be created as DIs. #20976
• Listboxes have been added to the Effect ID, Window, and Use filter on fields in the Option Module for MV. #21453
• Object Use
  • For Python macros as place of use, the IronPython script, the DF configuration, as well as process rules are checked.
  • For modules as place of use, both the belonging work areas (in which the module occurs) and menu items as well as user and roles with startup macros are checked.

Bug fixes

• The incorrect customizing of data table 974 SAP project structure/report has been fixed. #21235
• The use of the Object Use module has been improved and errors have been resolved, e.g.
  • the problem, that the traffic light DIs could not be found.
  • the error which occurred if the search string used to search for Python files generates a result which is too extensive. #20729 #20740 #20744
• The irritating Please check input status line message which was displayed during database consistency check has been removed. #20667
• The cause of the Python error message which occurred when trying to create an incarnation has been eliminated. #20054 #21012
• The Links without tooltip module variant has been removed from the Modules module. #20136
• The problem, that no input was accepted in the Variables for manual search lists field when creating new variables, has been fixed (the problem only occurred in DB 39.5.10). #21029
• Separate values are now used for the threshold values on the cost and effort traffic lights. The @G286 and @G287 variables are used for costs and the @G292 and @G293 variables for effort. #19980
  • In case you wish to continue the @G286 and @G287 variables for both costs and effort, please run the optional ChangeEffortThresholds migration packet after database update.

Migration Packets

Category	Packet name	Function	Type	WI
Mandatory packet	CreateMSSQLViews	Creates views which are required for the calculation of the recursive sums in the SAP-WBS tables in MSSQL =		#20514
Mandatory packet	AddPulseMappingTable	Inserts new tables for the hybrid implementation	Feature	#21604
Mandatory packet	AddPulseFlagForWebInterfaces	Inserts a new flag for web interfaces	Feature	#22130
Mandatory packet	AddQGDoneOnFieldForPL	Adds new Completed on: manager columns in DTs 804 and 463.	Feature	#21496
Mandatory packet	AddCtgConstraints	Adds the external keys of DT281-DT284 in DT280 to ensure that in the first mentioned data tables no records on the cost type groups exist which are not available in DT280.	Feature	#22092
Mandatory packet	AddFunctionalPortfolioId	Creates a new DI for the functional portfolio ID in DT870. At first, the functional ID is not contained in the user modules and cannot be changed. The function is scheduled for one of the following releases.	Feature	#20251
Mandatory packet	SetDfWithLengthOfResName	Extends the DF length of DI000246 and all dependent DIs (incarnations/exits) to 200. Adjusts the DF width of the respective data fields in all modules.	Feature	#20827
Mandatory packet	AddLiabilityPoolTable	Adds the new pool table DT559 for liability import.	Feature	#20491
Mandatory packet	ResolveSAPPSPAAEPacket	Sets the CreateTableSapPspAae migration packet (DB 39.5.10) to completed if the table it creates already exists.	Feature	#21059 #22409
Mandatory packet	AddMaxHoursColumnToEmployeePool	Creates the MAX_HOURS column for the Fast Creation of Employee Data for the new DI065035 Max. hours/day in the employee pool on the database.	Feature	#22158
Help packet	SetMaxHoursPerDay	Fills the Max. actual hours/day field for all existing employee resources (resource type = 1*) with the stored value in the maximum_work_hours_per_day global setting.	Feature	#22158
Mandatory packet	CreateCriticalPathDI	Creates DI064739 in DT463, with the help of which tasks are marked by the scheduling which lie on the critical path.	Feature	#21020
Mandatory packet	UpdateWorkFlag	Corrects the incorrect data produced by copying the absence data to the department resources.	Bugfix	#22092
Mandatory packet	ForceCtgCleanup	Runs the CleanupOldKoAGrFields migration packet if it has not yet been run during the update from Venus (DB 39.5).	Bugfix	#22278
Mandatory packet	CreateCriticalPathDI	Creates DI064739 in DT463, with the help of which tasks are marked by the scheduling which lie on the critical path.	Bugfix	#21020
Optional packet	ChangeEffortThresholds	Resets the variables for the threshold values of the cost and effort traffic lights used from DB 39.5.11 to those used prior to DB 39.5.11 @G286 and @G287.	Bugfix	#19980

Version DB 39.5.10

Application

Features

• General
  • Added Project Overviews and Program Overviews to the PLANTA Standard role Management 01100228 (demo user R47).
  • Changed the notation for names from last name, first name to first name, name throughout the system.
  • Work reporting of already closed projects and tasks will now be displayed now in the Work Reporting module They cannot be edited manually and cannot be edited.

• R41
  • Implemented the PowerPoint Export in the Status module. The export is started by the push of a button to a previously created PowerPoint template.
  • In the Status and Status Report modules, the Risk and Opportunity fields will be displayed in the colors of the area in the risk or opportunity matrix in which the risk or opportunity is displayed red, yellow or green by means of its weighting and probability of occurrence.
  • Adjusted the rights for creating work reporting for stakeholders via the Project Core Data module. Stakeholder without modification rights are only allowed to create work reporting for themselves.
  • Added a total line in the SAP WBS module, in which the values of all SAP WBS elements are summarized on top level. The element values located in the structure below are summarized on top level and, thus, are indirectly included in the total as well.
  • The checkbox of the Status reports: collective creation parameter in the Check Status Report Creation and Project Applications module can now be edited.
  • The period for searching planning objects for which the checkbox of the Status reports: collective creation parameter is activated and for which no status report has been created yet, will now be directly defined in the Check Status Report Creation and Project Applications module.
  • Added the Quality Gates module variant in the Schedule module.
  • In the Resource Plan module, the Distribute effort button has been implemented in order to standardize the distribution procedure.
  • When copying a schedule to a new project, notes from the template schedule are copied now as well.
  • A dialog module has been implemented which is displayed when a resource attempts to deactivate the Resource being planned checkbox and outputs a list with all projects and tasks the resource is planned in.
  • The layout of the Budget module has been improved (the base variant has been streamlined, areas have been separated more clearly, global parameters have been hidden, column alignment has been optimized).
  • In the Further ... module, a module variant has been implemented which enables you to individually define which modules are to be loaded by the default setting when the Project panel is opened.
  • For the Inform project manager function in the Critical Projects module, the option to only send messages to project managers of selected projects has been implemented.
  • In the Deviations module, comparing reports are now offered for selection in a dialog module which enables better handling of the report list.
  • Conversion Factors module
    • Implemented a message when deleting conversion factors whether they are really to be deleted.
    • The last available item in a conversion factor can not be deleted, as a conversion factor needs to contain at least one item.
    • It is not possible anymore to delete all the conversion factor items. When trying to delete all the conversion factor items, a noting message will be displayed.
  • Removed all the deviation model parameters from Start 1 deviation to End 5 deviation from the Model and Model ParametersMOD009A0U module as they are not used anymore.
  • Improved the performance when deleting a project.

• R50
  • Removed the save prompt about whether to copy a template into the Documents module.

• R60
  • Improved the layout of the Budget module (optimized visual separation of areas and column alignments).
  • Added the Quality Gates module variant in the Schedule module.
  • If, in the opened project list, a project is detached from the portfolio assignment, it is displayed immediately after updating the project list in the program.

• R70
  • Revised the Portfolio component completely. Implemented new modules, rebuilt existing ones. Adjusted the workflow to the one of a project.
    • Replaced the Portfolios (MOD0099FF) module by the Portfolios (MOD009CSD) module. Moved the charts to the new Info Board module and improved the performance.
    • The Portfolio module has been replaced by the Portfolio panel. Existing functionalities have been distributed to new modules and have been extended. This includes the following:
      • Dashboard: displays critical planning objects and offers the opportunity to create and edit a watchlist.
      • PortfolioCoreData: Portfolio basic data, cost type group administration, quality gate template selection, stakeholder selection and administration
      • Planning Objects: Overview over planning objects with the option to add new planning objects or delete existing ones from the portfolio.
        • The portfolio manager can add his own estimate of a planning object in addition to that of the project manager in the Planning Objects and Status modules.
      • Budget: contains the portfolio budget data. Editing per period can be done in the separate Edit Period module.
      • Quality Gates: provides the option to assign quality gates to planning objects as well as the check of the quality gate status per planning object.
      • Status: as starting point for creating new status reports and as overview over already created status reports.
      • The new Info Board module contains numerous portfolio related diagrams for the visualization of the portfolio development in different areas. Integrated the functionalities of the old Portfolio Analysis, Scoring module into the new Info Board module.
        • In the Info Board module, a message has been implemented, indicating that the selected portfolio does not contain planning objects which occurs when you try to open a report module (e.g. Projects by objective contribution and risk value) which does not contain any data due to missing planning object assignments.
      • Risks/Opportunities module: displays risks and opportunities of all planning objects assigned to the portfolio in graphic and tabular form.
      • Documents: provides the option to assign documents to the portfolio and to administer them.
      • Change Requests: displays the change requests of the planning objects assigned to the portfolio.
    • Implemented a new simulation in the portfolio:
      • The new Simulations module is a starting point for the creation of new simulations and displays an overview of already existing simulations and road maps.
      • The Simulation module offers the opportunity to edit a simulation and to define it as a roadmap.
      • A simulation or road map can be exported to a previously created PowerPoint template by the push of a button.
      • Utilization Simulation displays the utilization of one or several departments of which the resources are planned in the planning objects of a portfolio.
    • Added the Check Status Report Creation and Project Applications module to the Portfolio role in the Administration work area.
    • In the Portfolio Manager object right, requests will now be considered.
    • Renamed module MOD009BBI Projects by Objective Contribution and Risk Value (previously Projects by Objective and Risk Contribution).

• R90
  • Using PLANTA link, web services are available.

Bug fixes

• Work Reporting
  • Fixed the problem that tasks were not displayed at all or that sporadically the wrong tasks were displayed in the Reporting Hours Worked module when selecting an overhead cost project.
  • Fixed the problem that the Task listbox in the Reporting Hours Worked module did not show any data.
  • Fixed the problem that reported hours worked were saved when data was partially entered in the Reporting Hours Worked module but the saving prompt was answered with No.
  • Fixed the Python error message which occurred in the Reporting Hours Worked module when trying to report to the tasks in which the resource was not planned directly.

• SAP WBS
  • Fixed the Python error message which occurred when deleting SAP WBS elements in the Create SAP WBS Elements module.
  • Fixed the problem that in the SAP WBS module the task values were summarized incorrectly on SAP WBS level.
  • Fixed the problem that in the Effort module variant in the SAP WBS module cost resources and their values were displayed as well.
  • Fixed the problem that in the SAP WBS module the budget field stemmed from the wrong data table.
  • Fixed the problem that the internal STRUC task was displayed in the SAP WBS Elements to Tasks module.
  • Corrected the incorrect message which occurred when trying to delete WBS element assignments that have already been considered in a status report.

• Reports
  • Fixed the problem that additional fields were displayed when zooming in the Budget and Costs per Portfolio, Project, and Year module.
  • Fixed the Python error message which occurred in the Remaining Effort and Costs module if you deleted the grouping value and clicked on the Refresh button.
  • Fixed the problem, that when grouping by type in the Budget, Costs, and Revenues (Delta View) module the grouping name was not displayed
  • Fixed the problem, that in the Resource Load Per Month module the technical project ID was displayed instead of the functional one.
  • Fixed the problem with the error message when opening the effort charts in the Status Report module. See also Work Around.
  • Fixed the problem that after groupings have been deleted and the display was refreshed a cost code record was displayed in the Remaining Effort and Costs module anyway.

• Administration
  • Fixed the problem that an error message was output when trying to import holidays to the Calendar module without having selected a German bundesland. Now, an error message will be thrown.
  • Fixed error message when pressing the Start button in the Resource ID Change module.
  • Fixed the problem, that after filling Left on, the End period was filled with the same date, also if a date < than that in Left on was entered in the End period.
  • Fixed the Python error message in the Resource Data Sheet and Resources modules which occurred when attempting to change periods of the resource which contained no resource calendar. Now a messagewill be thrown at this point indicating that the resource calendar must be filled before periods can be changed.
  • In the Resource Structure module, the Left on column was deleted and hence the error message caused by this column has been resolved.
  • Fixed the Python error message in the Risk Checklist module which occurred when clicking on the Refresh risk values or Reset risk values button in a new risk checklist which does not yet contain risk queries yet Now a message will be thrown indicating that no risk queries have been created yet.
  • Fixed the Python error message which occurred when trying to delete new empty records in the Portfolio Listbox Values module.
  • The Python error message which occurred in the Objective Evaluation Criteria module after adding a new evaluation criterion line and clicking on the Refresh button.
  • When executing the Fast Creation of Employee Data the DI026601 field will not be filled anymore. DI026601 will be removed with database version DB 39.5.12.
  • Fixed the problem that the Attribute name and Filter criterion listboxes in the Object Filter Request module did not show any data.

• Project/Program/Portfolio
  • Fixed the problem that hours worked could not be reported via the Project Core Data module when the person concerned have not been planned in the project yet.
  • Corrected the PDF display of portfolio status reports and adjusted incorrect page breaks.
  • Fixed the problem that process steps in the From plan to project process model had no focus.
  • Fixed the problem, that it was possible to report from the Process Status module to the locked project.
  • Added the missing check of write rights in different project areas, e.g. when creating todo items, for the trend analysis settings, when editing todo items and when editing budget data in the Budget module, SAP WBS elements, etc.
  • Fixed the problem that liability values were automatically deleted on project level when rescheduling, if no values were available on yearly tranche level.
  • Fixed the problem that the info text in the dispatched e-mail was displayed in another format than previously in the Send Info module.
  • Fixed the problem that the % utilization field in the My Department and Resource Planning modules was not colored red if it contained the value 101%.
  • Fixed the Python exceptions which occurred when several global parameters for which particular input values are defined did not contain any values.
  • Fixed the problem that in the Process Status module the part string search on the process model name on the Process model field in the listbox did not work.
  • Fixed the Python error message which occurred in the Resource Plan module when attempting to assign resources via the dialog module.
  • Fixed the problem that for simultaneously running portfolios and programs, projects which had been deleted from the portfolio assignment were not immediately available for selection in programs, but only after Client restart.
  • Fixed the problem that the Task module was empty in particular constellations (e.g. when opening the module from a program) after pressing F7.
  • Improved the performance in the Todo Items module due to a change to the value range of DI051838.
  • Corrected the summarization of the Work parameter on department level for certain cases when the definition on sub resources did not meet anymore with the definition on the department resource.

Customizing and Technology

Features

• Changed the individual number range for @D variables , so that the variable numbers must now contain the customer license. For further information, click here.
• Implemented a check for all variable types which prohibits that variables with the same ID are created more than once. Exception: @D variables, as long as no DI has been selected and the record has not been saved, further variables can be created with the same ID. However, you have to consider that they are then incorrect in use.
• Added recursive relations to the relationship check in the Check Database Consistency module.
• Included the traffic light OLEs in the global settings, so that the changes of their values apply throughout the system. Furthermore, the traffic OLEs have been changed to Awesome font in the PLANTA standard. If you wish to use the old OLEs, the RestoreOldOLEs migration packet must be run.
• Extended the PLANTA Python Profiler modules in the context menu by two functions with which the module or data item of the current line in the customizer can be opened.
• Implemented a message which, when setting summarization type = 5 on projection data fields (DT411), indicates that this summarization type only takes effect if it has been set on the respective data item (DT412).
• Changed the value range type of DI010190 Action to PY.

Bug fixes

• Fixed the incorrect display in the Active parameter due to an incorrect value range.
• Fixed the problem that some SQL statements generated database inconsistencies for object protection fields in the following data tables: DT835, DT859 and DT861.
• Fixed the problem that the B_AddMissingIndexes migration packet failed when updating on MSSQL.
• Fixed the problem that the DeleteStandardConstraintsAfterDBImport migration packet failed due to non-deleted data.
• Fixed the problem that when using the Fast Creation of Employee Data module the transfer was not carried out completely, resulting in inconsistent data.
• Inserted a value range on the Entity name parameter which prevents invalid entries from being saved in the data field.
• Fixed an error in PLANTA link which caused not only data of the last export run to be saved when repeatedly exporting the same data, but data of all export runs, so that the same data existed multiple times in the file.
• Fixed an error in PLANTA link which enabled the columns of an exported CSV to occur multiple times.
• Fixed the problem that when repeatedly importing the SAP structure the existing elements were not updated correctly.
• Fixed the problem, that when creating new data fields in the Data Areas module, the data field behavior was always set to "i2", although the default setting was "i".
• Fixed the problem, that in the User's Module Variants module, unsaved changes were saved without prompt/confirmation when closing the module or pressing F7. Now, a prompt will be thrown.
• Fixed the problem that the ShowConcurrentDAPos migration packet of each of the modules in question logged twice.
• Removed the option to insert new records and define several favorites in the User's Module Variants module.
• Fixed the Python error message which occurred when attempting to run an empty configuration.
• Fixed the incorrect SAP plan costs export interface template.
• Standardized different lengths of the Manager ID and Manager name data items in different data tables.
• Fixed the problem that the Global Variables, Dynamic Variables and User Variables modules were emptied after refreshing via F7 or via the refresh button.
• Fixed the Python error message in the Object Use module which occurred when attempting to open an SQL statement while another one was still running.

Migration Packets

Category	Packet name	Function	Type
Mandatory packet	MoveDeviationOutOfScheduling	Deletes the DI001296 and DI001177 columns from the database which were before calculated by scheduling as the corresponding DIs are virtual now.	Feature
Help packet	RestoreOldOLEs	Changes the symbols of the traffic light OLEs to the previous design used up to DB 39.5.9.	Feature
Help packet	MigratePortfolioWorkAreas	Replaces the former 0099FF multi-portfolio board module by the new 009CSD module in case it has been assigned to an individual work area on part of the customer, since in this assignment the module cannot be replaced during the update.	Feature
Help packet	ChangeDiOfDtByDdiBackgroundHeadersPortfolio Revert_ChangeDiOfDtByDdiBackgroundHeadersPortfolio	ChangeDiOfDtByDdiBackgroundHeadersPortfolio replaces the values in the Dis by means of a predefined list within the migration packet and creates the Revert_ChangeDiOfDtByDdiBackgroundHeadersPortfolio migration packet to be able to reverse these changes again.	Feature
Help packet	ShowConcurrentDAUsages	Logs modules with multiple data area assignment which prevents a module start.	Feature
Mandatory packet	FillColumnType	Fills the column type for all DIs of the current license which do not contain a column type.	Feature
Mandatory packet	CreateUserModuleTable	Creates DT 170 User/module data table with the parameter of which the individual loading of submodules can be controlled.	Feature
Mandatory packet	ExtendColumnResTitle	Extends the maximum number of characters for the DI001275 Resource name field to 200.	Bug fix
Mandatory packet	AddPortfolioChanges	Adds real columns which are required for the new portfolio modules.	Feature
Mandatory packet	EnableDT280PrimaryKey	Activates the primary key constraint of data table DT280 that is required for further migration packets which create the foreign keys for this table.	Feature
Mandatory packet	PortfolioSimulationColors	Initiates project colors for the new portfolio simulation.	Feature
Mandatory packet	PortfolioSimulation	Adds required columns for the new portfolio simulation.	Feature
Mandatory packet	SetPortfolioDefaultPicture	Sets the portfolio logo as default image for already existing portfolios.	Feature
Mandatory packet	AddPortfolioManagerEstimation	Adds real columns that are required for the new project estimate of the portfolio manager for projects in his/her portfolios.	Feature
Mandatory packet	UpdatePersonNames	Changes the notation for names from “surname, first name” to “first name surname” throughout the system.	Feature
Mandatory packet	ExtendPSPPool	Adds further columns to the pool table of the SAP WBS interface template.	Feature
Mandatory packet	AddQualityGateColumns	Adds real columns that are required for quality gates.	Feature
Mandatory packet	ChangeSAPPSPElementCalculation	Adds and removes real columns in the database corresponding to the changed SAP WBS calculation.	Feature
Mandatory packet	CreateTableSapPspAae	Adds new tables and columns to the database for further SAP WBS elements.	Feature
Mandatory packet	AddSapInterfaceColumns	Adds time and structure fields in the database for the SAP WBS interface.	Feature
Mandatory packet	CreateStakeholderPortfolioTable	Creates new tables for portfolio stakeholders.	Feature
Mandatory packet	FixPSBDefaultValue	Changes the standard value of DI062362 Display PSR to 1.	Feature
Mandatory packet	ExtendColumnReportTitle	Extends the field length of DI008702 Report name to 100 characters.	Feature
Mandatory packet	SetParallelSessionsToDefault	Sets the default value for the number of parallel sessions to 3.	Feature
Mandatory packet	ZZZSetDatabaseVersion	Sets the database version to 39.5.10.	Feature
Mandatory packet	CreateWebInterfaceTables	Creates new tables for web interfaces.	Feature
Mandatory packet	SetINITRANS	Changes the INITRANS parameter of all active database tables to prevent ITL shortage deadlocks in Oracle databases.	Bug fix

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	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
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
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	SetObsoletePacketToSucceed	Resolves the problem, that the FixViewColumnLength migration packet failed when using MSSQL databases on Linux systems.	Bug fix
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	ZZZSetDatabaseVersion	Sets the database version to 39.5.9.	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.
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

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.

Version DB 39.5.7

Application

Features

• General:
  • A new matrix diagram for risks was implemented in several modules.
    • Risks/Opportunities (Project), Risks/Opportunities (Program),
    • Risks and Opportunities (Project)
    • Status (Project), Status (Program)
    • Status Report (Project), Status Report (Program)
    • Portfolio
    • In the course of this implementation, new parameters are created for risks (Extent of damage and Probability of occurrence), a traffic light is added on the Risk ID fields and evaluation fields are added for risk traffic lights.
  • Cost trend analysis and effort trend analysis charts show the current data of the entire project structure immediately after opening. Hence, you do not have to refresh by clicking on the button of the same name.
  • The capital value (NPV (without subprojects) and NPV) is now calculated automatically. In the case of an update from DB < 39.5.0 to DB > 39.5.0, please consider the following notes.
  • The Close/Reset menu item has been renamed Update/Reset. The menu item symbol has also been changed.
  • The new @date_time(dd.MM.yy HH:mm:ss) variable has been copied to the print text of the footer of the standard print module (009AFA), so that the current print time is now displayed in the footer.
  • The problem, that for user-defined Skins each text was in capital letters, has been resolved.

• R1:
  • When changing the period in the My Activities module, the scale is now adjusted to the newly selected period as well.
  • The Report to unplanned tasks button in the Work Reporting module has been renamed Post to other projects/tasks.

• R41:
  • Links
    • If external links exist in a project and the status is changed from "Active" to "Archive" or "Inactive" in this project or in the project to which the links lead, the external links are converted to external tasks.
    • A message has been implemented that indicates, upon existence of external links in a subproject that are to be detached from the structure, that external links exist and asks whether they are to be deleted.
    • A message has been implemented that indicates, upon copying parts of the schedule, that the part to be copied contains links to tasks that are not copied.
    • New control routines have been implemented that check, upon insertion of new links or changes to the model parameter whether such changes are possible with the current project relationships. If changes are not possible, respective dialog messages are displayed.
  • The Stakeholder module has been deleted from the Project panel. The functionality has been moved to the Project Core Data module. In the course of this, a new function has been implemented: Generate team from schedule.
  • The Controlling Reports function has been implemented.
  • If a process model was selected and activated in the Process Status module, it can be deleted completely as long as no process steps have been edited.
  • In the status line of the Schedule module, the Scheduling completed message is now displayed after completion of the scheduling.
  • In the status line of the Replanning (Calculation of all Planning Objects) module, the individual calculation phases are displayed one after another. After terminating the replanning, the Replanning completed message is displayed.
  • In the Risks and Opportunities module, the values of the subprojects (if available) are considered accordingly. I.e. all values displayed here are summarized values of the displayed projects and their subprojects (if available).
  • The sorting of the Actual effort, Remaining effort, and Total effort fields in the Schedule module has been adjusted analogously to the Budget, Status, and Progress modules.
  • On the Remaining effort field, a check has been implemented, preventing the manual editing of this field when a resource assignment with MAN load profile is made. This is indicated by a message.
  • In the Resource Plan module, an option for allocating the effort of the resource has been implemented.
  • The Delta View module has been renamed Deviations and has been repositioned. It can no longer be opened via the Schedule module, but is now contained in the Project panel as an individual tab.
  • When copying the entire project structure in the Copy Entire Project Structure module, external links that lie within the structure are copied now as well.
  • In the Deviations module, the bars for project requested dates, project actual dates, and float and delay values are included in addition to the bars for calculated dates.
  • When you try to subordinate an existing project, which is currently active, to another project as a subproject, a dialog message is displayed, pointing out that the project to be subordinated is to be closed. The subordination of an active project is therefore not possible.
  • Due to the merger of the End date and Milestones areas to the Dates area in the Status and Status Report module, an auxiliary module is provided with the help of which the estimates and comments entered in individual areas can be merged. This is necessary when updating to DB 39.5.7.
  • The Milestone Overview (Project) and Milestone Overview (Program) modules have been improved:
    • Display of milestones has been extended
    • (Master)milestones of subprojects can be compared to the main project
• R60:
  • In the Change Request (Program) module, the approved/rejected grouping has been inserted in the Completed requests category.
  • Programs can only be archived (Status=9) or deactivated (Status=2) if all projects assigned to the program have already been archived (Status=9) or deactivated (Status=2).

• R70:
  • In the Portfolio module, the Year virt. field has been adjusted, so that periods can now also be selected if no project has been assigned before.
  • The Objective contribution by groups _, _Objective contribution all groups, Projects by objective and risk contribution and Resource simulation buttons have been moved from the Portfolio Period module to the Portfolio module.

• Administration:
  • In the Cost Type Groups module, the grouping record with the cost type group class was made insertable, in case that the cost type groups must be entered completely anew, e.g. if PLANTA project is installed without demo data.
  • The new Cost type category field (Cost Types module) has been implemented. It serves to check whether the cost types are assigned to the cost type groups, and if so, whether the assignments are correct, in order to make sure that cost data is summarized properly in the cost type groups and is displayed correctly in the Budget module. By selecting the Cost type category = Without assignment, a cost type can be created without assigning a cost type group. See also the AddMissingColumnsInDT470 and AddMissingColumnValuesInDT470 migration packets
  • The reference of the letter buttons in the Users module has been changed from user code to user name (last name).
  • The Reset all process steps function has been removed from the context menu in the Planning Objects (in Table Form) module.
  • It is no longer possible to specify an existing resource in the New resource field in the Resource ID Change module.
  • The Resource ID Change function is available for MSSQL as well.
  • The MV creation and Parallel sessions fields have been included in the Fast Creation of Employee Data module. See also the A_AddMissingColumnsInMP and B_AddMissingColumnValuesInMP migration packets.
  • The Documents Category has been included in the Miscellaneous Listbox Values module under Master Data, so that new document categories have been created that can be selected in the listbox category in the Documents module.
  • The filter criteria of the letter button in the Users module have been adjusted. By filtering by User name instead of User, data is now displayed when using a numeric user (code).
  • The option for importing German holidays from a web service has been implemented in the Calendar module.
  • The No link on master milestones and Cross-project links soft model parameters have been made executable.

Bug fixes

• General:
  • The performance of the object filter in modules of the Multi-project board and Cost overviews panels has been improved.
  • The problem, that the values of the Probable damage DIs were not calculated correctly in the current planning, and that Probable damage and Probable gross profit were not calculated correctly in the status reports, has been resolved. See also FixReportChanceCalculation migration packet.
  • The problem with the value range of DI061212 Export status that resulted from missing text constants has been resolved.
  • The problem, that the benefit values entered in the Project Core Data were not summarized to the Budget module if the manual cost input parameter was active, has been resolved.
  • The Python error message when trying to create and save a new module variant has been resolved.
  • The problem, that the Costs and Effort budget values in DT461 also contained the values of the deactivated cost type groups, has been resolved.
  • The problem, that opening a project via the Go to menu item caused a Python error message while the process model of another project was open, has been resolved.
  • The problem, that no replanning but only a capacity scheduling was carried out in the Replanning (Calculation of all Planning Objects) module, has been resolved.
  • The Python error message that occurred when changing the functional ID if the " ' " sign was used for the new ID, has been resolved.
  • The IndexError: list index out of range error message that occurred in certain constellations when using Extras Go to to open a project has been fixed.
  • The problem, that spaces could be saved when changing the functional ID, has been resolved.
  • The missing space in the {total_sent} / {amount_of_records} sent - {received} received - {failed} failed status message has been inserted.
  • The problem, that the access to particular projects does not work for resources the access code of which contains wild cards in the Access to projects field, has been resolved.
  • The IE: org.hibernate.TransactionException: commit failed- parent key not found error message that occurred when deleting recently posted costs in the Cost Posting module has been fixed.
  • The trace back error message that occurred when opening an archived project has been fixed.
  • The problem, that a project was able to assign itself as a subproject, has been resolved.
  • The problem, that in the project list of the projects, projects that were already assigned to a portfolio were displayed as well, has been resolved.
  • The problem, that no links were possible in projects that have been assigned to programs, has been resolved.
  • The problem, that projects that are dependent on other projects cannot be assigned to the programs, has been resolved.
  • The sporadically occurring problem with the PSP code update for structured tasks has been resolved..
  • The error message that occurred in the Check Reported Hours module when clicking on the Filter button while the Until field was not filled has been resolved.
  • The error messages that occurred if the Replanning (Calculation of all Planning Objects) module was opened, one of the projects displayed in the list was subsequently deleted in another session and the replanning was initiated in the first session afterwards has been fixed. In this context, a check has been implemented that prevents that deleted planning objects remain in the calculation list, or that a project is deleted during replanning.

• R1:
  • The problem, that in the My Activities module only Calc. end and no Calc start was considered when filtering the tasks for the selected period, has been resolved.
  • The problem, that in the Reporting Hours Worked module, the behavior of the Actual load and from/to data fields differed in different records, has been resolved.
  • The problem, that when changing the absence reason from vacation to sickness in the Absence module, the respective field was set empty each time, has been resolved.
  • The problem, that sent info in the Info module cannot be marked as read by the sender and can therefore not be displayed in the recipient's mailbox, has been resolved.
  • The problem, that changing an already saved absence reason (e. g. Absence to Sickness) in the Absence module "reactivated" the availability of the respective resource on the day in question, has been resolved.
  • The problem, that when selecting an absence reason in the Absence module (e.g. maternity leave) only Absence or Vacation was displayed, has been resolved.
  • The problem, that the Send Info module can be opened several times in a row via CTRL + B, has been resolved.

• R41:
  • Dashboard:
    • The problem, that the cost deviation in the Dashboard module was not displayed for all projects, has been resolved.
    • The Python error message resulting from an error in the value range of DI059708 has been resolved.
  • Project Core Data:
    • The Python error message that occurred in the Send Info module after clicking on the Send button has been resolved.
    • The problem, that after creating a new risk category, the category in the Category name of the Project Core Data module is not displayed, has been resolved.
    • The error message that occurred when clicking on the End evaluation button in the Idea Core Data, Proposal Core Data, and Project Core Data modules has been resolved.
    • The problem, that the Locked checkbox in the Proposal Core Data module was not editable and therefore reporting to proposals was not possible, has been resolved.
    • The problem, that the records in the Select Stakeholders module could be moved with Drag&Drop, has been resolved. Moving is no longer possible.
  • Budget :
    • The problem, that when using the manual cost input model parameter, the gross profit values entered in the Project Core Data module were not copied to the Budget module, has been resolved.
    • The problem, that the summarized values were not deleted accordingly on project level when using the p_project_budget_edit global parameter = 1 after deleting the budget values on the yearly tranches, has been resolved.
    • The problem, that the revenues were summarized from the wrong columns from DT472 (from the effort columns instead of the cost columns) to the revenue columns in DT461 and DT861, so that in the case of conversion factors > 1, wrong values were contained in DT461 and DT861, has been resolved.
    • The problem, that the values in the deviation fields in the Budget and Critical Projects modules differed, has been resolved.
    • The problem, that the summarized values on project level were not deleted, although all values in all yearly tranches were deleted, has been resolved.
    • The Python error message that occurred when opening the Budget module while the project_budget_approved_edit parameter in global settings was set to 1 has been resolved.
    • The problem, that the budget of the projects assigned to the program in the Budget (Program) module was not summarized to the Cost budget column (DI060180 and DI060493), but to the Program budget column (DI060178 and DI060491), has been resolved.
    • The problem with the display of cost/effort budget graphics in the Cost Reports and Effort Reports modules of the structured projects (only main project data was displayed) has been resolved.
  • Schedule:
    • The problem, that the data in the Milestone trend and Master milestone trend variants was not displayed immediately when changing to the variants, but only after saving in the Configure Trend Analysis module, has been resolved.
    • The problem, that the bars for actual dates were covered by the bars for calculated dates due to a wrong sequence of the bar DIs in the module customizing, has been resolved.
    • The problem, that users were able to open and edit tasks in the Task module, for which they have no rights, has been resolved.
    • The error message that occurred when saving after copying a new schedule to a new project in the Schedule module has been fixed.
    • The problem, that resources in the Schedule module have been assigned to tasks that have created reportings to non-planned tasks in the Reporting Hours Worked module but have not been saved, has been resolved.
    • The problem, that after changing the functional ID of a project the gates in the Schedule of this project are not displayed, although the Schedule with gates checkbox is activated, has been resolved.
    • Different period filters in different areas in the Utilization with Cause module were standardized.
  • Task
    • The problem, that the LB in the Resource name field in the Todo item area displayed the stakeholders of another project, has been resolved (Filter @D15 replaced by @L30).
    • The error message that occurred in the Task module when saving after adding a new task document has been fixed.
    • The problem, that no task documents could be created or saved, as well as the Exception listed below that occurred in this context, have been resolved.
      • Under Oracle: ORA-02291: Integrity constraint ([DB_USER].FKDT815ID441) broken - parent key not found or ORA-02291: Integrity constraint ([DB_USER].FKDT815ID441) broken - parent key not found
      • Under MSSQL: The INSERT instruction is in conflict with the FOREIGN KEY restriction 'FKDT464ID441'. The conflict occurred in the [DB_USER] database, table 'dbo.DT441', column 'DI000446'.
  • Include subproject into the structure:
    • In the Include Subproject Into the Structure module, existing projects can no longer be assigned as subprojects if they already belong to a program or a portfolio.
  • Todo Items:
    • The Python error message that occurred when opening the Edit task context menu command has been fixed.
  • Microsoft Project :
    • The problem, that the export to MSP cannot run correctly due to a missing background module, has been resolved.
    • The problem, that incorrect data is displayed in the PLANTAProject vs. Microsoft Project module, has been resolved.
    • The problem, that structure tasks were displayed in the PLANTAProject vs. Microsoft Project module, has been resolved.
    • The problem, that after export the same message was written in the logfile several times (depending on how often it was output), has been resolved. Now the message is written once and the number of outputs is specified.
    • The ORA-02091: transaction was reset\nORA-02291: integrity contraint error message, that occurred when importing an XML file in the Microsoft Project module, has been fixed.
  • Status and Status Report:
    • The problem, that the trend arrows in the Status did not display positive trends, has been resolved.
    • The problem, that the trend arrows in the Status module displayed deviations immediately after the creation of a baseline if no changes had been made yet, has been resolved.
    • The problem, that in the Status module of the subprojects the status reports of the subprojects were not displayed, although they existed, has been resolved.
    • The problem, that for structured projects in the Status Report module, data of the parent project was partially displayed in the charts of the subprojects, depending on the project level from which the status report was opened, has been resolved.
    • The problem, that a project can be deleted despite assignment of a project status report to a portfolio status report, has been resolved.
    • The problem, that the costs in status reports varied if the status reports were created from different source modules, e.g. from the Status and Check Status Report Creation and Project Requests modules, has been resolved.
    • The problem, that costs and effort trend charts were only displayed if a baseline and a released status report existed, has been resolved.
    • The different length of the Category fields in the opportunity and risk tables (DT812, DT810) as well as in the respective report tables (DT872, DT831), which lead to a Python error message if values were entered in live tables that were longer than the length of the fields in the report tables, has been standardized. See also FixReportColumnLengths migration packet.
    • The problem with the wrong reference of the traffic light and the respective deviation values in the Dates area was resolved in the Status and Status Report modules. Now the traffic light refers to the worst of both deviation values (project end date or master milestone end date).
    • Cost trend and effort trend charts in the Status and Status Report modules can now be structured, i.e. in the respective charts the data of the selected project and summarized data of all of its subprojects is contained.
  • Deviations:
    • The problem, that the negative deviations were not displayed, has been resolved.
    • The problem, that the Number of deviating tasks field was calculated incorrectly, has been resolved.
    • The problem, that the tasks that did not contain any effort were marked as new as well (e.g. milestones), has been resolved.
    • The problem, that the Total effort field in the No longer exists in the current planning area did not contain values, has been resolved.
  • Risks/Opportunities
    • The problem, that the risks and opportunities deactivated or deleted in the Risks/Opportunities module are displayed in the Status and Status Report modules regardless, has been resolved.
    • The problem, that the values in the Probability and Possible fields in the Status module of the main project were not updated after the respective fields were changed in a subproject, has been resolved.
    • In Risks/Opportunities (Project) and Risks/Opportunities (Ideas/Proposal), the fields in the area bars that only display the sum values from all (active and inactive) risks and opportunities were replaced by new, correct project fields (DT461) to which the values from individual, only active risks and opportunities are summarized.
  • Project Application:
    • The sorting of the project phases in the Status Report and Project Application modules has been corrected. Attention: This applies to status reports/project requests that are newly created from now on. In those already created, the sequence remains the old one. See also AddMissingColumnsInDT877 migration packet.
    • The error message that has occurred in the Project Applications module when clicking on the Create project application has been fixed.
  • Process Status:
    • The problem, that the info that was sent from the Process Status module (e.g. when submitting the phase) was not displayed in the Inbox area but under Read info in the Info module, has been resolved.
    • The Python error message that was displayed in the Process Status module when activating a process model while a value that is neither a valid resource ID nor a valid Python ID that contains a resource ID was specified as a Placeholder in the Process Model Templates module.
    • The problem, that in the project request created via the Create project request process step in process model 8 (proposal) no costs and effort was displayed, has been resolved.
    • The error message that occurred in the Process Status module when assigning a process model to a project while another project was also open for process model assignment has been resolved.
    • The missing tree structure in the Completed phases area in the Process Status module has been added.
    • Problems with the part string search in the Resource name listbox in the Process Status module.
    • The problem, that when copying a project, the process steps of the source project are copied as well, has been resolved.
    • The problem, that a Python Exception message was displayed when you stored two records with identical data in the Cost Posting module and try to delete one of them, has been resolved.
  • Resource Requirements
    • The problem, that filtering by date via the from/to fields did not take effect, has been resolved.
  • Remaining Effort and Costs
    • The Python error message that occurred when trying to update the grouping has been resolved.
  • Earned Value Analysis: Divers problems have been resolved:
    • Problems with the update of the data display after the creation of new status reports.
    • Incorrect chart files
    • Problems with the traffic lights
    • Problems with Earned Value data in structured projects.
  • Overview and evaluation module
    • Performance problems, that have occurred in the Resource Utilization by Code module due to missing filter criteria, have been resolved.
    • The problem, that all bar for the projects with different project code were displayed with the same symbol (same color) in the Resource Utilization by Code and Resource Utilization by Skill modules, has been resolved.
    • The problem, that the Remaining load field in the Resource Load per Month module was calculated incorrectly, has been resolved.
    • The problem, that the Cost budget (current) field in the Budget, Costs and Revenues (Delta View) module is not filled, has been resolved.
  • The problem, that the Object Filter module behaved erroneously if a filter was created for which no objects were found, has been resolved.
  • The problem, that after creation of a new resource via the Fast Creation of Employee Data module, the values of the from and to fields were not displayed in the Start period and End period fields of the Resources module, has been resolved.
  • The error message that occurred after clicking on the Include in chart button in the Cost Trend Analysis has been fixed.
  • The problem, that when canceling the release of a status report in the Check Status Report Creation and Project Applications, the This function is only available for released status reports. message was erroneously displayed, has been resolved.

• R43:
  • The problem, that the resource manager could delete periods of a resource, although he/she does not have the necessary rights for this, has been resolved.
  • The problem with the incorrect calculation of the percentage values in the Resource Planning and My Department modules and the incorrect traffic light display connected with it, has been resolved.
  • The problem, that the overload traffic light in the Resource Planning and My Department modules did not switch to red if the overload was > 1000%, has been resolved. The problem with the immediate switch of the focus from the Absence module to the My Activities module after the absence for a particular resource was opened from the Absence module in the Department Board, has been resolved.
  • The problem, that the department manager without multi-project manager rights was able to delete the resource periods in the Resource Data Sheet module, has been resolved.

• R50:
  • The problem, that a multi-project manager can edit and delete requests without having request-manager rights, has been fixed.

• R60:
  • The problem, that under MSSQL the project data is not summarized to programs after clicking on the Recalculate button in the Budget module, has been resolved.
  • The problem, that when carrying out a Replanning

, the budget and cost data of programs in the Budget module was not refreshed, has been resolved.

• • The problem of several entries in the user menu after pressing F7 has been resolved.
  • The error message that occurred in the Status module when creating a Program Status Report or a program baseline has been resolved.
  • The problem, that when creating a new program, the Program Core Data module was not displayed correctly, has been resolved.
  • The problem, that the Cost budget, Total effort, Effort budget DIs are not filled for programs, has been resolved.
  • The Unhandled Python Exception in macro 009AK2 Python error message that occurred when clicking on the Update button in the Program Application and Program Status Report modules has been fixed.
  • The problem, that the milestone/master milestone trend graphics in the Status module only displayed the values from the last status report, has been resolved.
  • The error, that the The planning object contains no load records. message was displayed when creating or releasing program status reports, has been fixed.

• R70:
  • The problem, that when deleting a newly created, not yet used group in the Portfolio Listbox Values module, the One or several listbox values are already used in the portfolio evaluation criteria and risk checklists and can therefore not be deleted. message was erroneously displayed, has been resolved.
  • The problem, that when using the p_project_budget_portfolio_relevant global parameter = 1 under MS SQL, the project budget was not transferred to the Relevant column, has been resolved.
  • The problem, that in the Objective Contribution by Groups and Objective Contribution all Groups modules a Python error message was displayed if the Cost budget requested or Cost budget approved value was selected in the Bubble listbox in the Portfolio Analysis, Scoring module, has been resolved.
  • The problem, that the p_project_budget_portfolio_relevant under MSSQL did not work properly, has been resolved.
  • The problem, that in the Portfolio module in the Risks and Assigned planning objects areas different IDs were displayed for the same planning objects, has been resolved.
  • The problem, that the Client in the Portfolio Status Report module crashed when clicking in the empty chart, has been resolved.
  • The missing OLE symbol for the manual estimate (thumb right) in the Edit Portfolio Status Report module has been added.
  • The problem with non-existent data in charts in the Objective Contribution all Groups module, has been resolved.
  • The problem, that the source data for the charts was displayed in the Portfolio Overview module, has been resolved.
  • The error message that has occurred in the Portfolio Overview module when extending several portfolios has been fixed.
  • Problems with the deletion of portfolio assignments, the assignment of the portfolios to projects, and the opening of portfolios from the My Portfolios module have been resolved.
  • The error message that occurred in the Portfolio Analysis, Scoring module when clicking on the Objective contribution all groups and Objective contribution buttons has been fixed.
  • The problem, that when assigning a planning object to the portfolio, the "One of the selected projects is already assigned to a program." error message was erroneously displayed in the Assign Projects, Ideas, or Proposals to Portfolio module if none of the selected planning objects were assigned to a program, has been resolved.
  • The problem, that in individual modules in the Projects, Proposals, Ideas, and Programs panel, the assignment of objects to groups ... with portfolio assignment and ... without portfolio assignment is carried out incorrectly, has been resolved.
  • The problem, that in the Delete module project status reports are also displayed under program status reports, has been resolved.
  • The problem, that in the Portfolio Period module the links on planning objects for which the functional ID <> technical ID does not work, has been resolved.
  • The Python error message that occurred when trying to delete an evaluation criterion from the Evaluation Criterion module has been fixed.

• Administration:
  • The problem, that the absence of the resources was not considered in the creation of the periods, has been resolved.
  • The problem, that after activating the Earned Value Analysis in the Model and Model Parameters module, the The planning object contains no load records. message was displayed, has been resolved.
  • The Python error message that occurred in the Cost Types module when pressing the F1 key while the Cost type class field was focused has been fixed.
  • The problem, that the required cost type group could not be activated, although all assignments to cost types were removed due to the existing but invisible assignment to cost types "-", has been resolved.
  • The problem, that when clicking on the Reset password button in order to reset a password, no feedback was given by the program if no entry was available for the smtp_server_adress parameter in the Alpha (120) field in the Global Settings, has been resolved.
  • The problem, that an e-mail address is not copied from the e-mail field to the Internal e-mail field in the Persons module, has been resolved.
  • The problem with the deletion of skills in the Skills module, has been resolved.
  • The problem, that the Resource field is not cleared after the resource ID change in the Resource ID Change module, and hence the resource ID change could be started again for the same resource, has been resolved.
  • The error message that occurred when opening the Planning Objects (in Table Form) module has been fixed
  • The problem, that when clicking on the Create status report button in the Check Status Report Creation and Project Applications module, status reports are created that do not contain the changes at the time of creation, has been resolved.
  • The problem, that in the Absence module (view module) the absence and vacation values that contained half days were rounded up to full days and thus displayed deviating values compared to the Absence module (editing module), has been resolved.

• Miscellaneous:
  • A wrong message, that occurred when trying to open a planning object without having the required rights, has been fixed.
  • The problem, that the Open Directly via Functional ID function (Extras Go to menu item) does not check the access rights of the user (@53 on the cost center structure code), has been resolved.
  • For the following DIs, automatic numbers that are not required have been removed. DI001200 Project successor ID, DI001201 Task successor ID and DI001203 Predecessor.
  • The problem with the double use of DI034517 Probable damage as a real and virtual DI has been resolved.
  • The problem with cut off buttons due to missing DF widths has been resolved.
  • The missing value in the Task (functional) field is now displayed in the Check Reported Hours, Week Calendar and Reporting Hours Worked modules.

Customizing and Technology

Features

• General
  • The following improvements have been made to the Check Database Consistency:
    • Hyperlinks:
      • Use (DI, DT, primary key) is corrected.
      • For hyperlinks that do not exist in the hyperlink DT, the ID in the reference DT is set to 0.
      • Non server-based hyperlinks without URL and name (text) are deleted.
      • For server based hyperlinks, the URL or the name is generated automatically.
    • I-texts:
      • Use (DI, DT, primary key) is corrected. "Object protection:
      • Logfile: "Datatable without rwd" was changed to "Datatable has protection DIs, but without values"
      • No more empty DTs are checked
      • Only DTs with a value in "pos_os" are checked (without pos_os, no object protection).
  • The DT listbox in the Data Dictionary module was extended by the variable name.
  • In DT806, the relation to DT463 was removed and the respective relations were added in the module customizing of the standard modules that use this table. If you use individual modules with these tables, their customizing must be checked and adjusted if necessary.
  • The behavior of the DF behavior parameter for data items of class 16 (Hyperlink) and for the background DI, has been changed.
    • When assigning a hyperlink data item to a data area, the value in the DF behavior is automaticaly set to "h".
    • When assigning the DI025581 background data item to a data area, the value in the DF behavior field is automaticaly set to "a", but can be changed manually afterwards.
  • If a DI is deactivated, it is displayed grayed-out in the Data Dictionary module and in the listbox on the DI field in the Data Areas module.
  • The Form editor menu item Define tab order has been removed.
  • The column type of DI059758 from DT324 has been changed from NUMBER to NUMBER(10,0).
  • For the creation of a status report, you can now use respective column names in the customizing instead of the DI numbers in SQL statements.
  • A dialog message that warns users when trying to reactivate data items deactivated by PLANTA has been implemented.
  • In the PLANTA Module Customizer, a new module (Object Use) has been implemented that serves to find the objects in the PLANTA customizer.
  • In the Database Schema Export module, a check has been implemented. If an incorrect or invalid path is entered, the Invalid path message is displayed.
• PLANTA link:
  • The PLANTA link role has been revised and designed more user-friendly. For this purpose, some modules have been changed and new modules have been added.
    • Execution
    • Systems
    • Open Transactions
    • Stamping of date and user when importing/exporting load records
    • New Extended Configuration Options module
    • New Generate Definition module
    • New converter functions in PLANTA link
    • The PLANTADateToString converter now works without preceding ToInt converter.
    • New enricher (LeftPadder and RightPadder) in PLANTA link
  • In the current version, PLANTA makes two new interface templates available: Project import and Main project export.
  • In the Configuration module, individual mapping elements can be inserted subordinate to an existing mapping element via the new Insert child mapping button.
  • The validation mechanism has been improved: It is now checked whether one and the same module is used several times in a configuration (simultaneously in different functions, e.g. as source and target, or as pool and target).
  • The connection to an SAP system is established once, so that it can be used by different modules and does not have to be established anew each time a module is opened.

Bug fixes

• General
  • Problems with adjusting the database schema, that occurred when updating the database from 39.4.4.0 to 39.5.x, have been resolved. The ModifySchemaTables migration packet was corrected.
  • The Python error message that occurred when clicking on the Open macro editing button in the Edit Board Settings module, has been resolved.
  • The problem with missing owner licenses on some standard objects, which e.g. entailed that no entry was found in the Wiki via F1, has been resolved.
  • The following error message has been fixed: Database schema does not match System Customizing / Data Dictionary: No DB lenghts specifications in DT: V_DT430_DT472 * Column: POS, Type: NUMBER * Column: SAP_STATE, TYPE: NUMBER.
  • The problem, that the Reload system customizing button was displayed after filtering in the Data Items module, has been resolved.
  • The problem, that the changes to the submodules (DT404) did not entail that the respective parent modules were displayed in the MOD listbox in the Modules or Modules of the Last 30 Days modules, has been resolved.
  • The Python error message that occurred in the Users module when clicking on the Reset password button while the smtp_server_adress parameter was not set correctly in the Global Settings module has been fixed.
  • The Python error message that occurred in the Check Database Consistency module when clicking on the Carry out check button while the Consistency check field was not filled has been resolved.
  • The Python error message that occurred in the Define Incarnation/Fetch Exit module when clicking on one of the two buttons while the Fetch DT and Fetch DI fields were not filled has been resolved.
• PLANTA link
  • An error in PLANTA link, that lead to incomplete records being saved, has been resolved.
  • The problem with the wrong sorting when using the MtsExportPoolLoadModule Python module subclass and the sorted = 1 parameter, has been resolved.
  • The problem, that the Execution module was not focused when repeatedly selecting it from the context menu, has been resolved.

Migration Packets

Category	Packet name	Function	Type
Mandatory packet	DeleteIndices	Deletes indexes that were adjusted and recreated during schema generation.
Mandatory packet	CreateDataitemsForAccountedReports	Creates necessary DIs for the controlling reports
Help packet	PlaceholderCheckPacket	Carries out a correction of the incorrect dash records in the course of a database consistency check
Help packet	HyperlinkCheckPacket ItextCheckPacket	Each carry out a correction of the incorrect hyperlinks and a correction of the incorrect I-texts in the course of a database consistency check
Mandatory packet	AddSchemaExtensions	Creates indexes and constraints that do not result from the PLANTA customizing
Mandatory packet	UpdatePeriodAggregationQuery	Resolves the problem, that the basic load in the Resource Planning module was only summarized to the next parent level. See also the migration packet of the same name in S 39.5.17
Mandatory packet	MoveTablesToDifferentSchema	Moves the DT874 and DT875 tables from the Q3B schema to the Q5B schema and adjusts the automatic number for DI000443.
Mandatory packet	FixEarnedValueSubprojects	Corrects the display of the Earned Value Analysis module data of the structured projects	Bugfix
Mandatory packet	AdjustWrongColumnLength	Corrects the length of some columns
Mandatory packet	FixReportChanceCalculation	Corrects the calculation of the Probable damage and Probable gross profit parameters in status report tables
Mandatory packet	DeleteInconsistentStandardData	Deletes inconsistent standard data in order to secure the integrity of the database
Mandatory packet	SetOwnerLicenseForZZZRecords	Changes all owner license entries ZZZ to 011
Mandatory packet	AddIndexesOnColumnsForDataTableListbox	Adds indexes on columns, that are used in the data table listbox in order to improve the performance of loading the data tables.
Mandatory packet	DeleteStandardConstraintsAfterDBImport	Deletes all standard constraints on the standard columns including Unique Constraints and primary keys.
Mandatory packet	UnloadAndReplan	Carries out an unload and subsequently a replanning of all active planning objects after a DB update. Note: If the packet fails, you have to check the status of the A_CreateConstraints migration packet. If there are still incorrect constraints, they must be corrected before the UnloadAndReplan migration packet is run again.
Help packet	EnableConstraints	Activates all constraints. It is only required for the validation of the non validated constraints after data correction if A_CreateConstraints failed. Subsequently changes the status of the A_CreateConstraints migration packet to completed. Must only be run after all data which was reported in A_CreateConstraints has been corrected.
Mandatory packet	A_CreateConstraints	Creates constraints after the DB import
Mandatory packet	DeleteStandardConstraints	Deletes all constraints on the standard columns, except unique constraints and primary key before the DB import
Mandatory packet	AddMissingIndexes	Adds missing indexes
Mandatory packet	CorrectOwnerLicense	Corrects records with missing owner license
Mandatory packet	SetLanguageDT462	Adds language codes to the primary key of DT462
Mandatory packet	ShortenCRCColumns	Shortens the length of the CRC fields in the hyperlink tables to 10 according to the length in the database
Mandatory packet	AddNewIndexes	Creates new indexes for the improvement of the performance
Mandatory packet	ChangeLanguageOfPeriodCreation	Optimizes the generation of resource periods
Mandatory packet	AddLogTimestampColumn	Adds time stamp column in particular SQL queries
Mandatory packet	SetDistriblistEmpty	Deletes all distribution list headers from DT405
Mandatory packet	AddNewRiskChanceSums	Creates new columns for project risks and opportunities in DT461
Mandatory packet	AddMissingCostColumns	Creates missing revenue and gross profit columns in DT835 Budget/Co/Benefit for each Year/Report
Mandatory packet	AddMissingColumnDT343	Creates the missing column (DI063743) in DT343 SQL procedure code
Mandatory packet	AddProjectPoolTable	Creates data table 567 Project pool in the database
Mandatory packet	A_AddMissingColumnsInMP	Adds new columns to DT566. For this purpose, see the 14635 entry.
Mandatory packet	B_AddMissingColumnValuesInMP	Creates necessary values in the new columns in DT566
Mandatory packet	AddMissingColumnsInDT877	Adds missing columns in DT877 Object process/report. For this purpose, see the 14022 entry.
Mandatory packet	AddMissingColumnValuesInDT470	Adds values in the new Type column in DT470. For this purpose, see the 14504 entry.
Mandatory packet	AddAMissingColumnInDT470	Adds a new column (Type) in DT470 Cost type. For this purpose, see the 14504 entry.
Mandatory packet	FixCostTrendsAndEVA	Corrects a view, that serves as a data source for cost trends and Earned Value Analysis. This resolves the problem that charts displayed planned costs in baselines and status reports for other reports	Bug fix
Mandatory packet	FixPeriodCreation	Resolves the problem when creating the periods for resources the ID of which is longer than 20 characters
Mandatory packet	FixReportColumnLengths	Corrects the field length of DI 008876 and 029636 in order to fix inconsistencies between status reports and live data
Mandatory packet	AddCostsLastReportPerYear	Corrects incorrect calculations of benefit-costs and revenues-costs in the Objecive Contribution all Groups
Mandatory packet	AddIndexOnPoolTables	Sets indexes on the Status and Transferred on columns in all pool tables in PLANTA link
Mandatory packet	AddNewInterfaceParameterFields	Adds new interface parameters: Hidden and Locked
Mandatory packet	AddNewStampFields	Adds data fields in which the export/import user and the import/export date is stamped upon export/import of load records in PLANTA link
Mandatory packet	AddMissingListboxValueColumns	Adds listboxes on the Object field of the mapping elements according to the mapping element type
Mandatory packet	AddNewInterfaceSQLObjects	Creates new PLANTA link tables and columns
Mandatory packet	FixCrcColumnLength	Corrects the column width of the crc columns in hyperlink tables
Mandatory packet	FixViewColumnLength	Corrects the specification of the column length of "Pos" and "SAP state" in the V_DT430_DT472 view
Mandatory packet	FixProgramTrafficLights	Fixes the problem, that the Cost Budget, Total effort, Effort budget IDs are not filled for programs which results in incorrect traffic light display in the Status and Program Status Report modules
Mandatory packet	CreateViewMapping	Creates the MAP_DBA_VIEWS tables that are used in the Object Use module
Mandatory packet	CreateFederalStateColumn	Creates the FEDERAL_STATE column in DT430
Mandatory packet	ExtendDescriptionColumn	Enlarges the Description column in DT560
Mandatory packet	AddIndexesOnColumnsForModuleListbox	Completes indexes for columns in connection with the MOD module listbox in the Modules module
Mandatory packet	DeleteUnnecessaryMigrationPackets	Deletes the FixDT093ValueRanges and FixTimeBudgetMatrix migration packets
Mandatory packet	AddingProbabiltyAndDmgdimensionDIs	Completes missing columns in the DT810, DT831 and DT461 tables that are necessary for the new risk charts
Mandatory packet	RemoveVersionColumn	Removes the version column from the migration rule table. See also A_ReplaceOldFrameworkCustomizing, B_SucceedPreviousMigrationFramework, and ReplaceOldFrameworkCustomizingVenus.	Feature
Mandatory packet	FixV_EVA_VG	Corrects the FixV_EVA_VG view
Mandatory packet	z_AdjustSchema	Carries out adjustments to the schema
Mandatory packet	DeleteStandardConstraintsQ1BandQ2B	Deletes all constraints to standard columns in Q1B and Q2B, except Unique Constraints and primary key
Mandatory packet	FixLoadAutoNumber	Corrects the function for the creation of automatic numbers of work reportings
Mandatory packet	DeleteWrongOLEs	Deletes wrong OLEs that have the same number
Mandatory packet	FixColumnPrecisions	Corrects incorrect specifications on the column accuracy
Mandatory packet	DeleteStandardIndices	Deletes indexes of UUIDs, that are subsequently created during schema generation after database import. Furthermore, some standard indexes that are no longer required are removed.	Bug fix
Mandatory packet	ZZZSetDatabaseVersion	Sets the database version to 39.5.7

Version DB 39.5.6

Warning

• When reinstalling DB 39.5.6 with MSSQL and Server 39.5.14, the following script is to be run immediately after the installation in order to guarantee performance improvement.

Features

• The name of a project request cannot be changed manually. When creating a project application, the "Project Application" string is automatically entered in the name field.
• The Project dependency exists checkbox in the Portfolio module is now displayed as deactivated for programs since programs cannot have any dependencies.
• In the Check Database Consistency module the filter criterion that only filters by database instances of the xxB schema has been removed. From now on, all activated database instances of the current license are displayed.
• In the Mapping Parameters module, a link has been implemented on the name of the mapping function that opens the parameter description in Wiki.
• The display control of the resources in the Absence of the Department module has been changed. This is no longer done via the @32 variable on the Resource structure code field, but via @L80 on the Parent resource field.
• If e-mail dispatch was selected when sending a message in PLANTA project, but no e-mail address was selected for the respective user, the The recipient has not specified an e-mail address is output.
• The Resource Plan module for quick view and editing of the resource assignment of the project has been added to the Project panel.
• The module listbox in the Modules module and the Modules Of The Last 30 Days and Macros of the Last 30 Days modules show all modules to which changes have been made in arbitrary areas (e.g. Changes to header data, submodule assignments, data area assignments, etc.).
• Listbox values from the Portfolio data area cannot be deleted if they are already used in the evaluation criteria or risk checklists.

Bug fixes

• The problem, that when using the manual cost input = parameter, the annual values in the Budget module was not summarized to project level, has been resolved.
• The Python error message, that occurred in the Roles module when clicking on the Module column, has been fixed.
• The problem with the incorrect display of the % deviation values in the % deviation field on cost type group level, has been resolved.
• The problem, that a technical module is displayed when trying to assign a project to a portfolio, has been resolved.
• The problem that OS fields are filled incorrectly in DT285 has been resolved.
• Various problems with structure projects have been resolved, e.g., changing the availability of the subprojects in the Check Reported Hours module and the inheritance of the HPR-Status to TPRs, etc., in the watchlist.
• The problem, that in the Evaluation Criteria module several evaluation criteria cannot be deleted at once, has been resolved.
• The Python Exception Python error message, that has occurred due to the non existing entry in the plan_working_hours parameter in the Global Settings, has been fixed.
• The problem, that after creating new projects and carrying out the capacity scheduling without a schedule or single tasks having been created in the Dashboard module, the number of tasks is displayed anyway, has been resolved.
• The problem, that when defining the hours to be worked in the Edit Hours to be Worked dialog module it is not copied from the dialog module to the Resources module, has been resolved.
• The problem, that in the Budget module the values are overwritten on sum level although there are no values in the yearly tranches, has been resolved.
• The problem, that during calculation of the budget of the programs that contain one or more projects with status=9 (Archive) the The following planning objects have been excluded from the calculation because their status has not been set to "active" message is displayed although the values of the respective project are included in the program, has been resolved. The message is no longer displayed.
• The problem with copying schedules has been resolved.
• Missing data in the Cost budget approved active SB total field are now displayed.

Migration Packets

Category	Packet name	Function	Type
Mandatory packet	FixWrongColumnType	Changes (corrects) the incorrect column type for particular columns in DT 483
Mandatory packet	FixProgramBudgetForPortfolioBaseline	Corrects program budget values that are necessary for the display of the portfolio baseline.
Mandatory packet	ZZZSetDatabaseVersion	Sets the database version to 39.5.6
Mandatory packet	FixResourceIdentChange	Solves the problem that the resource ID change does not work correctly under Oracle. Under MSSQL, this function is temporarily not available.	Bugfix

Version DB 39.5.5

Features

• When creating a new project (proposal, idea), no more capacity scheduling is carried out automatically.
• In the Portfolio Status Report module you can now refresh data by clicking on the Refresh button at the bottom of the module instead of the Refresh view button. The Refresh view button has been removed from the Configure Portfolio Status Reports module.
• The procedure for inserting documents via the Create documents button in the Documents module has changed.
• The Tools menu was changed partially.
• The earned value analysis is versionized from now on (is included in status reports).
• When creating a new status report, an automatic complete recalculation of the entire project is carried out (dates, costs, budgets).
• The Check Status Report Creation and Project Applications module has been extended by program and portfolio status reports and program applications.
• If the Refresh button is clicked on in a non-released Project Status Report or Program Status Report, the affected project or program is recalculated and the refreshed data is included in the status report.
• If you have used a particular filter in a module with object filter and switch to another module with object filter subsequently, the filter from the previous module also takes effect in the newly opened module.
• In the Utilization by Skills module, the display of resources has been restricted to those the current user can access. As a result, the performance of the module has improved.

Bug fixes

• The problem with the display of symbols has been resolved.
• Todo notes and checklist items are displayed in the Schedule module now if they have been assigned to a resource.
• The problem, that the Conversion Factors can be deleted although they are assigned to one/several resources. Messages, indicating that the conversion factors cannot be deleted if they are assigned to resources, have been implemented.
• The problem, that the value in the Plan deviation (SV) field is calculated incorrectly in the course of the EVA, has been resolved.
• The problem, that the Completed proposal note symbol (green checkmark) in the Schedule module does not disappear automatically if the actual end date of the task is deleted, has been resolved.
• The problem, that in the My Activities module the filter is only considered on the to field and not on the from field, has been resolved.
• The Python error message in the Process Status module when carrying out submission and approval process steps, has been resolved.
• The problem, that when trying to assign a single resource in the Schedule module not the same resource list (Resource Name field) is displayed as if trying to assign several resources (Resource List module), has been resolved.
• Checkboxes are now supported language independent by PLANTA link.

Migration Packets

Category	Packet name	Function	Type
Mandatory packet	AddNewProcessModelSchema	Adds new Insertion permitted, Deletion permitted and Placeholder in the process model tables 496, 497, 498, 499.
Mandatory packet	ChangeCustomizingForDialogModules	Makes changes to the customizing of dialog modules.
Mandatory packet	ReportColumnEingetretenIsMissing	Adds the missing Achieved column for risk and opportunity data areas in report modules.
Mandatory packet	ExtendDeleteProjectFunction	Adds a dialog message indicating that the project assigned to the portfolio cannot be deleted because it possesses a status report that is used in the portfolio status report.
Mandatory packet	RelationProjectToPortfolio	Adds a check on the existence of a project status report in a portfolio status report, if the affected project is to be deleted.
Mandatory packet	ZZZSetDatabaseVersion	Sets the database version to 39.5.5

Version DB 39.5.4

Features

• Programs have been added to the Overview by Type module and the new Programs submodule has been added to the Projects, Proposals, Ideas, and Programs panel.
• The new Assignment: User to Role module has been added to the Administration panel.
• The Refresh button has been delted from the Portfolio Status Report module.
• The Recalculate button in the Budget module carries out a capacity scheduling as well now.
• In the Work Reporting module, the tasks finished in the current week are displayed separately below the Finished tasks of the current week heading.
• If a Left on date is set for a resource, the End period field is automatically filled with the same date.
• If a module does not yet contain a Python macro and if the Python Macros module or the Python editor from the Modules module is opened for this module, you can define whether a macro template is to be copied in or not by confirming the Yes/No query in the displayed dialog message.

Bug fixes

• The error message which occurred when trying to create a status report in a program without carrying out a budget scheduling while the projects assigned to the program contained budget data, has been resolved. Reason: Missing data in DT835
• The problem with saving newly created notes and dashboard entries in the Documents (Project) and Documents (Program) and Documents (Request) modules has been resolved. For this purpose, see also the SaveNotesIsNotPossibleInModuleDokumente migration packet.
• In the Cost Posting module (formerly Material Cost Posting), only cost resources (resources with Resource Type=9) can be selected now.
• The problem, that only 4 standard categories are displayed in the Evaluation data area (company risks) in the Project Core Data module and no individual ones, although individual ones have been created in the portfolio master data and included in the required checklist in the Risk Checklist module.
• The validation of the e-mail address has been deactivated in PLANTA project so that when sending a password to an e-mail address with invalid characters, no Python error message is displayed.
  • Since e-mail addresses are no longer validated, PLANTA project administrators must make sure that the e-mail address is entered correctly, otherwise the recipients in question do not receive any e-mails (e.g. in the case of a password change).

Migration Packets

Category	Packet name	Function	Type
Mandatory packet	FixOpPos	Deletes obsolete object protection position to prevent the overwriting of other values
Mandatory packet	ChangeColumnLengthForDT810and812	Adjusts different lengths of the corresponding columns in DTs 810 and 812.
Mandatory packet	SaveNotesIsNotPossibleInModuleDokumente	Makes changes to the DI001092 and DI001093 columns, so that the ZERO values are accepted. See also the 13104 entry

Version DB 39.5.3

Features

• A new global usage_actual_load_reporting parameter was implemented that controls the creation of the working hours in the Reporting Hours Worked module.
• The message that is displayed when trying to create a status report for a planning object with Status=9 (Archive), has been changed to Status reports can only be created for planning objects with "active" status.
• Module variants have been added to the Resource Planning module.
• The Global Variables module has been removed from the Administration panel.

Bug fixes

• The problem, that different listboxes are assigned to the Person responsible for the task field in the Schedule and Task modules, has been fixed.
• The incorrect behavior of the Resource List dialog module, which enabled the insertion of new records, has been fixed.
• The problem, that the end date deviation in the Delta View module is calculated incorrectly, has been resolved.
• The problem, that no subproject dates are considered in the Costs by Cost Types/Month module, has been resolved.
• The problem that it is not possible to switch to the past week in the Work Reporting module if the respective resource has left in one of these weeks and the period is set to completed, has been resolved.

Version DB 39.5.2

Features

• The symbols of the Form, Horizontal layout, Vertical layout, Horizontal auto layout, Vertical auto layout and Define tab order menu items, have been updated.
• All objects (module, data table, etc.) of the old ERP interface have been deleted. From DB 39.5.2, only the Universal Interface (PLANTA link) is used.
• It is now also possible to access the english PLANTA documentation (Wiki) from a PLANTA system that has been set to english via F1 and F2.
• The procedure of the Database Schema Export has changed.
• In the Resource Planning module, the Insert All Resources module variant that shows all resources of the department to which the user has access, regardless of whether they are planned for projects or not, has been added. The display of the available and planned capacity below the scale on the department resource is now consistent with the sum of individual resources.
• The calendar button function in the Work Reporting module has been changed insofar as it can also be used for resources that have no period. DT418 Calendar is used instead of DT468 Period . As a result, the stored calendar in @G150 is accessed.
• In the Remaining Effort and Costs module, the IDs of all grouping objects are displayed.
• If you try to create a normal status report for a finished project (all tasks have actual ends) in the Status module, the query whether a final report is to be created is displayed. If the query is negated, the creation is not aborted but a normal status report (no final report) is created.
• By the use of color, non-working days can be visualized better in the respective modules (e.g. Work Reporting).

Bug fixes

• The problem, that only data of the current planning is displayed in the Milestone Trend variant of the Schedule module and no data from status reports, has been resolved.
• The problem, that different resources are displayed in the listbox in the Resource field and in the Resource Data Sheet module, while they should really be identical, has been fixed.
• The problem with creating individual Dynamic variables in the 1000 - 79999 number range, has been resolved.
• The problem, that the calculated delta values in the Delta View module do not refer to the selected status report, has been resolved.
• The problem, that the end date deviation in the Delta View module is calculated incorrectly, has been resolved.
• The problem, that all reports are available for comparison in the Delta View module, notwithstanding the fact that the Milestone Trend Analysis checkbox in the Configure Trend Analysis module is only activated for particular projects, has been resolved.
• The problem, that in the Resource Planning module only resources with existing remaining effort are offered for effort distribution, has been resolved.
• The problem, that a stakeholder with modification rights for a particular project cannot create links in table form in this project if the cost center structure code of this project does not correspond to that of the user, has been resolved.
• The problem, that the records in the Delta View module are displayed with actual load, has been resolved. If an activity (a todo item or a task) has both actual and remaining loads, it is displayed on a respective day in the Week Calendar module (due to the existing remaining load).

Migration Packets

Category	Packet name	Function	Type
Help packet	LogUnsupportedKoAGrCU	Finds all modules with the customer license that old budget data fields use. This is necessary in order to convert the customizing of all affected modules to the new cost type group model. For this purpose, see Customizing information
Mandatory packet	MigrateCostsAndBudget	Migrates all data of the old cost and budget model with 5 cost type groups to the new model with n cost type groups. Sets the p_project_budget_edit global parameter to 0
Mandatory packet	CleanupOldKoAGrFields	Cleans (deletes) all CU objects with old cost type groups (DTs, DIs, modules).
Mandatory packet	DropCounterHistoryTables	Cleans (deletes) data tables sDT348_HIS and DT396_HIS.
Mandatory packet	CreateSchemaTables	Makes adjustments to the new database schema Further adjustments, see DB 39.5.0.	Feature

Version DB 39.5.1

Features

• When assigning an existing project to a main project as a subproject, the query whether the functional ID of the project to be subordinated is to be changed is displayed. If the query is answered with Yes, the functional ID of the subproject is automatically adjusted to the functional ID of the main project.
• On the info symbol in the My Planning Objects module, an action that can be opened via the Focus new infos context menu command and that leads to the Info module, has been implemented.
• The option to filter by @32 in the Utilization with Cause module has been removed. This causes the utilization for all resources to be displayed in the Schedule module, regardless of whether the current user has access to the respective resources (which is controlled via the resource structure code) or not.

Bug fixes

• The problem, that not all risk and opportunity measures that are displayed in the Activities area in the Dashboard module are also highlighted when switching to the Risks/Opportunities module, has been resolved.
• The problem, that the value of the Remaining costs field is calculated incorrectly on task level, has been resolved.
• The problem, that particular fields are not filled or updated during automatic creation of status reports (e.g. Current status report, Last automaticly created status report), which leads to corruption of the data, has been resolved.
• The problem that the % deviation total planned costs field has a wrong format (previously: without decimal places, now: with decimal places), which lead to the ?% display for particular deviation values, has been resolved.

Version DB 39.5.0

Application

Features

• The new Program Management function and role (R60) has been implemented.
• General:
  • A new hours to be worked function has been implemented. For further information, see the Resources module.
  • The Send data to menu item under Extras has been extended by two new subitems: PDF Standard Export and Create PDF as an e-mail attachment.
  • The PPID parameter is no longer used from version 39.5.0 and has therefore been removed from the System Information module.
  • In the System Information module, the used database system is now displayed additionally.
  • The Mark with pen menu item has been renamed Pen.
  • The Shortcut name of the menu items has been standardized.
  • The Text marker and Reset changes menu items have been added.
  • The layout of the dialog message that is displayed when the password is changed, has been improved.
  • Dialog message 0251 Incorrect basic calendar has been renamed Incorrect or missing basic calendar.
  • The following text constants have been added:
    • Your password has been reset and replaced by the temporary password:{0}This password needs to be changed the next time you next log in.{1}
    • The password was sent to the e-mail address given.

• R70:
  • The functionality of the PLANTA portfolio has been
    • revised:
      • The rights to create, edit and delete portfolios has been changed.
      • The PortfolioMOD0099FV module for editing portfolio data has been replaced by the new PortfolioMOD009BPB module.
      • The budget planning has been changed according to the budget planning in PLANTA project (planning with n cost type group).
    • extended:
      • Portfolio Status Reports, Portfolio Status Report
      • The new Program planning object type can be assigned to portfolios.
  • In the Budget and Costs per Portfolio, Project and Year module, no currency is displayed in charts anymore.

• R41:
  • In the Project Core Data module, the name of listbox value 0 of the Status listbox has been changed from Standard to Template.
  • The data field size in the listboxes on Group 1, Group 2, Group 3 and Customer data fields in the Project Core Data module has been changed.
  • For some DIs in the Project Core Data, Idea Core Data, Proposal Core Data and Request modules, the Input only via listbox parameter has been activated.
  • The Budget module (MOD0099D6) has been replaced by the new Budget module (MOD009BOW). In the course of this, the following problem has been resolved:
    • Wrong effort summarization on main project level
  • In the Schedule module, the following changes have been made:
    • DI063096 Requirements has been added to the TaskMOD0099CA module (in window 1) and to the Schedule module (in window 9).
    • In the Schedule module, todo item notes and checklist items can be added to tasks.
    • Upon inserting resources in the Resource name field in the listbox in the Schedule, resources are now only displayed once if they are assigned to different roles/teams within the project.
    • The load has been removed from the Base module variant. In return, the module variant With load has been added.
    • When opening the print preview, zoom is set to 100 %.
    • For changes to project structures (e.g. detaching a part of a project from the structure), the value of the Level parameter is updated immediately after the respective change and the capacity scheduling does not have to be carried out.
    • The VN button has been erased from the Task Chain module.
  • The new Milestone Overview module has been added to the Project panel.
  • The Status module is kept under the new 009BQQ ID.
    • The new model was extended by the Risk/Opportunities area.
    • The Costs and Effort areas have been designed coherently to the new Budget module.
    • _End date_ and Mile stones areas have been merged to one Date area.
  • The total costs are displayed in a Gantt chart in the Status Report module.
  • In the Progress module, the Task is now linked so that the Task Core Data can be opened by one click.
  • The layout in the Model and Model Parameters module has been revised.
  • In the Dependencies module, a new data area has been inserted in which projects are displayed for the completion of which the current project is required.
  • In the Open Items module, the following changes have been made:
    • Open Items have been renamed Todo Items.
    • In the Todo Items and Progress modules, the Extras Filter criteria menu item has been activated.
    • New module variants have been added to the Todo Items module:
  • Upon copying a schedule, subprojects are now available as well.
  • In the Process Status module, the Master milestone and Summary task fields have been inserted, which gives you the opportunity to link the approval of milestones and tasks that follow the milestones to the approval step in the process status.
  • The grouping or filter areas of the following modules are fixed at the top:
    • My Watchlist
    • Projects
    • Project Estimate
    • Critical Projects
    • Projects: 2 Groupings
    • Risks And Opportunities
  • In the Resource Utilization by Code module, the grouping display by code has been integrated as well as a button via which you can display the child resources of a department resource.
  • The customizing of the Effort Reports module has been adjusted, and in this course, the error that causes the resource effort in the Effort per resource chart to be displayed incorrectly, has been resolved.

• R43:
  • In the Resource name listbox in the Resource Planning module, cost resources are not displayed anymore.
  • The absence editing procedure of the department employees by the department manager has been changed. For further information, click here.
  • In the ICA module, the calendar week scale has been deleted.
  • The resources in the Resource Requirements module are now grouped by type.

• R1:
  • Employees can edit tasks assigned to them. As a result, different fields of a task can be adjusted by the user, like e.g., % completed and Comment.
  • The black clock in the parent area of the Employee Board has been deleted.
  • An option for moving red and sent messages in the Info module to the paper bin in order to keep the Info module clear. Messages that have been moved to the paper bin can be viewed in the Paper Bin variant of the Info module.
  • In the Work Reporting and Week Calendar modules, the options to jump directly to a particular calendar week (input field and Go to CW button) and to jump directly to the current week (Today button), have been implemented.
  • In the Week Calendar module, no completed tasks are displayed anymore.
  • The module variants in the Work Reporting module have been changed. Forecasts of the remaining effort have been transferred from the With Forecast variant to the Base variant.

• Administration:
  • In the Persons module, the filter criteria on the up to field has been changed, so that persons for which the date in this field is in the future are displayed as well.
  • The cost type groups have completely been revised. It is now possible to create an arbitrary number of cost type groups for both costs and effort. The old Cost Type Groups module (0099DZ) has been replaced by the new Cost Type Groups module (009BQD).
  • Instead of listing all users when opening the Users module, users can now be displayed via the letter buttons representing the respective first letter of their last name.
  • In the Check Status Report Creation and Project Applications module, tooltips have been inserted on the links to the respective project tooltips (Open project XYZ).
  • In the Availability module, an option for filtering by week days has been implemented. For the procedure, see here.
  • The Technical Administration 01100119 PLANTA Standard role has been removed from all standard users and will be deleted completely in one of the next releases. If you want to continue to use this role, you have to update it.
  • Further listbox categories have been added to the Miscellaneous Listbox Values module.

• Miscellaneous:
  • The DF length of the DI006922 Help text: Code name and DI007802 Cost Center Name was increased to 80.
  • In the following modules, missing tool tips were added:
    • Skills
    • Task
    • Info
  • Due to the implementation of the new program management, the programs used up to DB 39.5.0 have been renamed systems. This affects the 814, 815, 816 data tables, the Programs and Allocate Costs to Programs modules, and the Cost Distribution to Programs data area in the Project Core Data module.
  • In the Carry out matching of I-texts for language "XY" in the "" data base? dialog message, a Cancel button has been added.
  • From the listbox in the Language field, all languages that are currently not supported, have been deleted.
  • Further values have been added to the Output type parameter in the Dialog Messages module.
  • In the My Watchlist module, a new data area for filter selection has been added.
  • The Expenses,KM, Actual Load <> 0 checkbox is now activated for Actual Load < 0 as well.
  • The DI008523 Status and DI001519 Date DIs have both been renamed Load date.
  • In the DI027601 Amount lines data field, only values from 0 to 9999 can be entered.
  • The display of the measure status has been changed from number to text.

Bug fixes

• General:
  • The indenting of the ? Data field description has been corrected.
  • The problem, that the System Information module can be opened several times in a row via CTRL + B, has been fixed.
  • The Scheduling saving error has been extended and now delivers more information on this problem.
  • The Python error message that occurred when sending an e-mail to a recipient without deposited e-mail address, has been fixed.
  • A spelling mistake in the English dialog message 0851 has been corrected.
  • The Change request function is now available for subprojects as well.
  • The problem, that for structured projects structure tasks are displayed in some modules, has been resolved.
  • The problem that caused the selected grouping criteria not to take effect (e.g. in the Projects: 2 Groupings module) has been resolved.
  • The problem, that when creating a new project the Rem. duration data field remains empty after capacity scheduling, has been resolved.

• R70:
  • The problems with updating the units (h or €) and the heading for the bubble value in the Objective Contribution All Groups and Objective Contribution by Groups modules that occurred after the filter was changed in the Portfolio Analysis, Scoring module which causes a change in the bubble value, has been resolved.
  • The problem, that the Cancel Approval per Budget Period module is displayed empty, has been resolved.

• R41:
  • Dashboard:
    • The problem, that the legend of the Status diagram in the Dashboard module is not updated correctly if milestones have been adjusted retrospective in the sequence, has been resolved.
    • The expected string for parameter 'string' but got 'NoneType' error message in the chart in the Dashboard module after copying the entire project structure, has been fixed.
    • The problem, that change requests in the Dashboard module are not displayed in the Activities section, has been resolved.
    • The problem, that cost values in the Dashboard and Costs by Cost Type Groups modules do not match, has been resolved.
    • The problem with the Python error message in the Dashboard module has been resolved.
    • The problem, that a traceback error message is displayed in the chart area of the Dashboard module, has been resolved. If the chart cannot be visualized because certain requirements are not met, a note is now displayed indicating that no chart data is available and giving the reason for this.
  • Budget:
    • The problem, that for structured projects the value of DI006926 of the main project is overwritten by the TR has been resolved from 39.5.0 insofar as the Budget module has completely been reconstructed and the values of individual projects and those of the entire structure are calculated and displayed separately.
    • The problem, that the KPI value in the Budget module is not updated after it has been changed in the Project Core Data module, has been resolved.
    • The problem, that for pure cost resources (resources with Resource type=8 ) both costs and effort are displayed in the Budget module, has been resolved.
    • Due to the implementation of the new data tables for costs and budget planning and respective recustomizing of the Budget module in DB 39.5.0, the problem with the inconsistency of summarized values does not occur in the new Budget module.
  • Schedule:
    • The problem, that in some cases Bar required dates and Bar calculated dates (traffic light) overlap in the Schedule module, has been resolved.
    • The error message that occurred in the Schedule module when opening the Link calendar listbox has been fixed.
    • The problem, that todo item descriptions in the Gantt chart of the Schedule module are not displayed if the todo item has been assigned to a resource, has been resolved.
    • The problem,that the resource structure code is not considered when resources are displayed in the resource listbox of the Schedule module and which causes all resources to be displayed regardless of the respective access rights of the current user, has been resolved.
    • When assigning resources, now all newly assigned resources are displayed directly in the Schedule.
    • If a German speaking user creates a task document in the Edit Task module, this task is now displayed for users who speak other languages as well.
    • The problem, that different resources are displayed in the listbox in the Resource name field and in the Resource list module while they should really be identical, has been fixed.
  • Subprojects:
    • The error message that occurred when trying to assign a new subproject with a status report to a main project that also has a status report has been fixed. Due to possible data corruption, you should not assign subprojects with status reports to main projects with status reports. For further information on subprojects, click here.
    • The problem, that a main project is able to assign itself as a subproject, has been fixed.
    • The problem, that in particular constellations (after detaching a subproject from the structure and subsequently changing the functional ID of the main project and then undoing it again) there are 2 projects with the same functional ID, has been resolved.
    • The problem, that the levels in a structured project are wrong upon subordination or detachment from the structure, has been resolved.
    • The problem, that after detaching a subproject from the project structure, the Schedule module is displayed empty in the detached subproject, has been resolved.
    • The problem, that only projects with actual start date are displayed in the Include Subproject Into the Structure module, has been fixed.
  • PLANTA project vs. Microsoft Project:
    • Problems with the tree structure in the PLANTA project vs. Microsoft Project module have been resolved.
    • The following problem in the MSP export/import functionality has been resolved: If several tasks are deleted in a PLANTA project project after exporting it to MSP and then reimporting it to PLANTA project, the deleted tasks are not displayed in F3 (Gantt chart window).
  • Status Report:
    • In the Status Report module, the Submit button has been renamed Approve button.
    • The Python error message that occurred after confirming the dialog message for creating a new status report in the StatusMOD009BQQ module has been fixed.
    • The problem, that in all status reports the Comment end dates field always contains the comments of the latest status report, has been resolved.
    • The problem, that the milestones of the main project are displayed in the milestone charts of a main project status report, has been resolved.
    • The Python error message that occurred upon creation of a baseline for a completed project has been fixed.
      • If a baseline is to be created for a project with actual end, the For this project an actual end already exists. Create baseline anyway? message is displayed now.
  • Progress:
    • The problem, that in the Work Reporting variant of the Progress module the actual effort and actual costs of the load level are summarized on one and the same project level, has been resolved. Now they are displayed in two separate columns.
    • The problem, that the todo items (foremerly open items) are displayed in the With todo items (formerly With open items) variant of the Progress module, has been resolved.
  • Production Costs:
    • The print settings (page break) in the Production Costs module have been corrected.
  • Info Board:
    • Problems in the charts in the Cost Trend/Effort Trend area in the Info Board module, have been resolved.
    • The problem, that in the milestone graphic in the Info Board module milestones with actual end are displayed as well, has been resolved.
  • Process Status:
    • The problem, that pressing F1 in the Send Info module leads to a Python error message, has been resolved.
    • The Python error message that occurred when clicking on the Send as info context menu command on the Submission or Approval process steps in the Process Status module has been fixed.
  • Check Reported Hours:
    • The problem, that no subprojects can be selected in the Check Reported Hours module, has been resolved.
    • The obsolete Person resource name and Person resource DIs have been removed from the Check Reported Hours module.
  • Stakeholder:
    • The Python error message that occurred when selecting a stakeholder in the Select Stakeholders module after closing the Stakeholder module has been fixed.

• R43:
  • The Python error message in the Resource Planning module has been fixed.
  • The problem, that negative values can be entered in the For distribution field of the Resource Planning module as well, has been resolved. If you enter a negative value now, the Only positive values can be entered message is displayed.
  • The problem, that effort values with decimal place that have been defined in the Schedule module, are rounded automatically in the Resource Planning module, which causes problems for the effort distribution, has been resolved. At the same time, the decimal number format has been preset for all effort DIs in DT466.
  • The problem, that incorrect data is displayed in the ICA module, has been resolved.
  • The performance problems in the Absence module have been resolved by making certain changes to the filter criteria.
  • The Python error in value range of DI040102 "grouping_472_text": computeOutput Python error message that occurred when deleting the filter in the Grouped by field in the Remaining Effort and Costs module has been fixed.
  • The customizing of the Resource Requirements module has been corrected, so that the problem, that for subproject project structures resources of the main projects are displayed as well, could be resolved.

• R1:
  • In the Overview of Reported Hours module, negative postings are displayed now as well.
  • The problem, that completed measures are displayed as delayed in the My Activities module, has been resolved.
  • The problem, that the opportunity measures that had the date in the future or had no date at all were not displayed in the My Activities module if no other factors existed in the Future and Without date groups, has been resolved.

• Administration:
  • The Python error message that occurred in the Planning Objects (in Table Form) module when right-clicking on a marked stakeholder and selecting the Display utilization or/and absence has been resolved.
  • The problem, that employees that have left the company (Left on field in the Resource Data Sheet filled) can still be displayed as resources in the resource listbox, e.g. in the Stakeholder module, has been resolved.
  • The tab order in the Resource Data Sheet module has been corrected.
  • In the Resource Data Sheet module in the DA040735, the DI058989 Unit 5: Name has been replaced by the DI058988 incarnation data item of the same name.
  • The Python error in value range of DI003414 "resource_type": processInput Python error message that occurred when deleting the values in the Resource Data Sheet has been fixed.

• Miscellaneous:
  • The problem, that the DI059759 summarized % utilization is not calculated correctly, has been resolved.
  • The Python error message that occurred when entering a special character in a data field with Python value range has been fixed.
  • The problem, that a user that is defined as a stakeholder with modification access to a subproject cannot view this subproject in the Edit Watchlist module, has been resolved.
  • The problem, that the Start period and End period fields (in the Resource Data Sheet and Resources modules) are not marked in dark blue upon saving changes to them, has been resolved.
  • When saving in the Object Filter module, the module is not closed anymore but the filter is used instead.
  • In the Request module, input fields are not displayed in gray anymore.
  • In the listbox on the Person responsible for task field, only person resources are displayed from now on.
  • The problem with the incorrect order in the Task successor field has been resolved.
  • The value range of DI008815 Budget total effort deviation has been corrected.

Customizing

Features

• When clicking on the Edit value range button in the Data Items module, a template is now copied to the opened editor for further editing, provided that the value range has previously been empty.
• The Customizer rights parameter controls whether the respective user is permitted to switch from user view to customizer view via CTRL + F3, F9 and via the links in the Data Field Information module.
  • The respective data item is contained in the Users module (Customizer field) by default. If the data item has already been assigned to the module individually during the update to Server 39.5.0, it is to be deleted from the module before updating to DB 39.5.0 so that it is not contained twice.
• In the License Level module, the PLANTA link and MSP Link add-ons have been included and PLANTA Content Management has been removed.
• The DI002089 Format and DI041598 Currency format DIs have been renamed Date format or Number/Currency format.
• In the Skins and License, System Parameters and DB Instances modules, the DI025686 Language has been moved to window 9 since this DI is currently without function.
• In the Skins module, the Highlight color field has been replaced by the Highlight color preview field of the same name.
• For the Text Constants module, the Multiline has been activated.
• In the Data Items module, the module variant with type has been added.
• In the Effects module, the Color preview field has been added to the Color ID data field.
• The layout of the Other Module Parameters module has been improved.
• In the Modules module, the Open Python macro editor [ALT + E] or Open macro editor [ALT + E] tool tips have been renamed Edit Python macro [ALT + E] or Edit macro [ALT + E].
• The NULL date behavior is no longer used.
• The value ranges of the DIs that calculate the threshold values have been converted to Python value ranges. For this purpose, the new check_limit() function has been implemented.
• In the Data Items module, the Open value range [ALT + E] tool tip has been renamed Edit value range [ALT + E].
• Several new commands have been added to the context menu of the Data Items module: Open VR DIs, Open constant, Open dialog message, Open SQL statement.
• Customizing in the Model and Model Parameters module has been revised.
• The way a customizing module is opened has been changed in so far as it is now possible to decide whether the customizing is loaded in the same panel or in a new one.
• On the Number of work areas field, a traffic light has been implemented, indicating whether the module has already been assigned to a work area (green) or has not yet been assigned (red).
• Under Global Settings, a new Python macro template has been stored (py_macro_module_template), which is only copied for newly created macro modules (modules of the class=6), as soon as macro editing is started. Note: for normal modules (class=4 modules) the old template (py_macro_template) is used.

Bug fixes

• In the Indirect Modules module, the following problems have been resolved:
  • The Python error message that occurred when clicking on a module number in the Indirect Modules module has been fixed.
  • The Python error message upon clicking on the link in the MOD field in the Indirect Modules module has been fixed. In the Modules module, the following problems have been resolved:
  • The Record could not be read message that occurred when opening the Python macro editing in the Modules module without prior input of the module number, has been changed to Please enter a module ID.
  • The Python error message that occurred when clicking on the LB: Copying values in the Modules module has been fixed.
• Various errors in the system customizing have been corrected, i.a.:
  • Errors in exits
  • Double Python DIs in a data table
  • Double DB position in a data table
  • DIs with value range type but without value range
• Wrong system customizing has been corrected.
• The following problems that occurred when creating an incarnation or a fetch exit have been resolved:
  • When selecting a data table, the real DIs are displayed in the respective listbox now.
  • The Column Type field is now filled.
• The problem, that the Incorrect or missing basic calendar message is displayed when a non existing calendar is entered in the System calendar field in the License, System, Parameters, and DB Instances module, has been resolved.
• The Python error message that occurred if no value has been stored for the smtp_server_adress parameter in the Global Settings has been fixed.
• OLEs are displayed in the corresponding modules again, if they have been viewed in the OLEs module before.
• The problem, that the Fetch DT displays incorrect values because its value range is incorrect, has been corrected.
• The Python error message when filtering via CTRL + Q in the PLANTA data table module, has been resolved.
• The prefixed numbers that have been used in some Python IDs, have been deleted.

Migration Packets

Category	Packet name	Function	Type
Mandatory packet	FixTablesWithoutPK	Adds the primary key in tables with missing primary key.
Mandatory packet	ReplaceSchemaObjects	Replaces schema objects of the DB 39.4.4.4 versions with Server from S 39.5.x with objects of the schema of DB 39.5.x.
Mandatory packet	AdjustPLANTALinkSchemaVoE	Adjusts PLANTA link schema of DB 39.4.4.4 versions with Server from S 39.5.x to the schema of DB 39.5.x.
Mandatory packet	ModifySchemaTables	Updates existing columns in the database for the update from DB 39.4.4.0 to DB 39.5.0
Mandatory packet	CreateSchemaTables	Makes adjustments to the new database schema Further adjustments, see DB 39.5.2.	Feature