8.5.202.99
Web Services and Applications Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Mac | Solaris | Windows |
|---|---|---|---|---|---|---|---|
| 12/16/22 | Hot Fix | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
Resolved Issues
This release contains the following resolved issues:
Workspace Web Edition
Inbound email is no longer displayed with an empty email body content in Agent Desktop. Previously, in some specific situation (inbound email forwarded by the agent to an external resource, customer replied to this forwarded email, and this forward reply was received by the agent), inbound email was displayed to the agent with an empty email body content while the email body was not empty. (HTCC-31840)
The attachment area for email interactions in Agent Desktop now comes with a maximum height, beyond which its contents start scrolling. Previously, the attachment area became too large when there was too many attachments, which made the email body editor too small to work with. (HTCC-31838)
Agent is no longer presented with 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 may 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 stay away from concurrent read requests from Cassandra. To enable this new functionality, the following option should be set:
serverSettings:
cachingSettings:
enableBlockingStrategyForContactCenterSettingsCache: true(HTCC-31853)
Previously, if BlockingCache for BusinessUnits was configured (enableBlockingStrategyForBusinessUnitsWithSubresourcesCache: true), GWS may got a deadlock while reading data from Cassandra for cache population. If it has happened (gotten an error for read operation), client for corresponding API Request that caused this data evaluation, will receive 403 error "Forbidden" and all other subsequent API requests - 503 "Service Unavailable", since cache turned into locked state and is never populated anymore. This defect only affects agents with supervisor role and causes prolonged login time or inability to see their agents' states on supervisor’s dashboard. Now, such possibility of deadlock was remediated and attempt for cache population will be done with next API Request. (HTCC-31836)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.202.99.