8.5.005.08
Genesys Mobile Services Release Notes
| Release Date | Release Type | Restrictions | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|---|---|
| 11/26/14 | General | Under Shipping Control | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
New in This Release
This release is under shipping control. This section describes new features that were introduced in this release of Genesys Mobile Services.
- Preview Callback – Agents can now preview the details of a Callback interaction before making the outbound call to the customer. Also, to support Preview Callback, URS Strategies were updated, and a new Interaction Workspace Plugin Sample is available.
- The Callback service now allows a virtual queue to be specified as a request parameter so that each service can support multiple virtual queues.
- Automatic mobile push notifications are now supported for non CometD-based (polling) chat sessions.
- The GMS Callback service has been enhanced to be more robust in failover recovery scenarios.
- The Callback Management UI has been redesigned.
- GMS now enables role-based access for the Service Management UI.
- The embedded web server has been upgraded to Jetty 8.1.14.v20131031.
Corrections and Modifications
This release also includes the following corrections or modifications:
The GMS Sample now correctly handles the modification of the user name. Previously, the CometD channel was not reinitialized upon user name modification and the GMS sample was no longer receiving chat messages.(GMS-1768)
A user-friendly message is now displayed when security permissions are not sufficient to allow GMS to change options in Configuration Server. The new message is ERROR: Insufficient permissions to perform this operation. Previously, the message was Error: Server Error. (GMS-1592)
The _callback_number parameter in the Service Management UI is now a mandatory parameter. Previously, the Service Management UI allowed a voice Callback to be defined without this parameter. (GMS-1551)
The GMS JavaScript sample now correctly displays the latest messages from the customer. (GMS-1595)
GMS now has improved high availability support for outbound calls when ORS fails after a call is connected to the customer. Previously, after the oubound call was made to the customer and if ORS failed, it resulted in a failed Callback, and the Callback would not be tried again. (GMS-1530)
You can now use a GMS cluster with the embedded Cassandra instance. If you need to repair the nodes, you must use Cassandra external tools (for example, nodetool). (GMS-1538)
GMS no longer throws a Null Pointer exception after reconnecting to Configuration Server. (GMS-1738)
The Immediate notification mode has now been added to the Statistic service. (GMS-1708)
The GMS response to complex statistics has been enhanced to reflect the Stat Server message; for example:
"extensions": [
{ "VOICE_MEDIA_STATUS": 4 }
],
Previously, GMS returned a PSDK formatted message; for example:
{"value":0,
"tkvvalue":null,
"stringValue":null, "valueType":{},
"stringKey":"VOICE_MEDIA_STATUS",
"binaryValue":null,
"intValue":4
}
(GMS-1732)
In the chat push notification (using CometD or CustomHTTP mode), the chat notification events that are received from the agent can now be filtered according to the message type:
- Notice.Joined
- Message.Text
- Notice.Left (disconnected)
- Notice.TypingStarted
- Notice.TypingStopped
- Notice.PushUrl
- Notice.Custom
The filter is an option that you can set in the main chat section, using the option filtering_chat_events, or for a specific chat service, using the option _filtering_chat_events, with a comma-separated list of message type events. The filter excludes the events listed in the option from the conversation with the client (prior to delivering them to the customer client application). (GMS-1691)
GMS now correctly closes terminated connections when sending CustomHTTP notifications. (GMS-1681)
An empty event no longer appears in the transcript for the client. Previously, when a client created a chat session and prior to the agent joining, an external user type was able to connect to send various information. This connection message for an external user type created an empty event in the transcript. (GMS-1619)