Page Comparison

This section helps you understand how to customize your application instance for use by a global user community.

...

How Internationalization and Localization Works   

CSM Intelligent Service Management provides the internationalization support through language catalogs at two different levels. The system level language catalog contains predefined translations of all the menus and screen options for the supported languages. In the application, every system defined communication template comes with a translation in each of the supported languages. Items such as field labels, action links, toolbar names, navigation group names, messages, are available in the supported languages. The names of workflow entities or descriptions, ticket template names or descriptions, task group names, defined search names or descriptions, CCTI values, custom field labels, system defined metric names or description, ticket status, ticket reason code, ticket phase, ticket priority, urgency, impact, and CI status are also available in the language the user selects.

...

Entities Only Available in English

CSM Intelligent Service Management renders the following entities only in English:

...

The locale of the browser or the external portal does not affect the locale of CSM Intelligent Service Management. The application uses the locale as defined in the User Profile.

...

You can modify the defined searches to display the results in the language of the user locale. To add a prefix i18n_ to the column names, modify the select query. For example, modify the status column to i18n_status in the select query. The application automatically translates the query results for such columns. If the related defined search has i18n_ prefixed columns, the ad-hoc reports display the translated data.

Bulk Process Data

You can import language translations into the system by using Bulk Process Data. The Language Catalog sheet enables you to enter the keys and the relevant translations in different languages.

Localization of Email Configuration

...

• If the translation for the used communication template is available in the locale of the intended recipient.
  The application generates the communication record in the language of the locale the recipient specifies. If the translation is not available, CSM Intelligent Service Management uses the Default communication record.
• The application matches the language of the token values with communication record while replacing the token values with actual values. If the communication template uses custom fields, the custom field translation must be available in the locale of the user.

...

The following behavior is expected behavior when the communication records are delivered. The behavior is based on the locale of logged in user and the intended recipient, and the communication records generated.

• CSM Intelligent Service Management matches the locale of the recipient against the locale of the available communication record. If the locale matches, The application sends the localized communication record. If there is a mismatch, the default communication record is sent.
• The application decides the communication record while generating the communication record. The application then sends the communication record in the new locale of the recipient in the following conditions:
  When the locale of recipient changes after the generation of communication record, communication record is available in the new locale. When the communication record is not available in the new locale, the communication record is sent in the older locale.

Processing of Inbound Emails

CSM Intelligent Service Management parses the keywords in subject line to decide the action to take on the incoming email. The application creates a ticket or updates an existing ticket that is based on the keywords in the subject line. When the subject line contains keywords other than English, the translation of keyword is present in the language catalog to enable the keyword parsing.

To facilitate parsing of standard keywords, the application contains the translation of the following keywords in all the support languages. The first keyword match determines the locale of the message. The CSM Intelligent Service Management parses the message only for the identified locale.

...

• The bold or italicized characters are not supported in the Asian languages.
• Table sorting functionality is based on character sorting and has been validated only for English input values. Sorting do not work for other languages.
• If the password is specified in a language other than English, the password strength validations do not work appropriately. For example, number of characters, special characters, and integers.
Passwords do not work for different languages like Chinese or Japanese.
• Any localized calendar with a different start day of the week or local calendars are not supported. For example, start day of the week as Saturday.
• The browser locale controls the status bar messages. If the application makes an AJAX request, the status message gets translated.
• The label captions of the Browse button for File Uploads depend the browser. The application does not control them.
• Confirmation prompt dialogs with buttons such as Ok, Cancel, and Confirm depend on the browser. The application does not control them.
• Web service internationalization has some limitations.
• In the trend reports, when data points are based on months, the names of months appear in English.
• A user with a locale other than default has to specify the search criteria only in English. To get proper results while searching from Home, enter values such as Impact, Urgency, Priority, or Source fields in English.
• For any searches in ticket types, the user can select the input value from the available drop-down list. The system translates the locale language to English and then runs the query to generate correct results.
Alphabetical sorting of the items in lists as in Ticket Templates is based on character sorting.
• SERVICE REQUEST
• INCIDENT
• PROBLEM
• CHANGE REQUEST
• TASK TICKET
• TICKET
• CASE
• RE:
• FW:
• Out of the Office
• Returned Mail
• auto: cn
• mailer-daemon
• undeliverable:
• Approved
• Rejected

Build Language Catalog

CSM Intelligent Service Management supports the following languages:

• English
• Chinese
• Japanese
• Spanish
• French
• German
• Brazilian Portuguese
• Russian
• Swedish
• Finnish

The configuration parameter ENABLE_SHARING_OF_LANGUAGE_TRANSLATIONS must be set to YES to enable internationalization and localization. Click your profile picture, select My Account, and set your language preference. CSM Intelligent Service Management replaces the UI text elements and all system defined entities like auto-routes, workflow actions, communication templates with matching entries in the selected locale.

...

Follow these steps:

1. Select MANAGE, ADMINISTRATION, Tools, MANAGE> ADMINISTRATION> Tools> Language Catalog to view a list of screen elements of the application.
   To fetch new entries from the predefined areas like Action Name and Templates, click Update Elements .

2. Override Existing Translation: To provide a custom translation for an existing key, click the Translation Available field corresponding to the desired key.
   Note: The Key field displays the source text in English. The same source text is also displayed in the English Text field. The Translation Available field displays information on the languages in which the key has been translated. 

3. Click Edit in the Translations tab to edit the Language and Translated Text fields.
4. Add Translation for New Keys: Click the + button.
5. Specify the Language and the Translation Text for the key.  
   The key must be unique. You can edit the key name, language, and translated text.
6. Click Save to save the new key entry.
   The language catalog is ready with translations for new keys.

Valid Locales

CSM Intelligent Service Management supports the following languages:

Timezones

The Timezone field in CSM Intelligent Service Management is a Read Only field. You are not required to set the timezone for a given user manually. The timezone and the timestamp that is visible to users in the application depends on the system in use. When a user logs in to the application, the user account timezone value is synched with the system in use.

The accepted time zone values are derived from the tz database. Wikipedia maintains a list of tz database for time zones at: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones. Visit the link for the list of valid time zone values.