S 39.5.30
03/03/2022
Caution
- For an update to server version 39.5.30, it is absolutely essential that you also update the databse to version DB 39.5.17.
- An update to these combinations is only possible from a Venus system 39.5.16 (DB 39.5.16 and S 39.5.29).
- If you want to update from an older system (Earth or Venus on Earth), you first have to update to Venus version 39.5.16 (DB 39.5.16 and S 39.5.29) and subsequently to S 39.5.30 and DB 39.5.17. For an update to Venus version 39.5.16, please refer to the instructions under Help for releases up to DB 39.5.16.
- If you have any questions, please contact your PLANTA consultant.
Features
| Key | Description |
|---|---|
| 25489 | |
| 25583 | Two new get_client_type and navigate_to ppms functions have been inserted. |
| 25407 | Python IDs of the data fields are now also forwarded to the client. |
| 25411 | New session type for webclient sessions have been implemented |
| 9920 | You can now write into the server/session log from Python |
| 25045 | Data events will now also be run when saving via web requests |
| 25344 | The schema of the EVENTS table has been updated (UpdateEventSchema) |
| 25306 | For access to end points in the PLANTA link /api/* namespace, the server now writes into an access Log (LinkWebService.log) in common log format. See also https://en.wikipedia.org/wiki/Common_Log_Format |
| 25418 | Olingo library has been included in server binaries to make ODATA services available in PLANTA weblink. See also https://olingo.apache.org/doc/odata4/download.html |
| 25413 | The client will now be informed by the server via the customizing rights of the logged on user, enabling the allocation of different functions for a customizer on the part of the client. |
25416 25415 | An option to use an own user menu for web clients has been implemented which may differ from the user menu for desktop clients. The AddWebUserMenuModuleToSkin migration packet adds the required data field to the Skin customizing module. In systems with DB status 39.5.17, the respective data field is contained in the Skin module by default. See also the 25414 entry on PLANTA customizer in Release Notes. |
| 25549 | Dynamic variables are updated for data fields of type c5 as well as for data fields of type c4. |
| 25512 | If a user module is open in the customizing changes of which changes are made to data fields in the same session (DT411), the changed status will now be displayed to the customizer immediately. (UpdateClientEvent migration packet) |
| 25050 | Arbitrary message boxes can be displayed directly from Python. For this purpose, new methods have been implemented:
|
| 24982 | The Java version used by PLANTA has been updated to Java 11. |
| 24619 | The new ppms.get_auto_id Python function has been implemented which draws the next auto number of a DI |
| 25262 | New on_web_load(Variable dictionary) Python function added to Python events |
| 24983 | CPython has been updated to version 3.8.5 |
| 14511 | If a Python module possesses an invalid class name, a warning will be displayed and a fallback to the ppms.module_subclasses.base_class.Base standard Python class takes place. |
| 25753 | Performance improvement in server-client communication when several messages are quickly sent consecutively, since the server busy messages are now only sent if absolutely necessary. |
| 25739 | Logback-lib updated to version 1.2.10 due to logback vulnerability https://jira.qos.ch/browse/LOGBACK-1591 |
| 19349 | Now login/logout of the user are protocoled as well as informationen on the client used for login. |
| 25809 | New WebHqlQueryHandler.getSessionUser(Long threadId) and WebHqlQueryHandler.getSessionInfo(Long threadId) functions have been implemented in the Java Server API. |
Bug Fixes
| Key | Description |
|---|---|
| 24967 | The cause of the error message which occurred in System Information when a 0 for unlicensed add ons occurred in the license file, has been eliminated. |
24997 25166 | Missing primary keys for the EVENTS table have been added retroactively (AddPrimaryKeyConstraintToEventsTable migration packet) and EVENTHISTORY table (RecreateEventHistoryServer migration packet) |
| 25011 | Time-controlled events correctly write their results into EVENTHISTORY |
| 25101 | In HQL statements, the UUIDs will now be formatted internally so that the respective records can now be found with/without "-" and in upper or lower case. HQL statements hence function with these formats (both in MSSQL as well as in Oracle): b357c69d3336e14f9d09788aa5fc9fca B357C69D3336E14F9D09788AA5FC9FCA b357c69d-3336-e14f-9d09-788aa5fc9fca B357C69D-3336-E14F-9D09-788AA5FC9FCA |
| 25171 | The cause of the event error message which was displayed when deleting the resource in the Resource Data Sheet module has been eliminated. |
| 25384 | The problem with different date default values, independent of whether the respective data field was contained in the data area or not, has been resolved for Oracle systems. |
| 25537 | An error which could cause a Python traceback to be assigned to the wrong data item has been resolved. |
| 25610 | An error in the execution of ICOU under Oracle with utf8 has been resolved (UpdateClobHashFunction migration packet). |
| 25261 | An error in the PortNewLicenseVisualization migration packet in the update of earlier database versions has been fixed. |
| 22808 | When changing the title of a panel, special characters (like umlauts, etc.) are now converted correctly. |
| 25551 | Python names are read-out correctly, independent of whether they contain lower case or upper case letters. |
| 25744 | Incorrect calculation of the calculated end date of a task which contains assignments by several resources with CAP load profile if at least one resource is changed to PM profile. It is possible to deactivate this scheduling fix if necessary. To do so, add PM_AND_CAP_CURVES_IN_ONE_TASK_CORRECTED to DISABLE_SCHED_FIXES the planta_server.conf. |
| 25093 | Events will no longer be deactivated in the case of errors. Migration packet PortEventErrorMessages |
| 25123 | Cause of the "Connection timed out” error message which occurred when many saving processes were effected in a short period of time has been eliminated. |