New in 8.5.3

{{{{{TMPL8}}} |Release=8.5.3 |Draft=

8.5.301

• This release improves logging and reporting capabilities for Interaction Server and Interaction Server Proxy. In particular, Interaction Server Proxy now chooses to forward the message RequestDistributeEvent to Interaction Servers that serve the media type and tenant ID specified in the request attributes. Previously, the Proxy chose an arbitrary Interaction Server by using a round-robin algorithm.

• This release includes enhanced Groovy Logger samples. You might need to re-evaluate your solutions based on samples from previous releases. For more information, refer to the new Groovy Logger configuration templates and the README.text file in the groovy_event_logger subfolder in the Interaction Server installation folder.

|New=

8.5.300

Interaction Server

• Interaction Server clients of type RoutingEngine, such as Orchestration Server (ORS), can now use the attributes InQueues and OutQueues in the RequestPlaceInWorkbin to update respective destinations for the interaction. Previously, this feature was available only for Universal Routing Server (URS), which uses a different API.
• Starting from this release, customers must use an ODBC connection for Interaction Server instead of DB Server. See the Migrating to ODBC from DB Server page for more information.

Interaction Server Proxy

• You can now use configuration options to filter log data:
  1. Create a configuration option section named [log-filter-data].
  2. Add an option where:
     • key—Is a user data key.
     • value—Is one of the following:
       • copy—Write this data in log (default value).
       • hide—Mask this data in log.
       • skip—Do not write this data in log.
• A new configuration option, hint-media-unavailable, in the section [settings] that has the following values:
  • If true, Interaction Server Proxy sends notifications to the agent desktop to indicate when the last Interaction Server node that supports a particular media type is offline. Another notification is sent when support of the media type is restored after the affected Interaction Server node is connected again and the agent desktops are silently logged in.
  • If false, Interaction Server Proxy does not send the notifications described above.

}}