8.5.107.06
Interaction Server Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 05/20/16 | General | X | X | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- Interaction Server prints out the current license usage upon any attempt to log an agent in or out, including any automatic logouts due to timeouts, license cut or client/proxy disconnect.
- The option log-custom-message-content, added to the log-control section, allows you to enable or disable (the default) printing of the binary content of EventCustom in the Interaction Server log.
- This release introduces agent auto-logout, which allows logging out agents due to inactivity. The new option login-session-timeout in the settings section specifies the inactivity timeout in minutes. If an agent application does not send any request to Interaction Server for the duration specified by the option, Interaction Server logs out and disconnects that agent.
- The option reset-states-on-shutdown, added to the settings section, controls the behavior of Interaction Server when it is shut down normally. Previously, as part of shutting down when working with DB Server, Interaction Server finished all database updates and reset all interaction states to queued. Now, if this option is set to false, the Server does not update interaction states, so the agents have a chance to use the session restoration feature after reconnecting to a backup server. Note that when working with ODBC, the option has no effect and interaction states are not reset on shutdown.
- Interaction Server supports Red Hat Enterprise Linux (RHEL) 7 64-bit native.
Resolved Issues
This release contains the following resolved issues:
When a request to the integrated Web Service Capture Point contains SOAP 1.2 namespaces, the Capture Point no longer attempts to upgrade the response to SOAP version 1.2. (ESR-11595)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.107.06.
This page was last edited on November 1, 2016, at 17:03.
Comments or questions about this documentation? Contact us for support!