Known Issues and Recommendations
Interaction Server
The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Interaction Server. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
See also: Internationalization Issues
To allow ordering by the ReceivedAt and Id properties or by the received_at and id database fields, Interaction Server checks the order option of the Interaction View object and also checks the order attribute in requests that allow specification of order for selecting interactions, such as RequestTakeSnapshot, RequestFindInteractions and RequestGetWorkbinContent. If one of the mentioned properties or fields are present, the server does not automatically add those properties or fields in the default order. However, in this release the check is case sensitive, so names of properties and fields name must be entered exactly (for example, it must be ReceivedAt, not Received_At or receivedAt). If the case is wrong, it will most likely lead to a database error similar to the following: "A column has been specified more than once in the order by list. Columns in the order by list must be unique."
| ID: ESR-9358 | Found In: 8.5.101.00 | Fixed In: 8.5.102.00 |
The Web Service Capture Point does not work on Linux hosts when the number of open client connections is close to or exceeding 1024. On other platforms the limit is set by the OS-level limit of open files for the user (see, for example, the UNIX command "ulimit").
As a workaround, use Interaction Server Proxy as a middleman between Interaction Server and Agent desktop applications.
| ID: ESR-8382 | Found In: 8.5.000.10 | Fixed In: 8.5.100.18 |
When a client sends RequestStopProcessing to Interaction Server while the Interaction Server database is unavailable, Interaction Server does not send a request to delete this interaction from the database after the database becomes available again. At the same time in this situation Interaction Server sends EventAck to the client.
| ID: ESR-8208 | Found In: 8.5.000.10 | Fixed In: |
If DB Server disconnects just when a database transaction is about to start, there is the rare possibility that this particular interaction may became unreachable for further requests.
| ID: ESR-8185 | Found In: 8.5.000.05 | Fixed In: 8.5.100.18 |
Internationalization Issues
Information in this section is included for international customers.
There are no internationalization issues for this product.