_max_dial_attempts
Section: Voice - User Terminated
Default Value: 3
Valid Values: Integer
Changes Take Effect: Immediately
Maximum number of attempts to call the customer.
_suppress_sensitive_logging
Section: General
Default Value: false
Valid Values: boolean
Changes Take Effect: Immediately
Introduced: 8.5.226.01
If this option is configured to true, the Callback service no longer logs sensitive user data. Note that, in addition to this option, you can also update Composer to version 8.1.561.17 and higher which also eliminates sensitive logging. See Masking Sensitive Information in Composer Tomcat Logs for further details.
_enable_user_data_on_targeting_start
Section: General
Default Value: false
Valid Values: boolean
Changes Take Effect: Immediately
Introduced: 8.5.226.01
If this option value is true and if the Callback service receives a start request that contains user data, the Callback service attaches the user data to the WaitForTarget strategy start request. The user data is attached as a JSON string using the SERVICE_REQUEST_UDATA key.
If the service request does not contain user data or if this option value is false, the value for the SERVICE_REQUEST_UDATA key is the NOT PROVIDED string.
8.5.227.01
Genesys Mobile Services Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 07/09/21 | Update | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features and enhancements:
- GMS no longer supports the following Operating Systems:
- Windows Server 2008
- Red Hat Enterprise Linux 6
- The new _enable_user_data_on_targeting_start option allows you to add user data to the WaitForTarget strategy within the start request. (GMS-8387)
- The new _suppress_sensitive_logging option enables you to hide sensitive user data in logs. (GMS-8296)
Resolved Issues
This release contains the following resolved issues:
If you created a GMS application that does not use the default application name, GMS now correctly creates services through the Admin UI. (GMS-8386)
The Context services operation now gives correct calculation results and no longer counts some requests twice. (GMS-8366)
After a disconnection with Chat Server, GMS now correctly reconnects the notification channel. Previously in this scenario, the notification channel with Chat Server may not have been restored and CometD Chat V2 API requests might have failed. (GMS-8359)
When returning from a plugin execution, the callback service now properly handles a target specified with replyAction set to route_to_rp and replyMesg set to the JSON string of a Routing Point (RP) target expression. (GMS-8338)
The Callback service now attaches the value of the _max_dial_attempts service option using the GMS_Max_Dial_Attempts key to the current interaction. (GMS-8327)
The callback service now properly attaches the following KVPs to the customer call: _CB_T_CALLBACK_ACCEPTED, _CB_T_CUSTOMER_CONNECTED, and _CB_T_SERVICE_START. (GMS-8326)
Authentication credentials provided in the client's WebAPI CometD message are now masked in GMS logs. Previously, these credentials were logged in plain text.(GMS-8319)
GMS now supports warmstandby with Message Server, that is, when the primary is shutdown or for a primary/backup switchover. (GMS-8106)
Upgrade Notes
Further instructions are available in the upgrade section of the Genesys Mobile Service Deployment Guide.