Translations

Translations let administrators change the wording Amplify uses, so it matches your organization's own terminology — for example, calling benefits impacts, giving the Initiative Workbook the name your teams know it by, or rewording a notification email. They're changed under Administration > Translations.

This article covers both the Advanced and Simple Models, and needs administrator access, or an admin role with access to Translations — see Admin Roles.

How translations work

• Every piece of text is a string — each label, button, message, and email in Amplify is listed with its Key, which identifies where it's used, and its Default Translation, the wording Amplify uses as standard.
• Your wording replaces the default — enter a Custom Translation, and it's used instead of the default. Leave it empty to keep the default.
• Changes go live when you restart — each change is saved as you make it, but isn't shown until you click Apply and Restart. You can make several changes, then apply them together.
• Each language has its own wording — where your organization uses more than one language, choose the language before making changes.

Finding the right string

Amplify has thousands of strings, and the same words often appear in many of them. The quickest way to find one is by the wording you see on screen:

• Filter the Default Translation column for the words as they appear in Amplify, such as Request Stage Approval.
• Check the Key to tell similar strings apart. Keys are grouped by where they're used — expand a group to see each string in it. Some keys use older names for a feature, so search by the wording rather than the key.
• Expect more than one match for common words. A word like Benefit appears in page titles, menu items, buttons, and messages, each a separate string.

Changing a string

To change a string:

1. Navigate to Administration > Translations.
2. Where your organization uses more than one language, choose the language.
3. Find the string — see Finding the right string.
4. Click into its Custom Translation cell. An editor opens.
5. Type the wording you want to use instead. It's saved when you close the editor.
6. Repeat for any other strings you want to change.
7. Click Apply and Restart.

Amplify restarts, and your wording is shown to everyone. Apply and Restart is only available once you've made a change.

Dynamic fields

Many strings contain dynamic fields — a word inside %{ and }, such as %{user_name}. Amplify replaces each one with the right detail every time the string is shown. Dynamic fields appear throughout Amplify, in page titles, buttons, messages, and emails, and each string has its own — the ones in its Default Translation.

Kinds of dynamic field

• Item names — fields such as %{benefit}, %{benefits}, %{measure}, %{initiative}, and %{classification} are filled in with the name of a type of item, in the singular or plural. They use your wording where you've renamed the item — so the Benefit Register's title, %{benefit} Register, becomes Impact Register once benefits are renamed.
• Details — fields such as %{user_name}, %{name}, %{count}, %{link}, and %{approval_status} are filled in with a specific person, item, number, link, or status. What a field shows depends on the string — read the rest of the sentence to see what it'll be. For example, %{name} is a person's name in an email's greeting, but an item's name on its button.

Using dynamic fields

Your wording can either:

• Keep the dynamic fields — use every dynamic field in the default, spelled exactly as it is, and no others. You can move them, and change the words around them.
• Leave them all out — use plain wording, with no dynamic fields. The details they'd fill in aren't shown.

Amplify checks when you save. Where your wording has some of the default's dynamic fields but not all, or one the default doesn't have, it isn't saved, and a message says what's wrong.

For example, where the default is View %{name}:

• Open %{name} — saves, and shows the item's name.
• Open item — saves, without the name.
• View %{title} — doesn't save, as %{title} isn't one of this string's dynamic fields.

Some strings are lists, such as the names of the days. Each item is changed on its own, and can't contain dynamic fields.

Examples

Renaming benefits to impacts

To call benefits impacts across Amplify:

1. Filter the Default Translation column for Benefit.
2. Find the item's name, under benefit in the models group. It has two strings — one, the singular, Benefit, and other, the plural, Benefits.
3. Enter Impact for one.
4. Enter Impacts for other.
5. Work through the remaining matches, and change each one that should say Impact.
6. Click Apply and Restart.

Every string that uses %{benefit} or %{benefits} now says Impact or Impacts on its own — such as the register's title, and the names of benefit approval workflows. The remaining matches are strings with the word written out in full, so they need changing one by one.

Renaming the Initiative Workbook

To give the Initiative Workbook the name your teams use, such as Business Case:

1. Filter the Default Translation column for Initiative Workbook.
2. Change each match. The name appears in several places — the menu item on initiatives and projects, the page's title, messages when its layout is saved, and its settings for administrators.
3. Click Apply and Restart.

The Initiative Workbook's keys end in project_brief, its earlier name, which is why it's easier to find by its wording.

Rewording a notification email

Each email is made up of several strings — its subject, title, message, and button. For example, the email sent when someone is made the owner of an item is under assigned_as_owner:

Each custom translation keeps the dynamic fields of its default — see Dynamic fields. To find an email's strings, filter the Default Translation column for a sentence from it. For which emails are sent, see Notifications.

Date, number, and currency formats

How dates, numbers, and currency are shown is set by strings too. Before changing them here, check the Locale under Administration > Site Settings — choosing your region, such as English (Australia) or English (UK), sets them for that region in one go. See Site Settings.

Date formats use codes for each part of the date — for example, %d/%m/%Y shows 31/12/2026. These codes aren't dynamic fields, and aren't checked when you save, so check the result after you apply it.

Going back to the default

To go back to a string's default wording:

1. Click into its Custom Translation cell.
2. Delete the wording.
3. Click Apply and Restart.

The custom translation is removed, and the Default Translation is used again.