PLANTA link 39.5.23

05 Feb 2025

Version 39.5.23 contains: Database 39.5.23, Server 39.5.37, Client 39.5.34

released on: 02/05/2025

Below you will find a list of release notes for PLANTA link functions. For release notes for user and and customizing functions, please refer to the PLANTA project/portfolio and PLANTA customizer 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.
Under Container Releases in the Technology/Installation help area, you get a general overview of the PLANTA project releases. Here you find links to the corresponding Release Notes as well as information on installation and update of the software with the required release.

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
26406	The new Read module data web interface with the GET implementation `ModuleReaderImplementation` for reading the module data via the web and storing the data in a JSON file has been implemented.
27285	Web interfaces have a new Hostname attribute to set an explicit hostname for this interface. If the attribute is empty, the host name is used by the global setting Host name for web interfaces, if this is set. A host name can be configured for different groups of web interfaces via the environment variables: `planta__server__hostname__pulse` `planta__server__hostname__jira` `planta__server__hostname__adaptive_card` `planta__server__hostname__odata`
27727	From DB 39.5.23, individual mapping functions for PLANTA link must be added explicitly in module 009CXZ Manage Mapping Functions before they can be used. The class name and the module path must be specified during configuration. When updating to DB 39.5.23, this is done automatically for existing functions. The new configuration allows you to define the functions at any position. We recommend creating files in the customer Python folder instead of using the wrappers. Migration packet: `MigrateInterfaceFunctions`
27706	A new endpoint for querying the loads with an extended filter (extended query parameter) `POST /pulse/timeTracking/1.0/workloadSearch` has been implemented and replaces the user-defined endpoint `GET /pulse/timeTracking/1.0/users/{userID}/workloads`. The latter will be deactivated from DB 39.5.25.
27400	The following endpoints now return the remaining effort of the respective resource: `GET /pulse/timeTracking/1.0/users/{userID}/bookingFavorite` `GET /pulse/timeTracking/1.0/users/{userID}/postingObjects` `GET /pulse/timeTracking/1.0/users/{userID}/workloads`
27705	"Pulse: workload - POST" ("pulse/timeTracking/1.0/workloads") and "Pulse: workload - PUT/DELETE" ("/pulse/timeTracking/1.0/workloads/{workloadID}") have an optional attribute "cardID", which is stored in DI 066832 pulse: cardID.

Bug Fixes

Key	Description	From Server/Client
27285	If a port is stored in the host name, no extra port is inserted in the address if the global setting Include port in web interface URL is set to 1.
27917	The pulse synchronization is no longer carried out twice now.