PLANTA customizer 39.5.19
Version 39.5.19 contains: Database 39.5.19, Server 39.5.32, Client 39.5.31
released on: 05/09/2023
- Below, release notes on PLANTA project customizing functions are listed. For release notes for the user and interface functions, please refer to the PLANTA project/portfolio and PLANTA link help areas.
- The functions and bugfixes listed here are mainly contained in the database software component. Functions which stem from the server or client component are explicitly indicated in the column on the right-hand side.
- In the Technology, Installation, and Update help area you can get a comprehensive overview of the PLANTA project releases with links to the corresponding pages as well as software installation and update information for the release you use.
- Here you can find known and fixed issues.
Press CTRL+B in the program or select the ? → System Information menu item to learn which component versions you use.
Features
Key | Description | From Server/Client |
|---|---|---|
| 148 | The charts created with the new chart customizer are now also displayed in the new desktop client. | C 39.5.31 |
| 26360 | To ensure the correct functionality of the license check, some tables have been extended by indeces. | |
| 26338 | You can now also create risk charts using the chart customizer | |
| 26352 | When creating charts, the preview of all supported chart types is loaded via which you can select the required chart type. | |
| 26255 | For the chart data fields, DF behavior "ch" has been implemented. The behavior py is no longer supported for the chart data fields. | |
| 26342 | Python logging works with customer customizing if it is stored in a directory under /py/. | S 39.5.32 |
| 26407 | In DT412, a new column named Data item configuration has been implemented which is required for future tooltip modules on data items. | S 39.5.32 |
| 25936 | New data tables 450 Adaptive Card template and 451 Adaptive Card for the future Adaptive Cards function has been implemented. | |
| 26312 | The server.module and server.session server APIs are deprecated and will be removed in a future release. If one of the functions is opened from the modules, a warning is displayed in the log. The corresponding functions are contained in the utilities.module and utilities.session customizing API files. These APIs have been extended by the clientless function. | |
| 26463 | Data series objects of the chart customizer have been complemented by the Zero value behavior parameter which can be used to configure the way in which zero values are displayed. | |
| 470 | Dynamic strings are now possible in the Name and Text attributes in the data series of the chart customizer. | |
| 26462 | The Chart Customizer can be opened directly via the button right next to the chart data field. | |
| 26537 | A new data field behavior for customizing Adaptive Card data fields has been implemented. | |
26560 26447 | New Python API functions have been implemented: get_client_version, which returns the version number of the client and db_export_data, which can be used to start the export of a database. | S 39.5.32 |
In order for the ON_LOGON_PLANTA trigger to work correctly you have to execute the AddOnLogonTriggerNewVenus migration packet. | ||
| 25932 | It is now possible to open a session without GUI or web client in which modules can be run controlled via Jython. For further information, see under Java Server API. | |
| 25933 | An option for exchanging the return value between Jython open_module and CPython-Module. For this purpose, the new getReturnValueForModule and getReturnValueForModuleByClientlessId functions have been implemented. For further information, please see Java Server API. |
Bug Fixes
Key | Description | From Server/Client |
|---|---|---|
| 26281 | The usage check of the data items can now be started directly from the Data Items module via the context menu without any error message. | |
26304 26444 | In the Object Use module
| |
| 26350 | The cause of the error message which was displayed when an incorrect function path was specified in the Function name field during the creation of a Python event has been eliminated. | |
| 26414 | The limitation to 1000 conflicts per data table in the Conflict Management Procedure has been lifted. Now, all existing conflicts are handled. | |
| 26495 | The problem that charts were only deleted partially has been eliminated. | |
| 26522 | The incorrect DB positions of DI 066005 Resource request ID has been corrected (from 6000 to <6000) | |
| 26524 | ModuleWithRightCheck now inherits the authorization rules correctly on all subclasses. | |
| 26387 | Object protection is now set correctly in hybrid systems. Caution: If an action is carried out by an authorized user for another user (e.g. recording of hours worked), object protection will treat this action as if it had been carried out by the actual user. | |
| 26419 | The function of the PosRefresher which was implemented in DB 15 has been removed. An error which caused already existing ICOU rules not to be refreshed during update has been fixed. | |
| 26521 | During the to DB 39.5.19, conflicts on objects which were deleted are no longer indicated as "unresolved conflicts" in the overview module. |