PLANTA customizer 39.5.18
Version 39.5.18 contains: Database 39.5.18, Server 39.5.31, Client 39.5.30
released on: 10/10/2022
- Below you will find a list of all features and bugfixes which concern the customizing functions and which are for the most part contained in the database component (customizing). Functions which come with server and client releases will be expressly designated as such.
- If you wish to get a complete overview of the new and corrected server and client functions, please switch to the release notes pages of the respective components. For links to these pages and information on the PLANTA software versioning as well as on installation and update, please refer to the Technology, Installation, and Update help section.
- Information on the versions of the components you use can be obtained from the system information which can be retrieved via the CTRL+B key combination or the ? menu item → System Information menu items.
- See also known and resolved issues.
Features
Key | Description | From Server/Client |
|---|---|---|
| 26013 | Deactivated data tables are now greyed out in the Data Table listbox in the Data Dictionary module. | |
| 25778 | The use of data items can now be viewed directly by clicking the links on the UF DF, UF DDI, UF UDI and UF traffic light fields. | |
| 25655 | The Chart Customizer was expanded with a new Label symbol attribute for data series. | |
| 25565 | Creating individual dynamic global variables, list variables and variables for manual search lists outside of the individual number range is now being prevented. If a user tries to create a customer individual variable outside of the individual number range, a message appears informing the user. When creating individual dynamic variables, the customer license is added automatically if it has not already been entered manually. | |
| 25901 | New data field behaviors we and ad were implemented for customizing Browser Control data fields and data fields for integrating the Adaptive Card Designer. Furthermore, the DF Behavior listbox now displays the values which can be used for the data item which is currently being edited. | |
| 25976 | The new data field behavior al for the button DI 004336 was implemented in the data base as preparation for the function of switching between web client and desktop client. The function will be added in a later Client release. | S 39.5.31 |
| 25940 | A new data table (DT450) for saving Adaptive Card templates was implemented (migration packet AddAdaptiveCardTable). | |
| 26005 | A check was implemented which blocks the use of regular expressions on non-alphanumerical fields when customizing filters. If a user tries to enter a filter with regular expressions on a non-alphanumerical field, a message is displayed to inform the user. | |
| 25048 | The cache behavior in Jython was improved:
| |
| 23013 | In case of a conversion / database error of a DI, a more detailed error message is displayed. | S 39.5.31 |
| 25428 | A new migration parameter delete-demo-data for deleting demo data from the system during migration was implemented. More information can be found here. | S 39.5.31 |
25991 | The migration packets | |
25427 | A new migration parameter change-license for changing the license during migration was implemented. More information can be found here. | |
26122 | The new data table 245 Imported User Attributes for integrating Active Directory was implemented (migration packet AddUserAttributeTable). | S 39.5.31 |
26045 | A new API for sending e-mails out of Python was implemented. |
Bugfixes
Key | Description | From Server/Client |
|---|---|---|
| 25726 | The Jython message box now also displays ASCII special characters (e.g. äöüß) correctly in the title and message text. | S 39.5.31 |
| 25885 | A runtime error in the MOD009DA6 Time-Controlled Events module which occurred when entering a start date which is too far in the past was fixed. | |
| 26042 | The FixProjectStructureTable migration packet fixes the issues with the AddUUIDtoProjectStructure migration packet, which prevented new projects from being created with DB 39.5.17. | |
| 25882 | The CreateR45 migration packet which creates the demo user R45 Web Management was set to optional, which means that the user ist not automatically created during an update. If the demo user is needed, the migration packet needs to be run manually. | |
| 26214 | When solving conflicts (with the new conflict management procedure), the new PLANTA value "0", "empty" or "-" is not being ignored and reset to the old value anymore. The new value "0", "empty" or "-" is accepted. |