PLANTA project 39.5.26

General

928

From now on, a new versioning scheme based on the principle of semantic versioning with three components will be used for PLANTA Project: Major.Minor.Patch. The current software version is 26.0.0.

The documentation is based on the corresponding major release. The version picker now exclusively contains the major version as well. Minor or patch level changes are continuously incorporated into the existing documentation and can be tracked in the release notes if necessary.

706

A new icon for the Delete menu item has been implemented.

961

Special characters are now permitted in the technical IDs of projects.

628

In the System Information module, exact date and time specifications for the Database parameter are displayed.

620

Links have been implemented in the module variants of the Risks/Opportunities module, which can be used to call up the corresponding risks or opportunities.

Project/Portfolio

657

975

Costs and revenues can now also be posted from the Task module using the corresponding command in the context menu.

For this purpose, two dialog modules have been implemented: Cost Posting and Revenue Posting. They are now also used when posting costs and revenues from the schedule.

Web only

392

Hyperlinks have been implemented in the planning object and process ID fields in the Non-Postable Objects area in the Time Recording module.

641

The generic tooltip on the traffic light indicating outdated status reports in the Status and Simulations portfolio modules has been converted into a specific one containing precise details of the newer report.

849

Direct dependencies can now also be created between two projects that already have a shared dependency on a third project.

796

815

832

806

Project insights ratings (visualized by a thumb icon) are now also displayed in the Status Report, Project Rating, and Dashboard (Portfolio) modules.

740

A button for copying a direct link (deep link) to the module of the same name has been implemented in the Portfolio Status Report module.

677

The Schedule module now displays an informative dialog message explaining how network cycles can be corrected by adjusting the relationships between activities.

1102

When the schedule is recalculated (e.g., when the main milestone is changed), the system automatically adopts the changed values, so no update is necessary.

Risk management

653

767

PLANTA now offers the option of generating risks, opportunities, and corresponding measures for a project using AI in the Risks/Opportunities (Project) module.

642

643

In the overview modules containing risk management data, links on the numbers in the rating and traffic light fields provide detailed lists of the risks and opportunities in the corresponding rating category.
For example, if you click on the number in the “Medium” rating field in the summary area of the Risks and Opportunities (Project Reporting) module, the List of Risks module opens, displaying all risks from all projects with a “Medium” rating.

639

700

In the Risks/Opportunities (Project) and Risks/Opportunities (Program) modules, new data fields have been added for assessing risks (without risk treatment and with risk treatment), opportunities, and monetary damage, and traffic lights have also been added.

805

The Risks and Opportunities (Project) and Risks and Opportunities (Program) report modules display risk data that arises during or after risk treatment by default.

617

804

When a resource is assigned to a risk or opportunity as Person responsible, the corresponding risks and/or opportunities are now displayed in the My Activities module for the respective resource.

793

Risk and opportunity charts in the Portfolio Info Board have been adapted to the new risk management system.

681

1047

The management of risk and opportunity measures is improved by extended status values and grayed-out display of implemented, completed, or rejected risk and opportunity measures.

802

The risk area in the Status (Portfolio) and Portfolio Status Report portfolio modules has been adapted to match the display in projects.

801

988

In the Status (Project) and Status (Program) modules, the display of damage and gross profit values in the Risks/Opportunities subarea has been optimized and traffic light fields for the display of risks and opportunities:have been implemented.

In addition, the corresponding data sheet modules can be opened via the links on risks and opportunities.

640

799

Tooltips have been implemented in all modules with risk/opportunity management:

• on the traffic light fields that show the number of risks/opportunities at the respective assessment level. The tooltips list all risks of the corresponding assessment level.

• on the evaluation fields to show the values the assessment is based on.

Except for traffic light fields that contain links and matrix chart fields.

1059

If no risk treatment has been performed for a risk yet, the fields “with risk treatment” are pre-filled with the values from fields “without risk treatment,” as these values are initially identical.

800

In the Risks/Opportunities (Portfolio) module, traffic light fields have been implemented to display the recorded risks and opportunities in the sum area, and the matrix display in the Qualitative Assessment area has been optimized.

1188

After updating to the current version, the new Damage extent and Probability of occurrence fields with risk treatment are automatically filled with values from the eponymous without risk treatment fields. The automatically set values apply until they are changed manually.

PM Administration

723

The Change Person ID module is now accessed via the Change person ID context menu command on the record of the desired person in the Persons module.

987

Performance for MS-SQL has been improved, and the CalculateDepartmentAbsence migration package runs automatically during updates from DB 26 onwards, eliminating the need for manual execution. This means that all absence data in the relevant modules is correct.

General

809

If resource requests are disabled, they are no longer displayed when switching between module variants in the My Department module.

556

If several employee boards are opened from the department board and then the Home button is pressed, the system now correctly returns to the department board.

691

If a locked project is accessed in the browser and via a link to time tracking, a correct message is now displayed to notify the user.

991

The ModuleNotFoundError: No module named 'imp' error message is no longer displayed when executing certain actions, e.g. MSP Import/Export.

727

Opening the Stakeholder Analysis module from the Other... module without customizer rights in the desktop client is now prevented. The module is only available to normal users in the Web Client.

1038

The cause of the Python error message when attempting to change the existing entry in the New ID field in the Change Person ID module has been fixed.

1094

In the Settings parameter of the Stakeholder Analysis, all traffic lights for the values positive (green), neutral (gray), and negative (red) are now displayed correctly.

Project/Portfolio

555

The display in the Absence module has been corrected. All days of a month are now displayed in one column.

775

No more Python error message is displayed now when clicking on the Favorites star for projects.

904

Deep links for programs work correctly now.

814

In the Program Core Data module, the tooltip on the Open program link button is now displayed correctly.

1061

Export of projects to Microsoft Project now works correctly.

1051

In the Task module, resources that have been assigned to a task as Person responsible can now add new task document records by clicking on the plus symbol next to the area heading.

695

An informative dialog message is now displayed in the Process Status module explaining why it is not possible to assign a predefined resource to a process step.

845

The dialog message stating that the Subprojects module is currently not supported in the web client is now displayed correctly again.

647

The cause of a Python error message when attempting to create a collection of status reports has been fixed.

1096

1050

In the Task module, buttons for inserting new records are only displayed in the areas for which the current user has the respective write rights.

1154

The cause of the Python error message when distributing the effort for a resource in the Resource Plan module has been fixed.

1116

626

The view in the Time Recording module (unfolded projects or task records) now remains unchanged after new hours worked have been saved, existing hours worked have been rectified, or presence times have been recorded or rectified in the Presence dialog module.

526

The assignment of planning objects to multiple portfolios now works correctly again.

859

The Assign Planning Objects module now only shows planning objects that are not yet included in the portfolio.

1048

Performance improvements in the Portfolio Budget module

1079

Access restriction to portfolios now works correctly according to the selected cost center.

Risk management

679

The risk and opportunity categories are now multilingual.

493

When opening risk measures from the Week Calendar module, no Python error message is displayed anymore.

PM Administration

881

The cause of an Oracle error during data import via LDAP has now been eliminated.