Translate values in custom registers so each user sees them in the language selected in their user profile.

How translations for custom registers work

Administrators can use the translation page to translate values in custom registers, such as extended properties, positions, and other custom fields, into the languages used by the organization.

When the values are translated, users automatically see them in the language selected in their user profile.

Previously, administrators had to create all values in one language because the values could not be translated into other user languages.

Example: Translate extended properties

If your extended properties contain values in Norwegian, you can add English and Swedish translations. Users who have selected English as their language will then see the English values without the need for manual workarounds.

Example: Translate the position register

If you use the contract module and created the position register in English, but use Norwegian or Swedish contract templates, you can translate all position titles into those languages.

When you create a new contract, the position title automatically appears in the correct language.

Good to know about translations for custom registers

• Administrators manage translations on the translation page
• Users do not need to take any action. Values automatically appear in their selected language
• Translations will also be implemented for reports in the future