Jump to: navigation, search

Web Services and Applications Release Notes

Release Date Release Type Restrictions AIX Linux Mac Solaris Windows
12/22/22 Hot Fix X

Helpful Links

What's New

This release includes only resolved issues.

Resolved Issues

This release contains the following resolved issues:

Workspace Web Edition

Inbound email no longer displays an empty email body content in Agent Desktop. Previously, in a scenario where, if an agent forwarded an inbound email from a customer to an external resource, and if the customer replied to that forwarded email, this reply received by the agent displayed an empty email body content. (HTCC-31840)

The attachment area for email interactions in Agent Desktop now contains a specific maximum height, beyond which, the attachment area will be scrollable if there are too many attachments. Previously, the attachment area automatically expanded if there were too many attachments. This reduced the size of the email body editor making it too small to work with. (HTCC-31838)

Agent no longer receives a warning message stating that a reply for the inbound email is already in progress, when replying to an inbound email, after having forwarded this inbound email to an external resource. (HTCC-31837)

Web Services API

Previously, when Cassandra performance logger was enabled, GWS wrote down the incorrect value of execution time. Now, it’s fixed and represents the actual time. (HTCC-31854)

Previously, while using the cache for ContactCenter settings, GWS might send multiple concurrent read requests to Cassandra for the same data evaluation. Such readings lead to unnecessary increased load on database. Now, GWS can be configured to use BlockingCache which prevents simultaneous data evaluation and concurrent read requests to Cassandra. To enable this new functionality, the following option should be set:

    enableBlockingStrategyForContactCenterSettingsCache: true


Previously, if BlockingCache for BusinessUnits was configured (enableBlockingStrategyForBusinessUnitsWithSubresourcesCache: true), GWS might get into a deadlock state while reading data from Cassandra for cache population. In this case, clients receive a "503 Service Unavailable" error for some API requests that obtain data from the cache which is not populated any more. This defect only affects agents with supervisor role and causes prolonged login time or inability for supervisors to view their agents' states on supervisor’s dashboard. Now, a possibility of a deadlock was remediated and the cache will be populated with next API request. (HTCC-31836)

Upgrade Notes

No special procedure is required to upgrade to release

This page was last edited on November 15, 2023, at 23:09.
Comments or questions about this documentation? Contact us for support!