Patch Release CX4.9.2
Release Name | CX4.9.2 |
|---|---|
Status | QA PASSED |
Release Date |
|
Release Summary | Includes CXAPI security via user authentication, License Consumption status tracking, enhancements to the pause/resume conversation feature, and new functionalities in CX Campaigns. |
Upgrade Guide |
New in CX4.9.2
This is a patch release on top of CX4.9.1. This includes a few enhancements and critical fixes.
Enhancements
Feature | Description |
|---|---|
CX APIs security via User Authentication | CX APIs are now secured/authenticated at the ingress level using an Auth Plugin (APISIX) and integrated with Keycloak for authentication and token validation. |
Allows business administrators to view license details, monitor expiry statuses, and receive proactive warnings for licenses linked to a master key. | |
When an agent places a conversation on hold, the agent will not receive browser or sound notifications for any new messages sent by the customer during that time. | |
CX Campaigns | Introduces the following few features in CX Campaigns:
|
Resolved Issues
Improvement in MS Exchange-based Email | Adds two improvements to the MS Exchange email-based connector to address general limitations caused by varying customer server certificates and exchange processing time delays. Resolution: Set a scheduled time for data pooling via EWS (Exchange Web Service), subtract one minute, and search within that window. This gives Exchange Server enough time to fetch new emails, process them, index them, and make them available in Search. Issue: When CX sends an attachment to an Email Exchange Client, it previously used the FQDN-based URL from the Agent Desk to download images and send them in the required format. This worked smoothly when Java had the client’s trusted certificates. However, in customer deployments, explicitly configuring Java for this process proves challenging. Resolution: This is fixed now by replacing the FQDN with the file-engine service name and downloading the image. |
|---|
🤬 Vulnerabilities Fix
Critical vulnerabilities identified in CX4.9 are fixed now. A complete vulnerability report is attached.