PLANTA project 39.5.20

Version 39.5.20 contains: Database 39.5.20, Server 39.5.33, Client 39.5.32

released on: 09/29/2024

Below, release notes on PLANTA project user functions are listed. For release notes on the customizing and interface functions, please refer to the PLANTA customizer and PLANTA link help areas.
The functions and bugfixes listed here are mainly contained in the database software component. Functions which stem from the server or client component are explicitly indicated in the column on the right-hand side.
In the Technology, Installation, and Update help area you can get a comprehensive overview of the PLANTA project releases with links to the corresponding pages as well as information on software installation and update referring to the release you use.
Known and fixed issues can be found here.

Press CTRL+B in the program or select the ? → System Information menu item to learn which component versions you use.

Features

Key	Description	From Server/Client
General
26647 26466 437	In PLANTA project, an option to use tooltip modules for dynamic display of contents has been implemented as an alternative to static tooltips. Tooltip Modules provide an option for having explanations or other information displayed depending on the values of a field. To learn how to create and embed tooltip modules, please refer to the customize tiooltips description in the PLANTA customizer help area. E.g. display of business cards on resource fields, display of project and proposal information on their respective name fields, in-depth explanations on dependencies of planning objects in the portfolio on the Dependency field, justifications for the activated Mandatory checkbox on planning objects in the portfolio etc.	C 39.5.32
9874	The menu item and the corresponding symbol for opening the PLANTA Online Help have been included in the print and page break preview.
26720	A shortcut CTRL+R for the *Calculate schedule* menu item has been implemented.
25947 26246	For the Send forecast function in time recording and Submission/approval of process steps in process models you can now use Adaptive Cards with a connection to Outlook in PLANTA standard. For this purpose, the Adaptive Cards function must be activated in Global Settings and all conditions which are necessary for the use of the function must be met. PLANTA now also provides the Adaptive Cards customizer via which you can also customize Adaptive Cards individually for additional functions.
549 646	The handling of editors on continuous text fields with markdown function has been optimized. User adjustments to the position and size of the editor window are now saved. When opening an editor, the cursor is now placed at the correct position.	C 39.5.32 C 39.5.32
420	All input fields of a record are now highlighted when hovering over any field of the record. The highlighting can be configured or deactivated in the Client Settings if necessary.	C 39.5.32
421	In modules with table views, the context menu can now also be opened via a button.	C 39.5.32
Project
26643	Business cards for resources have been implemented as tooltips. They are displayed in all modules with resource assignments on the Resource field. Via customizing you can define what content is displayed on the business cards. See also entry #26647	S 39.5.30
26638	The performance of the Projects module (multi-project board) has been improved.
26452	In the Task module, buttons for quick insertion of new records have been inserted in some areas. They can be used as an alternative to insertion via the context menu.
26897	The Jira area has been removed from the Task module since the synchronization function has been reorganized and can now either be triggered in the Schedule module or it runs automatically.
26438	In the Task module, the float or delay of the task is now indicated as well. Some changes have been made to the layout of this module.
26439	Archived projects which are older than 10 years and which are not assigned to any portfolio and do no contain any external links can now be deleted automatically. For this purpose, a dedicated time-controlled event is made available.
24149	You can only assign images to projects and proposals in the Project Core Data or Proposal Core Data accordingly. The images are displayed in a tooltip along with additional information on the respective project or proposal if the user hovers the mouse over the name of the planning object. When you create a project or proposal, an image is inserted which is defined as standard image in the Global Settings. Subsequently, the image can be replaced by an individual image in the Project or Proposal Core Data. During update, a PLANTA standard image is automatically stored in the system and assigned to all existing projects and proposals. After an update, the default image can be changed in the Global Settings.
547	When creating links graphically, the source record is highlighted now as well.	C 39.5.32
Portfolio
26687 26398 26400 26675 26401 26672 26465	The portfolio panel has been revised and extended. The Planning Objects module has been dissolved and the functions of the module have been implemented in the new Prioritization and Planning Object Status modules. Planning objects are now assigned to the portfolio in the Portfolio Core Data module. The new Prioritization module has been implemented as a replacement for the former Prioritization module variant of the Planning Objects module. Besides the display in table from, the new module also offers a graphical display of the planning objects by objective contribution and risk values, allowing for a faster categorization of the projects in terms of their priority. A new module named Planning Object Status has been implemented. The module provides an overview of all planning objects assigned to a portfolio. For each planning object, manager estimate, automatically calculated status of the current planning, and status from status reports are specified. A new module for the display of planning objects of a portfolio with Gantt view (Portfolio Gantt) has been implemented. In the Dashboard module, diagrams have been implemented to provide a better overview of the planning objects. The function of the Dependencies checkbox has been extended. Now it does not only show whether the selected project depends on other projects but also whether it is required for the completion of other projects.
26252	All charts of PLANTA portfolio which previously existed as visifire charts have been changed to a synchfusion blazor component technology and can be adjusted with the PLANTA Chart Customizer. You can also create new charts using the PLANTA Chart Customizer.
638	If an action is stored on a chart, this is signalized by a change of the cursor symbol.	C 39.5.32
26584	The performance of the creation of simulations in the portfolio has been improved.
25879	The layout of the Budget module has been improved.
26781	In the Group 1 and Group 2 filter listboxes in the Portfolio Info Board, the groups are displayed by area to facilitate the selection for the Objective Contribution by Groups analysis. Background: both groups for the afore mentioned analysis must stem from the same area since the evaluation of the planning objects in the core data modules is carried out separately for each area (see above) in which objective contribution criteria are grouped. Different areas can contain different groups.
26734	In the Budget and Costs per Portfolio, Planning Object, and Year module, the button for opening the display of possible dependencies of a planning object has been replaced by the Dependencies checkbox on which a tooltip module is implemented. This tooltip module immediately shows possibly existing dependencies.
26460	In the watchlist of the Portfolio Dashboard, estimates of the managers of the inserted planning objects as well as the calculated status of costs, effort, and dates are displayed (visualized by traffic light triangles).
26461	A traffic light has been implemented in the Status module in the area for assignment of status reports to planning objects which turns red when the most recent status report has not been assigned to a planning object.
26395	The functionality of the portfolio images has been revised and the Manage Portfolio Images and Select Portfolio Images modules have been removed. Portfolio images can now be uploaded, changed, and deleted in the Portfolio Core Data. When you create a Portfolios, an image is inserted which is defined as standard image in the Global Settings. Subsequently, the image can be replaced by an individual image in the Portfolio Core Data. During update, a PLANTA default image for portfolios is automatically stored in the system. If a default image already existed prior to the update, it will be overwritten during the update. After an update, the default image can be changed in the Global Settings. However, all portfolios retain the images which are assigned to them at the time at which the update is carried out.
PM Administration
26436	PLANTA now provides an option for nocturnal update by means of a time-controlled event. You can find the corresponding standard event in the Time-Controlled Events module.
24151	In the Resource Data Sheet module, an option has been implemented to store avatar images of the respective resource in the Avatar field which has been implemented for this purpose.
26488	The data of the persons left can now be anonymized/pseudonomized. For this purpose, a dedicated time-controlled event is made available.
26794	If the PLANTA groups are deleted for a person in the Active Directory because the person changes, e.g., to another department of the company and no longer works with PLANTA project, a Left on date is set for the respective person in PLANTA project after LDAP import. The Left on date is then automatically copied to all properties of the person (stakeholder, user, resource).
26775	Some rights parameters have been defined as Active Directory-leading for LDAP import. They cannot be changed after import. If you try to change such parameters for the persons imported from Active Directory, a message indicating this will be displayed.
26930	The risks and opportunities categories have been added to the Listbox Values administration module to offer an option to complete or edit the respective listbox values without having customizer rights.
Hybrid pulse/Jira
26573	Automatic synchronization for hybrid systems has been implemented. The synchronization is now run automatically immediately after you have saved the relevant changes, provided that all settings for the hybrid system have been set correctly. For pulse, the user, project, task, and then resource assignment interfaces are run automatically. For Jira, only the project and task interfaces are run automatically. In the course of automation, the default interfaces for pulse and Jira have been consolidated and partially changed. See also Release Notes for PLANTA link Automatic synchronization has been implemented based on the two new “Pulse hybrid synchronization“ and “Jira hybrid synchronization” events. The events are automatically activated as soon as the API URLs for the hybrid interface have been defined.
26703	The procedure for initial synchronization has been changed: By selecting an external system in the Project Core Data module, systems are now linked and the selected project is synchronized with the selected external system. Tasks are now initially synchronization in the Schedule module.
26772	In the Schedule module it is automatically saved as soon as you click on the pulse or Jira symbol or switch to the task data sheet (Task module). Conversely, as soon as you save in the Schedule module, the automatic synchronization of the data is triggered in the linked systems.
26334	In the Task module, a module variant has been implemented which exclusively displays pulse data. When clicking on the link on card specifications of synchronized tasks in the Schedule module, you directly switch to that module variant of the Task module.
26468	If a synchronized project is archived in PLANTA project, the corresponding project in PLANTA pulse is archived as well.
26428 26485	In task synchronization in hybrid systems with PLANTA pulse, the following data is now synchronized and automatically updated in pulse when changes are made in project. The calculated dates of the corresponding project (start and due date in PLANTA pulse) The WBS code of the tasks. The WBS code is displayed in the board header next to the name of the respective board.
26762	A new module for the logging of all synchronization requests has been implemented. The module can be found under Further...→ Miscellaneous → Hybrid Protocol. On this basis, an additional help function has been implemented for failed synchronization requests. If synchronization fails, this is now indicated in the Dashboard module by the symbol. By clicking on the symbol, the new Hybrid Protocol module is opened, in which you can view the cause of the failure.
26751	In the course of synchronization rebuild, an option has been implemented which allows you to define in a PLANTA project administration module which users are to be synchronized. For this purpose, a new module variant has been implemented in the Users module which contains two new checkboxes: Synchronize with PLANTA pulse and Synchronize with Jira Server. Only users for whom the checkbox is activated are created in the external system. For further changes which have been made to the user synchronization, please refer to the Release Notes for PLANTA link.
23626	If a user is created in PLANTA pulse in the course of user synchronization, he/she receives an invitation e-mail by PLANTA pulse in which he/she is asked to define a password. Users left are no longer created in PLANTA pulse.
Management Functions in the Web
26423 26809	The modules of the PLANTA portfolio role (demo user R70) can now also be accessed via the web client. However, some functions, such as PDF export, PPT, or direct links to the planning objects contained in the portfolio, are currently not yet available in the web client. If the user tries to execute this function, he/she is informed about this by a respective message and an option is offered to him/her to switch to the desktop client to use this function. If this query is answered with Yes, he/she is redirected to the corresponding position in the desktop client.

Bug Fixes

Key	Description	From Server/Client
General
26767	The error message regarding automatic numbers is no longer displayed when logging in to MSSQL systems.
565	The context menu is no longer displayed in listbox modules.	C 39.5.32
634	The markdown editor is now opened correctly when you click in a text field.	C 39.5.32
616	An error which occurred when filtering in dialog modules has now been corrected.	C 39.5.32
624	Continuous text fields with markdown function are now also displayed correctly in print preview.	C 39.5.32
746	An error which caused a system crash when the "Create PDF as e-mail attachment" function was used, has been fixed.	C 39.5.32
Project
26416	In the Status module, the incorrect display of the effort deviation and of the corresponding traffic light in the header of the Effort area have been corrected.
26718	In the Projects module, filtering via the Filter criteria menu item has been deactivated, since here you can already and should use the object filter for filtering.
26392	When archiving the projects, no intermediate module is displayed anymore.
26685	Display problems for comments in the Dependencies module due to the use of different comment data fields have been fixed.
26106	In the Milestones/Master Milestones module variant of the Schedule module, no more links are displayed.
26075	The cause of the Python error message in the SAP WBS module which occurred when attempting to assign tasks to empty SAP WBS elements has been eliminated.
26770	The Documents module is now available again in the Idea panel.
26766	Project creation directly after the update now works correctly again.
Portfolio
26585 26604	The performance in the creation of a simulation and when opening an existing simulation has been improved.
26792 625	The creation of PDF files from the Portfolio Status Report module is now possible again.	C 39.5.32
	The print preview in the Portfolios module has been improved.
26847	Overhead cost projects are taken into account in the Portfolio Dashboard.
PM Administration
26590	The option to manually change the code of a person in the Persons module is now disabled.. Person code (Person IDs) can only be changed in the Change Person ID module.
26605	The Calendar is active parameter has been removed from the Resource Data Sheet module since it is no longer used.
26774	If a user with a multi-project manager and a multi-portfolio manager role is imported into PLANTA via LDAP, he/she now receives the higher rights level of the two, i.e. multi-portfolio manager rights.
25917	Costs and revenues can no longer be posted to locked projects. The locked projects are no longer displayed in the project selection listbox in the Cost Posting and Revenue Posting module.
26778	The settings of the Load role startup module parameter are no longer overwritten during LDAP import.
26779	The problem, that in the case of a deleted resource for which the remainder of the data like person, user, etc. still existed, the resource data was not completed correctly after renewed LDAP import, has been resolved.
26587	The persons, the accounts of which are locked in the active directory or set to "left user” because they have already left the company, are not imported initially to PLANTA project. If they already exist in PLANTA project, a left on date is set for them during LDAP import.
Hybrid pulse/Jira
26153	If, in a hybrid system in PLANTA project, the project manager is changed to a person who is not synchronized with PLANTA pulse, synchronization is no longer started, but a message is issued immediately to indicate this. The project manager slection must then be corrected. To do so, you first have to reset the former project manager, save, and select the new one.