S 39.5.36

10/09/2024

S 39.5.36.3 -Stable 3 (27746)

Key	Description
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).

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

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

Key	Description
27362	New 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.
27163	If LDAP has not been configured, only the `ldap_enabled` parameter is returned with `false`.
27310	A user can be assigned a web client menu item role and a desktop menu item role at the same time.
27235	If the DB crypto is missing under ORACLE, the installer terminates without a long wait with a clear error message.
27245	New functions implemented to temporarily deactivate exits, both in Python and Jython. For further information, see here.
27355	New functions implemented which serve to deactivate events temporarily, both in Python and Jython. Python API Reference. For further information, see here.

Key	Description
27227	Requests to open a clientless session are now forwarded to a master session and executed there.
27295	Time-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.
27304	Changes made to data are passed on to the native part with each data event.
27318	Before a module is executed from Jython (e.g. via an event), it is checked whether the started session has already loaded the user menu.
27319	The error message that was displayed when attempting to create an idea in the Web Client has been eliminated.
27390	The problem that the parameters `ssl.keystore.file, ssl.keystore.password, ssl.truststore.file, ssl.truststore.password` could not be set in `secure.conf` due to an incorrect adaptation of the naming scheme has been fixed.