Revision as of 12:13, May 11, 2020 by Mgionet (talk | contribs) (RN Automation.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

8.5.311.06

Chat Server Release Notes

Release Date Release Type Restrictions AIX Linux Solaris Windows
05/15/20 Update X X


Helpful Links

Releases Info


Product Documentation

eServices

Genesys Products

List of Release Notes

What's New

This release contains the following new features and enhancements:

  • For a deployment with multiple GMS clusters, which is needed for multi-data center operations, Chat Server now selects a GMS node from another cluster if the cluster that was registered initially, is empty (in other words, all GMS nodes in this cluster are down). (CHAT-3684)
  • Chat Server web health metrics have been extended to include additional information about the application. (CHAT-3683)
  • New health metrics mem_sessions_launched and mem_sessions_disposed have been introduced. These metrics are intended to report how many chat sessions Chat Server keeps in its memory. (CHAT-3673)
  • Chat Server now correctly sets "idle alert timeout" after a session restoration, taking in account the idle waiting time before the restoration. Previously, Chat Server was resetting "idle alert timeout" completely after a session restoration. (CHAT-3597)



Resolved Issues

This release contains the following resolved issues:


Chat Server now sends a different "party left" reason code when a customer is removed from the chat session by the flex-no-agents-timeout configuration option. Bot Gateway Server uses it to correctly stop a bot session when StopBotOnCustomerLeft is set to true during the bot startup. (CHAT-3694)


Chat Server now correctly applies Personally Identifiable Information (PII) configuration from UCS after a session is restored. Previously, for restored sessions, only the default hardcoded PII configuration was applied. (CHAT-3679)




Upgrade Notes

No special procedure is required to upgrade to release 8.5.311.06.

Comments or questions about this documentation? Contact us for support!