PLANTA link 39.5.20

Version 39.5.20 contains: Database 39.5.20, Server 39.5.33, Client 39.5.32

released on: 09/29/2023

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 Releases and Downloads 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
	New endpoints for web interfaces for Adaptive Cards have been implemented. `api/ac/refresh/{card_id}` `api/ac/action/{card_id}` See also Adaptive Card Customizer
26730	A new endpoint `/api/resource/{resource_uuid}/avatar` for the exchange of resource avatars with other applications, e.g. in Adaptive Cards has been implemented in the web interfaces. The respective interface is configured with an API token authentication and must remain at this setting in order for avatars to be displayed correctly in the Adaptive Cards.. Before using it for the first time, you have to create and link a token.
26582	The Data Maintenance module for viewing and possible deleting links by users from the AD and PLANTA has been implemented.
26573	Automatic synchronization based on “Pulse hybrid synchronization“ and “Jira hybrid synchronization” time-controlled events has been implemented. The corresponding interfaces are run automatically executed each minute if the project system is configured for the corresponding external system. For pulse, the user, project, task, and then resource assignment interfaces are executed automatically. For Jira, only the project and task interfaces are executed automatically. In the course of automation, the existing standard interfaces for pulse and standard interfaces for Jira have been revised. The former pulse/Jira interfaces which were used to synchronize the current context object have been set to Hidden but they still exist in the system.
26751	In the course of synchronization rebuild, the following changes have been made to the user synchronization. The 009D6T & 009CZ1 user synchronization modules now each contain a checkbox for marking users for synchronization. If a user is synchronized, the checkbox cannot be activated again. You first have to delete the linkage. Users left are no longer linked to the external system. Now, users are only created in/linked with external systems which contain a verified person. If the users are linked to an external system, the users that exist in the external system but could not be linked to project are no longer treated as incorrect, only the information is written to the logging (pulse & Jira). The 009D6T & 009CZ1 user synchronization modules now only show the users who would also be created in/linked with pulse/Jira. Users the e-mail address of whom is not unique are ignored by the user interface. In the PLANTA pulse and PLANTA Hybrid Parameters module, "Interface: Create New Users", "Interface: Link Existing Users" and "Interface: Refresh User Master Data" have been deleted and the new "Interface: User" has been moved from the User Synchronization (pulse) area to the Hybrid Interfaces (pulse) area. Headings and layout in the 009D6V & 009CYX (Synchronized Objects) modules have been adjusted and the button for the creation of an API token has been removed (you should use this button in user synchronization). The Jira interfaces which are currently not used by the standard have been hidden in the configuration. Logging: See 26762
26762	A new data table (DT599) has been implemented to log the communication between PLANTA project and external systems. The Hybrid Protocol module with the Hybrid Protocol Actions submodule which serve to check the synchronization of the projects and tasks with PLANTA pulse and Jira has been implemented. For checking the user synchronization with PLANTA pulse, you can also use the Hybrid Protocol Actions module which can be opened from the User Synchronization module via the Show protocol button. The logging of the user synchronization is still carried out with PLANTA link logging. Migration packet: `AddExternalProtocol`
26760	Hybrid interfaces are locked during transfer. This lock is automatically lifted after 5 minutes if no further record is transferred. This is necessary if, for example, the server was shut down while a transfer was still in progress.
26231	The new ppms.interface.BasePyRFCModule base module subclass for PLANTA link, which serves to establish a connection to SAP using the new pyrfc library, has been implemented.