Jump to: navigation, search

Known Issues and Recommendations

eServices Manager Plug-in for GAX

The Known Issues and Recommendations section is a cumulative list for all 9.0.x releases of eServices Manager Plug-in for GAX. 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 Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues.



The HTML standard response editor is unavailable when using Internet Explorer 11.

Workaround: Use another supported browser.

ID: KM-5312 Found In: 9.0.003.06 Fixed In: 

eServices Manager is not compatible with GAX 9.0.102.03 and later versions.

ID: KM-5277 Found In: 9.0.001.08 Fixed In: 9.0.003.05

Internet Explorer 11 does not load Standard Response content properly.

Workaround: Use another supported browser.

ID: KM-4937 Found In: 9.0.001.08 Fixed In: 

eServices Manager is now backward compatible with 8.5.200.xx versions of Universal Contact Server (UCS).

ID: KM-4930 Found In: 9.0.001.08 Fixed In: 9.0.002.05

The Help (?) link opens the wrong version of the documentation.

Workaround: Use the following link: https://docs.genesys.com/Documentation/ESDA/9.0.0/ESMgr/KMwelcome.

ID: KM-4657 Found In: 9.0.000.09 Fixed In: 9.0.001.08

When using the standard response HTML editor, clicking Markdown generates additional HTML elements that move down any text already present in the editing box.

ID: KM-4655 Found In: 9.0.000.09 Fixed In: 

For WhatsApp Notification standard responses, if you have parameters in the Content section in JSON that are missing in the parameters list and then you click Edit JSON, the missing parameters are not immediately listed in the editor parameters list.

Workaround: After you click Edit JSON, add and delete characters in the Content field. The missing parameters then appear in the parameters list.

ID: KM-4654 Found In: 9.0.000.09 Fixed In: 

Adding duplicate parameters with the same index value can cause incorrect behavior when using the JSON Editor for WhatsApp Notification standard responses.

Workaround: Use the correct JSON structure for WhatsApp Notification standard responses and ensure this structure does not include duplicate index values.

ID: KM-4652 Found In: 9.0.000.09 Fixed In: 9.0.001.08

The Mark style does not appear correctly in the standard response HTML Editor.

Workaround:Open HTML Editor, click Source, find your text, and add span tag with attribute. For example:

<span style="background-color:Yellow;">Your text</span>
ID: KM-4643 Found In: 9.0.000.09 Fixed In: 

The HTML standard response editor does not have the Select All button.

Workaround: Use the keyboard combination Ctrl+A to select all.

ID: KM-4584 Found In: 9.0.000.09 Fixed In: 9.0.001.08

The buttons for Find and Replace are not present in the standard response HTML editor.

ID: KM-4583 Found In: 9.0.000.09 Fixed In: 9.0.001.08

Google Chrome and Microsoft Internet Explorer 11 do not show all emojis from the Emoij List in the standard response HTML Editor. This is a known issue with CKEditor ( click for more information).

Workaround: Use Mozilla Firefox.

ID: KM-4576 Found In: 9.0.000.09 Fixed In: 

The plug-in does not allow you to save an Apple Pay structured message if there is any text in the Supported Countries field.

ID: KM-4511 Found In: 8.5.305.09 Fixed In: 9.0.000.09

If, in the configuration of any business attribute value of the MediaOrigin business attribute, the rich-media-types section is missing (in Annex) but there are other section(s) with any other names at the same time, the Media Origin drop-down menu in the plug-in will be empty and a structured message under Standard Response cannot be created.

Workaround: All MediaOrigin business attribute values must have the rich-media-types section in Annex.

ID: KM-4866 Found In: 8.5.304.10 Fixed In: 

The plug-in does not perform a validation check on whether an imported or copied JSON contains duplicated or invalid properties. You must ensure the JSON does not contain duplicated or invalid properties before it is uploaded.

ID: KM-4291 Found In: 8.5.304.10 Fixed In: 

eServices Manager 8.5.302.02 and later releases are not compatible with GAX 8.5.260.xx or earlier releases.

ID: KM-3835 Found In: 8.5.302.02 Fixed In: 

Users who do not have the View Standard Response privilege can still import Knowledge Management objects.

ID: KM-3805 Found In: 8.5.302.02 Fixed In: 

eServices Manager displays an error if you search for a standard response using the Owner criterion, but the owner you searched for does not already exist in the system.

ID: KM-3552 Found In: 8.5.301.09 Fixed In: 

eServices Manager does not prevent you from creating or updating screening rules that have incorrect pattern syntax. For example, you must not use incorrect pattern syntax that has text before the function, such as abcdefFind("abcdef").

ID: KM-3497 Found In: 8.5.300.09 Fixed In: 


Internationalization Issues

Information in this section is included for international customers. Release numbers in the Found In and Fixed In fields refer to the English (US) release of eServices Manager Plug-in for GAX unless otherwise noted in the issue description.


There are no internationalization issues for this product.


This page was last edited on June 15, 2021, at 11:46.
Comments or questions about this documentation? Contact us for support!