PCM v6.2.4.1 Release Notes
Ticket: L3REQ-70580
Resolved a backward compatibility issue with the SSP API following the upgrade to the latest SSP version. The Check Node Availability API is now functioning as expected.
Ticket: L3REQ-71950
Fixed an issue where multiple child directories were not displayed in the Mailbox UI during updates. Now, all specified child directories are correctly displayed under the parent mailbox.
Enhanced security by adding the following cipher suites when creating SFTP profiles:
The default JWT secret key has now been securely moved to the secrets file as part of Helm configuration changes, enhancing security and manageability.
Note: It is now mandatory to provide a value for the JWT secret in the secrets configuration, as the default value in yml file is no longer shipped with the build.
Improved the UI behavior for assigning partners, SSH keys, and Mailboxes. Previously, the search results would refresh and disappear after selecting an entry. The fix ensures that the search results in the Assign pop-up persist after selection for a smoother user experience.
Ticket: L3REQ-71939
Upgraded Spring Boot, Apache Tomcat, and various third-party libraries to their latest stable versions to address known security vulnerabilities. These updates enhance the overall security posture and platform stability.
Introduced validation logic to check if a username or mailbox is being used in other configurations before allowing deletion. If in use, a validation popup will prevent accidental deletion and notify the user accordingly.
The Virtual Root creation logic has been updated to automatically utilize the first path defined in the Pickup and Drop Mailbox configuration as the Virtual Root. This streamlines setup and ensures consistent path resolution.
Ticket: L3REQ-69732
Resolved an issue where PCM Partner details were improperly deleted from B2Bi when switching the partner type from Partner Connect to Hub Connect and back. The system now preserves correct partner configuration details across transitions.
Note: If the partner type is switched by mistake, users are advised to cancel the edit to avoid unintended changes. Re-editing the partner is recommended to ensure data integrity.