S 39.5.31

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.

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

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.

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.

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

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, see here.

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

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

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.

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.