General
Translations are often done during the deployment project, but can be modified later. If you need help with translations, please do not hesitate to contact our support team.
With Global Translations it is possible to alter and translate commonly used terms and for example the menu titles in the CRM system. Therefore, they should not be used to make larger translations of the system but to adjust the terminology.
You can examine and edit the Global Translations in Settings → Global Translations.
The picture below shows some fields that can be globally translated in those languages that are set active in the system (more information in the guide Activating languages in the system). You can translate the fields shown in the list in the textboxes of each of the languages’ columns. When you are done, remember to click the Save button at the top right corner. A single field and all its translations can be removed by clicking the Remove button (red x icon) after the row.
If a term that needs translating is not shown in the list, you can add it by clicking the Add Translation button in the top right corner above the translations. The button opens up a window (see the picture below) where you can search for the needed term using the Search field. You can write the whole term or just parts of it. The list below the field updates while you are writing and suggests terms found in the system that include the search input. When a suitable term appears in the list, you can add it straight from the list by double-clicking the term. Using the suggestions list is not mandatory, you can also write the wanted term in whole in the Search field and then click the Add Exact Text button next to the field. Using this method demands extra care with spelling.
Translation Keys
These are specific translation keys used with Admin tool Global translations when the CRM-service system terminology is changed to fit the customer needs.
New Account
Window pop-up when new entity is created the translation key is
entity_dialog.new.accounts
Where the module (red) can be changed to any example quotes, contacts, relations etc…
First block of each module
With all modules, there is this first block that is called example Ticket information, potential information and so on. If you need to change the name of that permanent
LBL_TICKET_INFORMATION
Where the module (red) can be changed to any example quote, contact, account etc…