HaloITSM

HaloITSM Guides

Documentation to assist with the setup and configuration of the HaloITSM platform

Guides > Languages in Halo

Languages in Halo

In this guide we will cover:

- Changing Language per Agent

- Setting a Default Language

- Customise Language

- Add Translations Shortcut



Admin Guides:


Changing Language per Agent

You can change your own language under your agent profile. Go to the top right corner and click your profile picture > My Account > Preferences tab > Usability dropdown > "Application Language". This will be set to the global setting by default but can be changed.


Fig 1. Changing the language of an agent.


Setting a Default Language

In Configuration, you will find the Language module in the Advanced section.


Fig 2. Language module.


Clicking into this will show the below screen, where 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.


Customise Language

Clicking into the "Customise Language" button will bring up the list of languages currently imported into your Database.


The following screen will then show. Here you have the option to import/export the language pack to edit it in bulk, or add custom translations.


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 the first two fields.


Fig 4. Import/Export options on a language pack.


Clicking "Export Custom Translations" will provide an Excel file of what each term in Halo is called, like below. This can be edited and then reimported to edit how each term is called.


This will show entities that have been custom named by yourself instead of hard-coded into Halo.


i.e. "Service" is preconfigured within Halo, but the service type like "Laptop Request" is custom.


Fig 5. Section of the export file.


In the following tabs, you can then edit the phrasing of the pre-configured areas by editing the language pack.


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. 


If I change "Tickets" to "Calls"...


Fig 6. Changing the language pack.


You can see where the word "Tickets" appears, it now says "Calls" instead.

Note: If changed with this method, the word will change anywhere it appears - you cannot specify this to a certain area.


Fig 7. Tickets configuration changed with the language pack.


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. Once a string is added, this will be translated. 


Fig 8. 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 9. 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. 



Popular Guides

Pin It on Pinterest