10/10/2022

Caution

  • When updating to Server 39.5.31, the license.conf file must necessarily be replaced since the license check has been extended and now also checks the validity of the license. See entry 25970.

S 39.5.31.2 - Stable 2 (75200)

Bug Fixes

Key Description
26846When using PM_load profiles, negative costs no longer arise if more effort was posted than planned. 
26535A running Oracle DB session can now be quit without being rebuilt.
26983The critical path is now calculated and displayed correctly.
26366

It is now possible to filter when using skins with different date formats or date formats which deviate from those used in the PLANTA standard system.

In order to be able to use this function, you have to implement a global setting with the "standard_date_format" Python ID in which the required date format is specified. This format is then used to interpret data values in Filter from / Filter to (instead of the date format which is entered in the skin of the user). This has no impact on the display of date values on the interface which is still defined by the date format in the skin of a user.
CAUTION: This means that the filter data strings MUST be defined in this format system-wide. This rule applies both to filter data strings entered by the user when filtering in the Filter Criteria module and to filter data strings preset in the customizer. Please note that in PLANTA standard all filter date strings already preset in the customizing have the German format (000004).

See also the description under Known Issues.

S 39.5.31.1 - Stable 1 (73797)

Bug Fixes

KeyDescription
26307The PLANTA installer has been adjusted insofar as now a direct update to S 39.5.31 and DB 39.5.18 is possible again.

S 39.5.31.0 - Base

Features

Key Description
25907

The server part of PLANTA secure has been integrated in the Server. In this context, new server files have been integrated. secure.conf and ldap.conf

25970

Extension of the license check 

  • In license.conf, the new Valid from and Valid to parameters have been implemented. They serve to define the period of validity of the specified license. These entries are mandatory. If one of these entries misses, the license check fails and the server is started with a minimum demo license (which, e.g., only allows for the creation of 3 projects). You therefore necessarily have to exchange the license.conf file when you upadte to Sever 39.5.31. 
  • It is now possible to have different licenses for different objects per data table.
  • There is a new parameter named Deny message. Here you can enter the number of a specific dialog message which will be displayed when the creation of records is denied. If this parameter is left empty, a PLANTA default message (1314) will be displayed.
  • If the license check fails, a notification is displayed in the title bar of the program. In the case of an expired or not yet activated license, users with customizing rights also receive a respective dialog message upon program start.
26197

OS login is no longer supported by PLANTA. In order to ensure secure authentication, PLANTA offers Kerberos or PLANTA secure. If you have any questions, please contact your PLANTA consultant.

25891

In PLANTA secure, authentication via LDAP has now been integrated.

26099

The web interface authentication can now be configured individually​. New authentication options via API token in the URL have been added. For this purpose, the new Authentication field in the Web Interfaces module and the new Manage Tokens module are made available. For further information, please click here.

Required migration packets: ​AddWebToken, AddWeblinkAuthentication, AddTokenMapping, MigrateJiraWebinterfaceAuthentication, MigratePulseWebinterfaceAuthentication

PLANTA standard interfaces to PLANTA pulse and Jira are now authenticated via API token.

25675

An option for deleting records also via context menu has been implemented. For detailed information on deletion, please refer to the Introduction and Program Operation help section.

23013In the case of a conversion/database error of a DI, a more detailed error message will be displayed.
25973Every time the server is started, the generated pojos are deleted from the target directory and are newly generated. Via the new parameter in the globals.conf you can switch off deletion and new generation.
25974Internal changes to the client server protocol have been made: If it is a web client, the Python names of the data fields are always sent from server to client. If it is a desktop client, only the Python names of data fields which have at least one data field with "we" behavior  are sent from server to client.
25976New "al" data field behavior for changing from web client to desktop client has been implemented.
25428New delete-demo-data migration parameter for erasing demo data from the system during migration. For further information, see here.
25987slf4j logging api has been updated to version 1.7.36.
26154The Java version of the PLANTA Server has been updated.
26122New data table 245 Imported user attributes for connecting Active Directory has been implemented (AddUserAttributeTable migration packet).
26047

The outdated "pysapnwrfc" SAP library has been replaced by the new "pyrfc" library. In Server version 39.5.31, both libraries are valid. From Server 39.5.32, only the new library will be valid. In this context, the SAP interfaces in question must be adjusted. For further information on the integration of PLANTA project and SAP, see here.

Bug Fixes

KeyDescription
25726Jython message box now displays ASCII special characters (e.g. äöüß) correctly in the title bar and in the message text.
22739If a day for which planning has already been carried out (remaining loads) becomes a non-working day (due to vacation/sickness), the planned load will be deleted and planned for the next working day in the next calculation of the schedule. 
21220The schedule calculation with "Adhering to float" setting now works correctly. If there is float, it will be used if necessary.
26036If the migration server is started in migration mode, no license check takes place. Even if the license is incorrect, the connection will not be aborted.
25967The incorrect record counter in license check has been fixed.
25890An error in the default error treatment of the web interface has been fixed. Unhandled errors are now displayed in a defined format. Web interface implementations with public=False can now be used as implementation. The public attribute only controls whether this class is to be added to the listbox as a suggested value when the implementation is synchronized.