Jump to: navigation, search

8.5.000.12

Genesys Mobile Services Release Notes

Release Date Release Type Restrictions AIX HP-UX PA HP-UX IPF Linux Solaris Windows
03/03/14 Hot Fix X X

Helpful Links


New in This Release

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release also includes the following corrections or modifications:


GMS now sends the correct attached data to Chat Server. Previously, GMS was sending incorrect attached data for FirstName, LastName, and EmailAdress. (GMS-1336)


GMS chat no longer encounters a conversion issue involving multi-byte characters encoded in UTF-8. (GMS-1331)


The refresh time for chat events has been decreased to two seconds. Previously, the notification period to receive events was five seconds (maximum). (GMS-1332)


GMS now forwards customized user data to Chat Server. Request parameters starting with ATTACH_ that are passed in the Create chat interaction request, are treated as user data and are attached to the chat interaction. (GMS-1327)


The following new methods have been added to provide access to storage associated with a service. For further information, see the Genesys Mobile Services API Reference.

GET service/{service id}/storage - retrieves the entire list of key/value pairs
GET service/{service id}/storage/{key}- retrieves individual value (binary or text)
POST service/{service id}/storage - creates new
POST service/{service id}/storage - updates existing Key/values are always in the body. An individual key update through the URL is not supported.

(GMS-1330)


GMS now supports additional NoticeType events for Chat sessions:

  • NoticeType.Custom—This is part of the chat transcript event.
  • customNotice—This event can be sent using the GMS Chat API with the following path:
    POST /genesys/1/service/{serviceId}/ixn/chat/customNotice
    The message parameter will contain the custom message.

(GMS-1328)


This page was last edited on March 16, 2015, at 13:16.
Comments or questions about this documentation? Contact us for support!