HaloCRM

HaloCRM Guides

Guides > Languages in Halo

Languages in Halo

In Halo you can change the language per Agent and have a global setting suitable for the region you operate in, while not exhaustive or complete, some of the languages we support are:

  • Polish
  • Italian
  • Swedish
  • Spanish

Changing your language


You can change your own language under your agent profile. Shown in figure 1. 

Fig 1. Changing the language of an agent


Setting the Global Default Language

Fig 2. Language module



Head to configuration and click on Language, here you will see an option to set the default language, customise any language used and allow users to select a language.


Fig 3. Setting default language for Halo 


Customise Language

 

Clicking into here will bring up the list of languages currently imported into your Database. Clicking into these will bring up the language editing screen, here you can navigate through the tabs and adjust the language as necessary to suit your needs. This includes the key terms.


To translate a phrase/term in your Halo you will need to find this in the language pack. Terms are separated in to separate tabs depending on where/how they appear in Halo. You can either search using the 'Description' column, this is the description of where the term is found in Halo. Or, you can search using the 'Default Value' column, this is the visible term without any translation. The 'Translated string' column is the string that the default value will be translated into when using this language pack. 


As an example you may refer to your Clients as Consumers or Customers and would like to change this in Halo, you can change this here. In figure 4 the default value is 'Client' but I would like this to instead be 'Customer' so I have changed the translated string in the language pack I am using to reflect this. 


Fig 4. Changing the term 'Clients' to show as 'customers'


If you notice some phrases are not translated in the language pack, for example a custom field label, this will be due to the translated string not being present in the language pack. For example, in figure 5 the custom field 'Paper Size' does not have a translated sting so will not be translated, once a string is added this will be translated. 


Fig 5. Field label without a translated string


Add Translations shortcut


Some field labels will have an 'Add translations' shortcut next to them when being created/edited. 




Fig 6. Add Translations shortcut against field


This shortcut allows you to quickly add a translation for the string in this field to a language pack(s) of your choice, without needing to navigate to the language pack configuration. It is important to note that any fields that have this shortcut against them do not appear in the language pack, a translation for them must be added using the shortcut. Entities that have this shortcut include but are not limited to:

- Service name

- Dashboard widget title 

- Self-service portal button title and description override


If you cannot find a field in the language pack it likely uses the 'Add translations' shortcut instead. 


Load/Export Language Pack File


If you have an updated language pack from us or one of our previous software packages you can import from or export to this using these field and the appropriate settings in the software.


Fig 7. Load/Export Language pack file 



Popular Guides

Pin It on Pinterest