8.5.203.03
Web Services and Applications Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Mac | Solaris | Windows |
|---|---|---|---|---|---|---|---|
| 07/07/23 | General | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
Workspace Web Edition
- [HTCC]
GWS 8.5 now supports Red Hat Enterprise Linux version 8 (RHEL 8). Compatibility with RHEL 7 is also maintained. (HTCC-31901)
Web Services API
CRM Gplus Adapters
Resolved Issues
This release contains the following resolved issues:
Workspace Web Edition
Web Services API
[API]
Previously, while enabling HTTP traffic logger for POST/PUT API requests, Agents were not able to sign in WWE, getting error message ‘please contact administrator’. This is now resolved and the HTTP traffic logger can be used for any kind of API requests.
[IX Proposed version]:
Agents are now able to log in to WWE when HTTP traffic logger is enabled for POST/PUT API requests. Previously, in this scenario, Agents received an error message 'please contact administrator’ when logging in to WWE. (HTCC-31959)
[API]
Added new options ‘Template:ChatServerConnectionTimeout' (default value 7000 in milliseconds), and 'Template:ChatServerReconnectTimeout’ (default value 10000 in milliseconds) to configure connection timeouts to Chat Server. Previously, these options were not customizable, and the value used for 'Template:ChatServerConnectionTimeout' was 5000 ms.
The 'Template:ChatServerConnectionTimeout' option controls the timeout, after which the connection attempt fails.
The 'Template:ChatServerReconnectTimeout' controls the delay between reconnect attempts.
To customize these options, add them to the ‘application.yaml’ file inside the ‘serverSettings’ section with the desired values:
Template:ChatServerConnectionTimeout: 7000
Template:ChatServerReconnectTimeout: 10000
[IX Proposed Version]:
The following options are newly introduced to configure connection timeouts to Chat Server. You can include them in the ‘application.yaml’ file in the ‘serverSettings’ section.
Template:ChatServerConnectionTimeout - specifies the timeout, after which the connection attempt fails.
Template:ChatServerReconnectTimeout - specifies the delay between reconnect attempts.
Example configuration:
Template:ChatServerConnectionTimeout: 7000
Template:ChatServerReconnectTimeout: 10000 (HTCC-31948)
[API, eServices]
Web Services and Applications now correctly works when the option ‘Template:EnableChatSynchronization' is set to ‘true’. Previously, enabling this option could cause an issue where the agents couldn’t see messages in chat sessions.
[API, eServices]
Added new options ‘Template:ChatServerRejoinAttempts’ (default value 5), and 'Template:ChatServerRejoinDelay’ (default value 10000 in milliseconds) to configure join attempts to chat sessions of the Chat Server. Previously, these options were not customizable.
The 'Template:ChatServerRejoinAttempts' controls the number of join attempts to a chat session.
The 'Template:ChatServerRejoinDelay' controls the delay between join attempts to a chat session.
Multiple join attempts might be needed after the ChatServer failover, on startup it needs time to restore chat sessions.
To customize these options, add them to the ‘application.yaml’ file inside the ‘serverSettings’ section with the desired values:
Template:ChatServerRejoinAttempts: 5
Template:ChatServerRejoinDelay: 10000
[IX Proposed version]:
When there is a ChatServer failover, multiple join attempts might be needed to restore the chat sessions. You can configure the number of join attempts and the delay between each attempt by using the following new options in the serverSettings section in the application.yaml file.
Template:ChatServerRejoinAttempts - specifies the number of join attempts to a chat session. By default, the value is set to 5.
Template:ChatServerRejoinDelay - specifies the delay in milliseconds between join attempts to a chat session. By default, the value is set to 10000 milliseconds.
Example configuration:
Template:ChatServerRejoinAttempts: 5
Template:ChatServerRejoinDelay: 10000 (HTCC-31942)
[API]
Previously, while establishing a session with Configuration Server, GWS SyncNode might not use all connections from the CloudCluster application if any network issue has occurred that led to unavailability of corresponding channels (voice, chat, etc). This issue is now resolved and all channels are available despite any possible network issue.
[IX Proposed version]:
While establishing a session with Configuration Server, GWS SyncNode now connects with all channels (voice, chat, and so on) configured in the CloudCluster application despite any possible network issue. Previously, GWS couldn’t connect with those channel(s) if they were unavailable due to a network issue. (HTCC-31923)
[API]
In some configurations with a large number of CorporateFavorites and LogHeader functionality enabled, GWS could send thousands of read requests to Cassandra at once that might impact Cassandra performance.
In such scenarios, to optimize performance, reading application setting for the LogHeader functionality can be disabled by using the following configuration option through the application.yaml file:
{quote}serverSetting: logHeaderSettings: excludeAppSettings: true{quote} (HTCC-31921)
CRM Gplus Adapters
Upgrade Notes
No special procedure is required to upgrade to release 8.5.203.03.