Genesys Engage on-premises

 View Only

Discussion Thread View

  • 1.  Widgets / GMS localization

    Posted 05-08-2019 09:48
    Hi 

    Does anyone know how to deploy a "full" localization file for a GMS/Widgets integration? I have followed instructions for the callback widget here: https://docs.genesys.com/Documentation/GWC/latest/WidgetsAPI/CallbackLocalization, and it works fine, but I don't know how to translate the error messages received from GMS. For example, if the user inserts a callback number not allowed, we get the error "Customer Number is not allowed, because it is invalid. Check option _disallow_impossible_phone_numbers" (code 40040). How can this error be translated? I have tried to  include them in the "Errors" section of the localization file, but it does not work:

    "Errors": {
    "501": "Parámetros inválidos.",
    "503": "Falta apikey.",

    <<…>>

    "40040": "Introduzca un número válido.", 
    "unknownError": "Algo fue mal. Perdón por los inconvenientes. Por favor, chequee sus parámetros de conexión e inténtelo de nuevo.",
    "phoneNumberRequired": "Número de teléfono requerido."
    }

    Thanks a lot
    #Integrations

    ------------------------------
    Juan Carlos Valera
    ------------------------------


  • 2.  RE: Widgets / GMS localization

    Posted 05-24-2019 03:54
    Well,

    it seems that localization for these error messages coming from GMS is not supported in API v1, only in API v3 -> Not supported in premises, but in cloud environment only … which does not make much sense to me. I think it is a basic functionality

    Thanks

    ------------------------------
    Juan Carlos Valera
    Teamvision IT
    ------------------------------

    Original Message


Need Help finding something?

Check out the Genesys Knowledge Network - your all-in-one access point for Genesys resources