Genesys Mobile Services Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release includes only resolved issues.
This release contains the following resolved issues:
If the _status_notification_target and _callback_events_list options are both set in the Callback service configuration and if the _status_notification_target option is not set in the _callback_events_list Transaction List object, then Callback now uses the _status_notification_target value configured in the Callback service. Previously, in this scenario, the _status_notification_target option defined in the Callback service was ignored. (GMS-3699)
You can now configure your firewall to allow HTTP messages matching the /internal/* pattern and ensure that notifications and metrics are submitted. Previously in this scenario, an HTTP 401 error would have been returned because authentication information was missing. (GMS-3690)
If the first selected agent does not answer the call, the callback strategy now correctly selects another agent. (GMS-3653)
The vertical timeline of the Context Services interface no longer fails to render if it contains a state whose media type cannot be found. Previously, the interface may have failed to render when the mapping of the Business Attributes was not correctly set in the business-attribute section of the Context Services application. (GMS-3737)
Genesys Mobile Services
GMS no longer throws the IllegalArgumentException: Cannot convert date error that blocked the display of the Service Management UI. (GMS-3702)
No special procedure is required to upgrade to release 184.108.40.206.