Version DB 39.5.2

• 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