We know many companies have branches all over the world and it would be more effective for the employees to have the system they work with every day in their native language. Flowis offers wide possibilities of translations to make the user experience as neat as possible.
Translations are set up in three different sections – System Translations, Content Translations, and Custom Translation Keys. What is the difference?
System Translations
These translations contain formulations used in system buttons, notifications, administration section, etc. – every word that was a part of Flowis before you started using it and configuring it for your company.
Content Translations
As you might assume, Content Translations contain all the formulations from your configurations – names of Statuses and Workflows, names of the fields in Transaction Types, names of Custom Tabs, etc. Everything that you set up to make Flowis work for your company is translated there.
đź’ˇ Tip: E-mail templates are not translated there - please use the possibility to add multiple versions for various language mutations in your e-mail templates.
Setting up System & Content Translations in Flowis
The first step is to create a new locale (search for Locales in the left menu). Set up its name (e.g. SK), and native name (e.g. Slovensky) and mark it as active.
Then you have to wait for the system to generate translation keys for System Translations. It may take a few minutes. If it takes longer than a day, please, contact your IT administrator.
Once you have the translation keys of System Translations generated (that means when you open System Translations, it is not a blank table anymore – there is a list of thousands of translation keys), you can start translating. You can do so either one by one – edit each of the rows (always look for the “Value” field in the table at the bottom) and save it manually; or you can download the whole list, translate it in your sheets editor (fill in the Value column), and import the whole list to Flowis.
The same applies to Content Translations, the only difference is that you do not need to wait for translation keys to be generated – they are available immediately.
Setting up Custom Translation Keys in Flowis
Custom Translation Keys are not generated automatically – you need to create them manually. When creating a new Custom Translation Key, you need to fill in following fields:
- Name – default translation which will be shown for this key unless Content translation is defined
- Key – the technical name, use lower-case and under-scored values
- Description – only for your internal purpose, it’s not used anywhere else in the application. You can describe where this translation key is used
After creating the Custom Translation Key, it is necessary to re-run translation generation in Locales:
Then you can translate this Key into another language in Content Translations – in the filter box Object type, choose Setting::CustomTranslationKey. You will see a list of all Custom Translation Keys and can translate them the same way as all the other Content Translations.
