Multi-Language Set Up & Configuration

This page covers:

Multi-Language Functionality in Amp Impact

Organizations that work across geographies often use their system in different languages. While Salesforce’s Translation Workbench supports meta-data translation into multiple languages, data elements are not easily translated natively with Salesforce.

Amp Impact comes with the ability to translate certain data elements into up to three additional languages.

This includes translation for:

• Manage Indicators

• Manage Framework

• Set Targets

• Add Results

• Performance Graphs

Multi-language set up and configuration has two levels:

1. Meta-Data Translation using Salesforce Translation Workbench

2. Reference Data Translation into up to three additional languages using Amp Impact multi-language capabilities

These categories are described separately below in detail.

Metadata Translation using Salesforce Translation Workbench

Enable Translation Workbench

1. From Setup, enter Translation Language Settings in the Quick Find box, then select Translation Language Settings.

2. On the welcome page, click “Enable”.

Open

For more details on configuring the Translation Workbench, refer to the Salesforce documentation.

Add supported languages in Translation Language Settings

1. From Setup, enter Translation Language Settings in the Quick Find box, then select Translation Language Settings.

2. Click “Add” to add any language(s) that you will be using.

3. For each language that you intend to use:

   1. Mark the language as Active.

   2. (Optional) Specify one or more translators who have permission to enter the translations.

4. Click “Save”.

   Open

   

Reference Data Translation Using Amp Impact Multi-Language Feature

Specify Language Code by Tranlating the USER_LANGUAGE_CODE custom label

The custom label USER_LANGUAGE_CODE is used to codify each language that will be used in the system. By default, USER_LANGUAGE_CODE has a value of ‘0’ (zero) for the default language, and it can be translated using Translation Workbench to codify up to three additional languages. 

1. From Setup, enter Custom Labels in the Quick Find box, then select Custom Labels

2. Click on label USER_LANGUAGE_CODE.

3. On the Custom Label page, click New Local Translations / Overrides.

4. On the New Translation page, select the language in the Language field.

5. In the Translation Text field, enter the Language Code

   1. Language Code for first language (Language of text entered in field ampi__[FieldName]_Language_1__c) is ‘1’

   2. Language Code for second language (Language of text entered in field ampi__[FieldName]_Language_2__c) is ‘2’

   3. Language Code for second language (Language of text entered in field ampi__[FieldName]_Language_3__c) is ‘3’

Add Translated Fields to Add/Edit Pop-Ups

Amp Impact has three additional language fields for each supported Text, Text Area, or Long Text Area field for users to enter translated values of the default field.

E.g Amp Impact field ampi__Description__c on ampi__Indicator__c object has 3 associated language fields:

• ampi__Description_Language_1__c

• ampi__Description_Language_2__c

• ampi__Description_Language_3__c

These language fields are used to enter Indicator Definition (or other reference data) in upto 3 different languages. 

E.g. if custom label USER_LANGUAGE_CODE is translated as 0 in English, 1 in Spanish, 2 in French, and 3 in Portuguese, then Indicator Definition can be specified for these languages as follows:

• ampi__Description__c = % of patients who are new

• ampi__Description_Language_1__c = % de los pacientes que son nuevos

• ampi__Description_Language_2__c = % des patients qui sont nouveaux

• ampi__Description_Language_3__c = % dos pacientes que são novos

To enable users to enter or edit reference data in multiple languages, add these fields to following field sets:

Add Translated Fields to Data Tables & Filters

To display data (e.g. Indicator Definition) in user’s language, translated fields should be added to field sets that control data tables and filters:

• For all supported Text and Text Area fields, add the translated formula field (i.e. ampi__[FieldName]_Translated__c) to field sets.

• For all supported Long Text Area fields, add the default language text field (i.e. ampi__[FieldName]__c) to field sets.

The fieldsets that control data tables and filters are as follows:

Add All Language & Translation Fields to Page Layouts

To allow users to access language and translation fields, add them to the page layouts of objects. 

Related lists (e.g. Geographic Area, Objectives, Thematic Areas on the Project page layout, Project Indicator Geographic Area on the Project Indicator page layout, etc.) are displayed in default language instead of the user's language locale. 

If System Admin wants to display these fields in the user's language locale, they can add ampi__[Field_Name]_Translated__c (e.g. ampi__Geographic_Area_Translated__c) to the related list from page layout of that object.

[Optional] Relabel the Language Fields to Reflect the Actual Use Case

The field labels of language fields can be relabelled so that it is easier for users to identify the field used to store the data in a particular language

E.g. if Language 1 = French, then the field label for ampi__Indicator_Definition_Language_1__c, “Indicator Definition Language 1”, should be relabelled to “Indicator Definition (French)”.

Setup Custom Fields to work with Multiple Language Capability

Text / Text Area fields

1. Create a new custom label 

   1. Set up language codes by translating the custom label in same format as USER_LANGUAGE_CODE as under ‘Specify language code by translating the USER_LANGUAGE_CODE custom label’ above.

2. For a Text/Text Area field [Field_Name]__c, System Admins need to create 4 additional fields with API names as follows: 

3. Add language fields to add/edit popups as done above.

4. Add translated field to data tables and filters as done above.

5. Add all fields to page layouts as done above.

Long Text Area Fields

1. For a Long Text Area field [Field_Name]__c, System Admins need to create 3 additional fields with API names as follows: 

2. Add translated field to data tables and filters as done above.

3. Add default Long Text Area field (i.e. [Field_Name]__c) to data tables and filters

4. Add all fields to page layouts as done above.

General Multi-Language Use Set Up

Create or Update Users with Locale Settings for Specific Languages

1. From Setup, enter Users in the Quick Find box, then select Users.

2. On the All Users page:

   1. To create a new User, click on the New User button.

   2. To edit an existing User, click on User’s name.

3. On the User Details page, navigate to the Locale Settings section.

   1. Change Language to user’s preferred language

4. Click on “Save”.

Amp Impact Multi-Language Feature Limitations

1. Amp Impact currently supports up to four languages (the system default and three additional languages).

2. This feature only works with languages that use the Roman alphabet (e.g. Spanish, French etc.). Languages, such as Arabic and Mandarin, that do not use the Roman alphabet are not supported as yet.

3. This feature does not support exporting Target/Result or Financial data in multiple languages at once.

4. If a user creates an aggregated Project Indicator, or sets the aggregation criteria for an aggregated Project Indicator, the details in aggregation criteria popup display in that user’s language (i.e. the default language as per user’s locale settings).

5. If one of the four fields language fields (ampi__[Field_Name]__c, ampi__[Field_Name]_Language_1__c, ampi__[Field_Name]_Language_2__c, and ampi__[Field_Name]_Language_3__c) is modified, the other three must be manually updated to match the modified data, as this does not happen automatically, and the user does not receive a notification to ensure that data is synced.

6. Amp Impact does not support entering reporting or supplementary data in multiple languages (e.g. Qualitative Targets/Results, Reviewer Comments). A list of features not supported for multiple languages as of current release are as follows:

   • Activity Tracking

   • Financials (Budget Excel download/upload, Disbursements)

   • Risk

   • IATI Publishing

   • Submissions

     • Multiple languages can be used for Submissions by creating a different template for each language in which users would be submitting.

     • The following metadata cannot be translated, or it will cause the functionality to break:

       1. ampi__Submission__c RecordType values

       2. ampi__Question__c RecordType values

       3. ampi__Question__c.ampi__Response_Type__c picklist values

7. If a user is set up with a specific locale and language (different from the default language), and there is no translated data entered in the language text area and language text Amp Impact managed package fields for their preferred language, the user with that language setting will view data in the default language.

   • For example, if a system has an English User and a Portuguese User, and USER_LANGUAGE_CODE is translated in Portuguese as ‘2’. If the field value of ampi__Project_Indicator__c.ampi__Description__c is provided in English while ampi__Project_Indicator__c.ampi__Description_Language_2__c is left blank, then the English User will view the Indicator Definition in English and the Portuguese user will view it in the default language (as stored in ampi__Project_Indicator__c.ampi__Description__c) on the Set Targets page.

8. Multiple languages are supported for the following Text, Text Area, and Long Text Area fields :

Multiple languages are supported for the following Text, Text Area, and Long Text Area fields as of the Nashira (v1.38) release.