10/09/2024

S 39.5.36.3 -Stable 3 (27746)

Bug Fixes

KeyDescription
27746

Customer properties (L<licence no.>_name) in HQL statements can be written in both lower and upper case (in hql.query, hql.search_record, hql.modify).

S 39.5.36.2 -Stable 2 (76320)

Bug Fixes

KeyDescription
27726An error that a longer running system got full CPU utilisation and that no new clientless sessions were opened has been fixed.

S 39.5.36.1 -Stable 1 (76215)

Bug Fixes

KeyDescription
27634Customer-specific attributes can now be spelled with upper/lower case as desired.


S 39.5.36.0 - Base

Features

KeyDescription
27362New session startup events that are executed every time a new session is started (after user login, as soon as user menu is loaded & Python code is executable). For further information, see here.
27163If LDAP has not been configured, only the ldap_enabled parameter is returned with false.  
27310A user can be assigned a web client menu item role and a desktop menu item role at the same time. 
27235If the DB crypto is missing under ORACLE, the installer terminates without a long wait with a clear error message.
27245New functions implemented to temporarily deactivate exits, both in Python and Jython.
27355New functions implemented which serve to deactivate events temporarily, both in Python and Jython.

Bug Fixes

KeyDescription
27227Requests to open a clientless session are now forwarded to a master session and executed there.
27295Time-limited events in the “Running” status (i.e. which were executed when the server was shut down) are now executed again when the server is restarted.
27304Changes made to data are passed on to the native part with each data event. 
27318Before a module is executed from Jython (e.g. via an event), it is checked whether the started session has already loaded the user menu.
27319The error message that was displayed when attempting to create an idea in the Web Client has been eliminated.
27390The problem that the ssl.keystore.file, ssl.keystore.password, ssl.truststore.file, ssl.truststore.password parameters could not be set in secure.conf due to an incorrect adaptation of the naming scheme has been fixed.