Patch Release CX4.9.5
Release Name | CX4.9.5 |
|---|---|
Status | QA PASSED |
Release Date |
|
Release Summary | Introduces enhanced LinkedIn integration through webhook subscriptions and reinforces API security for Unified Admin through integration of Application Gateway. Also addresses high-priority bug fixes, including:
|
Upgrade Guide |
New in CX4.9.5
This is a patch release on top of CX4.9.4. This includes a few enhancements and critical fixes.
Enhancements
Feature | Description |
|---|---|
Supports real-time comments notification using LinkedIn webhook subscription. Use this guide to subscribe to the webhook. | |
Ensures the security of the Unified Admin APIs through integration of the Application Gateway with Identity and Access Management (IAM). |
Resolved Issues
Support Email transcripts | Issue: Email transcripts were not visible on reports because the Email message type was not handled in the transcript component. Resolution: Email message type support has been added in the transcript. Now the email transcripts are available in reports. |
|---|---|
Team dropdown in real-time dashboard | Issue: The Realtime Dashboard encountered errors while switching between different teams on the Teams dropdown. Resolution: Implemented safety checks to handle null-pointer scenarios, ensuring smoother transitions between team views. |
Disable the ‘Hide Comment’ action for LinkedIn messages | Issue: On the Agent Desk, comment-type messages displayed action buttons, including Like, Delete, View Full Post, and Hide Comment, upon hover. However, LinkedIn does not support the Hide Comment functionality. Displaying this option for LinkedIn messages led to potential confusion and the risk of triggering unsupported actions. Resolution: The Hide Comment button has been removed for LinkedIn messages. This eliminates the possibility of initiating invalid interactions. |
Restrict Sending Attachment to Valid LinkedIn Replies | Issue: For LinkedIn interactions on the Agent Desk, the message composer was intentionally disabled to prevent agents from replying directly to customer comments, since such replies are unsupported on the LinkedIn platform. However, the attachment button within the disabled composer remained active, allowing agents to attempt sending attachments outside the context of a valid reply. These actions were not handled correctly, leading to inconsistent behavior. Resolution: This issue has been resolved. For LinkedIn messages, the attachment button now remains disabled by default and is only enabled when an agent clicks the ‘Reply to Comment’ action while hovering over a comment. This ensures that attachments are only sent as part of a platform-supported response flow. |