The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.
TWiki> CurrentEN Web>ReleaseNotes>DatabaseReleaseNotes>ReleaseNotesDB3950

See also: Release Notes: Version Overview
Release Notes: all Database Versions
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.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.

  • 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:
    • 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:
    • 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.

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.

  • 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:
    • 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

         PLANTA project







 
  • Suche in Topic-Namen

  • Suche in Topic-Inhalten
This site is powered by the TWiki collaboration platform Powered by Perl