PLANTA project 39.5.21
Version 39.5.21 contains: Database 39.5.21, Server 39.5.34, Client 39.5.33
released on: 19/02/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 | ||
Almost all charts (with only a few exceptions) in the PLANTA project component, that have up to now been available as visifire charts have been changed to a new Synchfusion-Blazor component texhnology and can be adjusted via the PLANTA chart customizer. You can also create new charts using the PLANTA Chart Customizer. | ||
27002 27055 | Quick access from the user menu has been extended.
| |
| Time Recording | ||
| Project | ||
| 26159 | Resource requests/approvals are now available for subprojects as well. | |
27020 26885 | For the manual load profiles with time grid (PM_DAY, PM_WEEK, PM_MONTH, PM_QUART, PM_YEAR), the option of automated control of under-used or over-used effort per period was implemented by means of underposting correction and overposting correction. For further information, see here. | |
| 26941 | From the Task module you can now also have the utilization of the assigned resources in other projects displayed. | |
| 22305 | If you want to have the utilization of a resource who has left the company displayed, a respective message is displayed. The Show Utilization module is not opened for resources left. | |
| 26354 | An option has been implemented to set the missing actual end date for a project directly during the creation of a final report. For this purpose, a respective query has been implemented. | |
| 26788 | In the Evaluation criteria area of the Project Core Data, Proposal Core Data and Program Core Data modules, the weighted criterion contribution is now displayed additionally for each evaluation criterion. For this purpose, the corresponding column has been unhidden. | |
| 26942 | In the Risks/Opportunities modules of the projects and in the Risks/Opportunities modules of the programs, plus buttons which allow for the simple insertion of new risk or opportunity records have been implemented. | |
| 26791 | In the Resource Utilization by Skill and Resource Utilization by Code modules, the default period of the scale has been adapted to the period of the data. | |
| 27067 | For programs and ideas, images can now be stored in the respective core data modules. | |
| 24821 | In the Project Core Data and Program Core Data modules, the Schedule with gates checkbox is now activated automatically as soon as a main milestone is selected. If a main milestone is removed, the Schedule with gates checkbox remains activated. If changes are made, the time intervals on the gates are now updated when refreshing the Schedule module or during scheduling. A client restart is no longer necessary. | |
| 27130 | The TAB order in the Resource Requests module has been corrected. | |
| 27129 | Filtering in the Resource Requests module has been optimized. | |
| 27109 | If project dates are simulated in the portfolio and projects are thus shortened or moved, the effort which is then outside the simulation period are no longer hidden but displayed in the months of the initial planning and must/can be distributed by the portfolio manager according to the new dates. | |
Bug Fixes
| Key | Description | From Server/Client |
|---|---|---|
| General | ||
| 27027 | The problem that in the employee board in the Absence of the Department module the absence and vacation values recorded by employees were not summarized to the parent resources (departments, subdepartments), has been resolved. | |
| Project | ||
| 27017 | The missing arrows in the Budget module, which serve to transfer the budget from the baseline column to the Budget(w/o SP) and Requested (w/o SP) columns, have now been added again. | |
| 27008 | The performance of the Projects module (multi-project board) has been improved. | |
| 26931 | The format for the display of the year and of the costs has been corrected in some chart tooltips. | |
| 27047 | The problem, that in the status module of the programs, the number of risks displayed in the module itself and the number of risks displayed in the chart did not match, has been resolved. | |
| 26928 | In the Benefits and Revenues area of the Budget module, negative benefit values are displayed now as well. | |
| 27075 | Projects which have no normal status reports but only status reports which were created for simulation purposes can now be deleted. | |
| 27077 | In the pie charts for costs and effort, cost type groups which do not contain values are no longer displayed. | |
| 27070 | The pie chart titles for risks/opportunities is now displayed correctly when languages are switched. | |
| 26640 | The performance of the Schedule module has been substantially improved. | |
| 27128 | If the Resource Requests module is opened from the schedule of a particular project, the Project field is now always set to "output". | |
| 27152 | The cause of the Python error message which was displayed in the Schedule module when attempting to read the task chain of a task via the eponymous context menu command, has been resolved. | |
| 27105 | In the Resource Requests module, a dialog message is now displayed when you try to generate resource requests without filling the Project field. | |
| 26846 | When using manual load profiles with time grid (PM_DAY, PM_WEEK, PM_MONTH, PM_QUART, PM_YEAR), negative costs no longer arise if more effort is posted than planned. | |
| 26983 | The critical path is now calculated and displayed correctly. | |
| Portfolio | ||
| 27025 | The problem that when simulating the projects in portfolios, effort values were sometimes no longer displayed in utilization diagrams has been resolved. | |
| PM Administration | ||
| 26382 | When creating new resources in the Resource Data Sheet, saving is now refused until all mandatory data fields are filled. | |
| 27004 | A Python error message when filtering for "day" in the filter criteria of the Calendar module has been eliminated. | |
| 26518 | The values for factors 3, 4, and 5 for resources without child resources per day (DT468) are now calculated correctly when refreshing after changes have been made. | |
| 26790 | The period of the calendar listboxes is now represented uniformly in all from/up to (left on) fields. | |
| 26997 | The error message in the Calendar module, which is displayed when holidays for Bavaria are imported while the special holiday for Augsburg is marked as a working day, has been resolved. In addition, you can now select whether the Day of Prayer and Repentance is to be marked as a public holiday or not. | |