Translations
The "Translations" tab
The Translations, available in the form editor, allows adding translations for the form, composite components and business components. It is also possible to add keys that override the default form content here (details in the chapter Platform translation keys).
This tab also allows adding or modifying validator messages related to components (details in the chapters Complex validations and Script validators).

Editing a key and value
After selecting a cell in the table you can edit both the key and the translation values for individual languages.
For multi-line values the edit field will automatically expand to show the entire content.

Deleting a key
To delete an entire translation row, click the icon located to the right of the key.

After deleting a key, a notification with an option to undo the operation will appear at the bottom of the screen.

Adding a key
It is possible to add a translation for any form element that displays text – titles, descriptions, labels, validation messages and content returned by external services.
Keys corresponding to validation error messages are added automatically after a validator is added. The exception is script validators, for which the key must be added manually.
To add a new key, use the button Add key located above the language columns.4

Clicking adds an empty row in which at least the key name (the KEY) column must be filled in. If the field is left empty, the system will automatically assign the name:
emptyempty.copyempty.copy1and so on, as needed.

Selecting the default language (tag)
The default language can be set in the table header. This option is available only while editing the process.
The default language is Polish.
To set a language as default, click the star icon next to the language code.
A yellow star indicates the currently selected default language. ![]()

Filtering empty translations
To hide keys without translations, click the icon located in the KEY.
An active filter is indicated by a crossed-out “eye” symbol
. Additionally, information about the number of hidden keys is displayed
.
Searching translations
The search works both by key names and by translation values.

If no results are found, the following message is displayed:
At that point the user is also offered the option to add a new key. After adding the key, the search field is automatically cleared.
Adding and editing languages
To add a new language, click the button to add a new column located on the right side of the table.

The name (tag) of the language can be changed by clicking its header.
Language code should comply with the ISO 639standard, written in lowercase. The list of supported codes is available at: https://www.oracle.com/technetwork/java/javase/java8locales-2095355.html
Determining the language used when opening a form
When a form is opened to be filled in the system determines the language in the following order:
1. The "locale" parameter in the URL
If the incoming address contains the localeparameter and the template contains translations for the given language, that language will be used.
field is sufficient.
2. Browser accepted languages (Accept-Language)
If the URL parameter is not available and in the Webforms configuration the parameter:
then the system will take the language from the Accept-Languageheader, provided the template has the appropriate translations.
field is sufficient.
3. The template's default language
If none of the above conditions are met, the template default language, set in Eximee Designer, is applied.
Last updated
Was this helpful?
