Contents
Localization File
Overview
The localization file allows you to customize the way you send a message to subscribers. You can define several messages based on the language of the customer.
Localization file
Format
<?xml version="1.0" encoding="UTF-8" ?> <messages> <message id="welcome"> <locale language="en_US"> <entry key="text">Welcome</entry> </locale> <locale language="de"> <entry key="text">Willkommen</entry> </locale> <locale language="fr"> <entry key="text">Bonjour</entry> </locale> <locale language="es"> <entry key="text">\u00A1Hola</entry> </locale> <locale language="ja"> <entry key="text">\u3053\u3093\u306B\u3061\u306F</entry> </locale> </message> <message id="welcomeArgs"> <locale language="en_US"> <entry key="text">Dear customer $customer.lastname, how can you be reminded</entry> </locale> <locale language="de"> <entry key="text">Sehr geehrter Kunde $customer.lastname, wie können Sie daran erinnert werden</entry> </locale> <locale language="fr"> <entry key="text">Cher client $customer.lastname, comment pouvez-vous être rappelé</entry> </locale> <locale language="es"> <entry key="text">$customer.lastname Estimado cliente, \u00BFc\u00F3mo puede ser recordado</entry> </locale> </message> </messages>
Arguments
Arguments can be added to the message, GMS will replace the arguments in the message with correct value provided when you publish the message.
Simple style | Expanded style |
---|---|
{ "message":"welcome", "tag":"yourtag", "mediaType":"localizestring", "locArgs":{ "customer.lastname":"Doe" } } |
{ "message":"welcome", "tag":"yourtag", "mediaType":"localizestring", "locArgs":{ "customer":{ "lastname":"Doe" } } } |
For example for language option (provided at subscription time) equals to "de" (German), the customer will receive the following message:
Sehr geehrter Kunde Doe, wie können Sie daran erinnert werden
Genesys Mobile Services Configuration
Please refer to the push section documentation on Genesys Mobile Services Configuration Options.
This page was last edited on February 28, 2013, at 20:28.
Comments or questions about this documentation? Contact us for support!