Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

An organization may choose to customize Amp Impact to match the specific terminology users are familiar with.

Here are the areas where terminology can be updated or changed:

Translate Tabs 

  1. Navigate to Setup > Rename Tabs and Labels.

  2. Click Edit next to the relevant object name (e.g., Project).

  3. Enter the new tab names (singular and plural) to update the translation / terminology (e.g., Project → Investee).

  4. Click Next.

  5. Review updates and click Save.

Translate Field Labels

  1. Navigate to Setup > Translation Workbench > Translation Settings.

    1. Select Enable.

    2. Click “Add” under “Supported Languages” and select “English”.

  2. Navigate to Setup > Translation Workbench > Override.

  3. Select “Amp Impact” Package and “English” Language. 

  4. Select the Components to translate (Custom Field) and then the relevant object(s).

  5. Choose the Aspect “Field Label” to update field labels and “Related List Label” to update the labels displayed on related lists on a record detail page.

  6. Edit the Field Label Override to update the translation/ terminology.

  7. Click Save.

Customize/Translate Picklist Values

  1. Navigate to Setup > Object Manager.

  2. Click on the object with the relevant picklist field (e.g., Activity).

  3. Click on the Field & Relationships tab.

  4. Click on the name of the picklist field (e.g., Status).

  5. Customize the picklist values.

    1. To update a picklist value, click Edit next to the value.

    2. To create a new picklist value, click New at the top of the list of picklist values and fill in the fields accordingly.

While most Amp Impact picklists are unrestricted and can be modified, certain picklists have either restrictions or limitations. These are listed in the table below.

Object API Name

Field API Name

Restrictions/Limitations

Activity__c

Status__c

To update picklist values, both Label and API Name must be modified with the same value.

There are no restrictions on creating new picklist values.

Type__c

To update picklist values, both Label and API Name must be modified with the same value.

There are no restrictions on creating new picklist values.

Geographical_Area

__c

Type__c

There are no restrictions on editing or creating picklist values, but the changes made to this picklist field must also be made to Geographical_Disaggregation__c on Indicator__c and Project_Indicator__c.

Indicator__c

Data_Type__c

To update picklist values, both Label and API Name must be modified with the same value. The corresponding custom label (listed below) for the picklist value must also be translated:

  • INDICATOR_CURRENCY_DATA_TYPE

  • INDICATOR_MILESTONE_DATA_TYPE

  • INDICATOR_NUMBER_DATA_TYPE

  • INDICATOR_PERCENT_DATA_TYPE

  • INDICATOR_QUALITATIVE_DATA_TYPE

There are no restrictions on creating new picklist values, but additional picklist values will not display on SetTargets or AddResults.

Indicator__c / Project_Indicator__c

See footnote

Calculate_Total__c

This picklist is restricted. The default picklist value labels can be updated, as long as the API name is not modified.

Additional picklist values will not yield any calculations on SetTargets or AddResults.

Aim__c

This picklist is restricted. The default picklist value labels can be updated, as long as the API name is not modified.

Reporting_

Frequency__c

There are no restrictions on editing or creating picklist values, but the changes made to this picklist field must also be made to Report_Type__c on Reporting_Period__c.

Target_Frequency__c

There are no restrictions on editing or creating picklist values, but the changes made to this picklist field must also be made to Report_Type__c on Reporting_Period__c.

Geographical_

Disaggregation__c

There are no restrictions on editing or creating picklist values, but the changes made to this picklist field must also be made to Type__c on Geographical_Area__c.

Project__c

MI_Indicator_Order__c

There are no restrictions on editing or creating picklist values (via the Indicator_Type global value set to accommodate custom fields), but additional picklist values must be formatted such that:

  • Label = Custom field label

  • Value = Custom field API Name

MI_Project_Indicator_Order__c

There are no restrictions on editing or creating picklist values (via the Indicator_Type global value set to accommodate custom fields), but additional picklist values must be formatted such that:

  • Label = Custom field label

  • Value = Custom field API Name

STAR_Project_Indicator_Order__c

There are no restrictions on editing or creating picklist values (via the Indicator_Type global value set to accommodate custom fields), but additional picklist values must be formatted such that:

  • Label = Custom field label

  • Value = Custom field API Name

Project_Indicator_

Reporting_Period__c

Data_Tracked__c

This picklist is restricted. The default picklist value labels can be updated, as long as the API name is not modified.

Additional picklist values will not display on SetTargets or AddResults.

Question__c

RecordType

Record Type values for Question__c cannot be translated.

Reporting_Period__c

Report_Type__c

There are no restrictions on editing or creating picklist values, but the changes made to this picklist field must also be made to Reporting_Frequency__c and Target_Frequency__c on Indicator__c and Project_Indicator__c.

Result__c

Data_Tracked__c

This picklist is restricted. The default picklist value labels can be updated, as long as the API name is not modified.

Additional picklist values will not display on SetTargets or AddResults

Submission__c

RecordType

Record Type values for Submission__c cannot be translated.

Any changes made to a picklist on the Indicator__c object should also be made to the corresponding picklist on the Project_Indicator__c object, and vice versa (e.g. if a new picklist value “Bimonthly” is added to Reporting_Frequency__c on Project_Indicator__c, then “Bimonthly” must be also added to the Reporting_Frequency__c field on Indicator__c).

For details on picklists related to the IATI reporting functionality, please refer to the IATI Section.

Translate Custom Labels in Visualforce Pages and Lightning Components

Select custom labels are referenced in Visualforce Pages and Lightning Components as output text. To update this text, you need to also update corresponding custom labels. To do so: 

  1. Navigate to Setup > Custom Labels.

  2. Locate the relevant custom label. 

    1. The Categories column indicates:

      1. Which Visualforce page or Lightning Component references the custom label.

      2. Which item(s) - e.g. button, tooltip, pop-up header - display the custom label text.

  3. Click the relevant custom label (e.g., AVAILABLE_THEMATIC_AREA_LABEL) to view the label’s details. 

  4. Then add a new translation by clicking “New Local Translations / Overrides”.

  5. Select the Language as “English” and fill in Translation Text with the appropriate translation / terminology (e.g., “Available Focus Areas” to replace “Available Thematic Areas”).

  6. Click Save.

When a user downloads an Excel template from Set Targets or Add Results, they are given a set of instructions on how to properly set up the Excel sheet for upload. For any additional custom instructions that may be needed for your organization, use these custom labels to add further steps to the sections of the instructions sheet:

  1. UNDERSTANDING_THE_DOWNLOADED_EXCEL_CUSTOM

  2. PREPARE_EXCEL_FOR_UPLOAD_CUSTOM

  3. UPLOAD_EXCEL_INSTRUCTIONS_CUSTOM

  • No labels