Version S 39.5.19

Server

Features

• PLANTA now also supports Java 1.8
• The use of the MSSQL 2014 version has now been approved (see System Requirements and Platforms).
• Improved performance through extended indexes in foreign keys.
• Performance improvement for enquiries with large result sets, e.g. for scheduling via the new hibernate.jdbc.fetch_size and hibernate.jdbc.batch_size parameters that define the number of lines to be transferred for reading or writing.
  • In server update/installation, default values are allocated for these parameters. They can be adjusted individually if necessary.
• The performance when running migration packets that change large amounts of data, has been improved.
• During installation (installer), an alternative directory for the migration packets can be specified.
• When reinstalling a system, no more not-null constraints are created for history tables in Oracle.
• In a database update, it is no longer the case that all data except that with a customer license is changed, but instead all data with 000 and 011 is replaced.
• When updating, constraints are first created without validating the data, in order to ensure a complete update. Errors that are detected in the subsequent validation are written in the logfile.
• Migration packets that are run before a database update are displayed in the Before DB Import area in the Migration packets panel. Migration packets that are run after a database update are displayed in the After DB Import area in the Migration packets panel.
• The creation of the MIGRATION user and the corresponding person before an update has been improved.
• The get_data_dictionary() Python function now also processes Python value ranges that only compile error-free within a user session or module construction.
• For improved identification, DEFAULT constraints in MSSQL now have a name that is readable instead of a name generated by the system.
• Preparation for configurability of the time fixed up to now from 5min up to disconnection of Server and Client when the user is inactive, in order to enable the specific configuration of the value in an ini file for future Client versions.
• Numerous improvements have been made to the PLANTA schema generation, e.g. respective names for constraints, generation of drop/create statements for indexes.
• Improvement of the logging during migration.
• Service functions now behave more performant if they are opened in a performance-critical loop.

Bug fixes

• The incorrect CreatePkUuids packet has been corrected.
• The problem, that the Client did not reconnect after a server crash if the PLANTA Server ran under Windows, has been resolved.
• The problem, that from S 39.5.16 relogin was no longer possible under Windows after using the Reload system customizing menu item, has been resolved.
• The crash in connection with the search_record() HQL function, which did not return a string due to a internal customizing error or due to the deletion of the computeSqlValueRange() function, has been resolved.
• The problem, that migration packets for the current release could not be restarted after the first run if they have previously failed, has been resolved.
• In the CreatePkUuids migration packet, UUID columns that already exist in the database are ignored and not interpreted as errors.
• The problem that made it impossible to reconnect to the server after some time has been resolved.
• The Damage to PRIMARY KEY restriction 'PID472DT472'. A double key cannot be inserted in the dbo.DT472 object. The double key value is (000079, -1638) error message, which occurred in the capacity scheduling of a project with subprojects if one subproject had a higher priority than the main project, has been resolved.
• The java.io.IOException: The system cannot find the specified path and The "setenv.bat" command is either spelled incorrectly or could not be found. error messages that could occur when installing the monitoring component under Windows have been resolved.
• The problem, that the server crashed when using HQL with commented out value ranges, has been resolved.
• A crash that sporadically occurred when the server logfile was activated under Windows has been resolved.
• The problem, that the session crashed when opening the Utilization by skills module while using MSSQL, has been resolved.
• The problem, that an update installation failed when using DB 39.4.4.0 under Windows if the installer was stored on another drive than the installed server, has been resolved.
• The problem, that the end date deviation in the Copy Schedule module is calculated incorrectly, has been resolved.

Migration Packets

Customizing Hotfix

Features

• The Check Database Consistency module has been improved and some errors have been resolved.
  • The new Check dash records and Check and write dash records options have been implemented.

Bug fixes

• The problem, that the FillMigrationruleTable migration packet was displayed twice due to an error in the CleanupPacketData migration packet, has been resolved.
• The problem, that the FixNotNullConstraints packet failed if tables were contained in the Data Dictionary that did not exist in the database, has been resolved.
• Database objects that cannot be changed, like e.g. (materialized) views, are skipped in the FixNotNullConstraints migration packet.
• The following migration packets have been adjusted:
  • DropCounterHistoryTables
  • DeactivateVariableObjectTables
  • ModifySchemaTables
  • ReplaceSchemaObjects
  • CreateSchemaTables (DB 39.5.0)
  • CreateSchemaTables (DB 39.5.2)
• The Python error message that occurred after opening Edit Python module subclass on the Python module subclass field in the Modules module if a non-existent path to a Python module subclass was specified, has been resolved.
• The Caused by: java.sql.SQLDataException: ORA-01841: (entire) year must be between -4713 and +9999 and must not be 0 error message, that occurred when entering hours in a system with two license records, has been resolved.
• The Python error message that occurred in the Modules module when clicking on the Edit Python macro button, has been fixed.
• The IE: auto commit behavior was changed when running ServerExecute_11DE45EC, reset is forced! error message that occurred after clicking on the Import from Microsoft Project button and subsequently selecting an XML file in the Microsoft Project module, has been resolved.
• The problem, that failed migration packets from the Server area were not displayed in the respective module among the failed packets but in the Irrelevant Packets module, has been resolved
• The problem, that changes of a data field configuration that were made in an external editor were not applied, has been resolved.
• The problem, that period records were not created correctly after deletion and recreation, has been resolved.
• The problem, that after deletion, recreation and repeated deletion of periods in the Resource Data Sheet module, the No period records found module was displayed, has been resolved.
• The problem, that an already checked configuration in the Configuration module of the PLANTA link was checked again after clicking on the Validate configuration button, has been resolved.

Migration Packets