This ReadMe does not cover Universal Contact Server (UCS), UCS Proxy, and UCS Manager. These components are included on the Interaction Management CD and also on a separate Universal Contact Server CD, which has its own ReadMe.

New in Interaction Management 8.5.x Releases

[+] New in Release 8.5.3

The following new features were added in the 8.5.3 release:

8.5.306

Interaction Server now includes the following enhancements:
- All Java-related functionality is placed in the ixn-java-aux.jar library.
- Sensitive options of any Groovy Event Logger can now be stored in a safe way.
- Kafka Groovy Event Logger shipped as part of the Interaction Server IP can now stream reporting events in Genesys binary format.
- Kafka Groovy Event Logger script options are now consistent with Kafka Capture Point options.
- ElasticSearch Java libraries of version 6.8.3 are now used by ElasticSearch Groovy Event Logger.
- Support for Microsoft SQL Server 2019. See the Supported Operating Environment: eServices page for more detailed information and a list of all supported databases.

8.5.305

Integrated Capture Points now support the Apache Kafka messaging system.

8.5.304

Interaction Server now includes the following health monitoring-related enhancements:
- A new endpoint "/health/all/" on the Interaction Server health port
- New health counters for Interaction Queue Views
- New health counters for strategies loaded in routers
- Support of Prometheus format
Interaction Server now offers support for the following databases. See the Supported Operating Environment: eServices page for more detailed information and a list of all supported databases.
- Oracle 18c
- Oracle 18c RAC TAF
Interaction Server and Interaction Server Proxy now offer support for the following operating systems. See the Supported Operating Environment: eServices page for more detailed information and a list of all supported operating systems.
- Windows Server 2019 Hyper-V
- Windows Server 2019

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.txt file in the groovy_event_logger subfolder in the Interaction Server installation folder.

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.

[+] New in Release 8.5.2

[+] New in Release 8.5.1

The following new features were added in the 8.5.1 release:

8.5.110

Interaction Server can now generate an event that can enable tracking of abandoned interactions.
Interaction Server no longer supports the T-Server application type.
It is now possible to use the Groovy Event Logger to process reporting events using custom Groovy scripts.
Interaction Server comes with a new configuration option, max-userdata-size, to specify the maximum user data size for any specific interaction.
Various logging improvements have been added, including new logging control options (trace-segmented-views and max-segments-traced-number) and updated default values for Interaction Server and Interaction Server Proxy.
Interaction Server and Interaction Server Proxy now support TLS 1.2.

8.5.109

This release introduces Cluster Manager Plug-in for GAX, a user interface that you can use to configure Interaction Server and Interaction Server Proxy clusters.
This release supports Universal Contact Server v9.0 in N+1 mode.

8.5.108

Interaction Server 8.5.108.05 supports MS SQL Server 2014, MS SQL Server 2014 Cluster, and Java version 1.8 update.

8.5.107

Interaction Server 8.5.107.06 can be configured in a cluster when working with Interaction Server Proxy 8.5.107.14. This enables multiple Interaction Servers to manage the same agents in a single tenant.
Interaction Server 8.5.107.06 and Interaction Server Proxy 8.5.107.14 support Red Hat Enterprise Linux (RHEL) 7 64-bit native.
Starting in release 8.5.107.14, Interaction Server Proxy supports connections from client types like Media Server (such as Chat Server) and Routing Engine (such as Orchestration Server). It also supports connections using the ESP protocol and can process those requests.
Agents can be automatically logged out.

8.5.102

For RequestGetWorkbinContent, you can now specify:
- Filtering condition
- Number of records returned
- Order in which records are returned.
PostgreSQL databases are supported on Windows and Linux using an ODBC connection.

8.5.100

This release contains updated functionality that enables new features and enhancements of Orchestration Server (ORS).
Interaction Server and Interaction Server Proxy now support UTF-8 on Windows as well as on other platforms. On Windows, this support requires Interaction Server to connect to its database using ODBC (not DB Server).
The way that Interaction Server communicates with its database has been modified to optimize performance.
This release supports:
- Windows Server 2012 Hyper-V
- Oracle 12c RAC
- MS SQL 2012 Cluster
SCAN is not supported in this release.

[+] New in Release 8.5.0

Interaction Server

Interaction Server is part of the PureEngage Digital (eServices) platform. It controls interaction processing according to workflows as configured by Interaction Routing Designer.