Altamira Recruiting is a fully localized applicant tracking platform and both the back office recruiter environment and front office Career Centre can be displayed in different languages. To be able to successfully manage the localization of an Altamira Recruiting account, please review the following concepts.
Localization is performed on two levels: there are system supplied translations and user supplied translations. The system supplied translations include:
- All user interface labels and messages
- System email messages such as the message sent to users when a new account is created
- System managed lists such, for example “events email can be associated with”
Users supplied translations include:
- User managed lists such as study titles, business units, job functions etc. and all the custom lists
- Custom texts used in the Career Centre
- View names, titles and field names. Custom field names
- User managed email templates
- Workflow names, statuses and outcomes
- Activity types and fields
The platform has its own mechanism to know what language to display. In the back office, the platform looks for the
users preference and attempts to display the platform using the following rules:
- If the user has chosen Use browser settings, the platform will decide what language to display on the basis of the browser being used
- If the user has selected a specific language, the platform will display the platform in the requested language
Please note that for system supplied content, translations will always be available as updating the translations is part of the product release cycle. For user supplied content (pick list items, field names, etc.), the platform will attempt to display the information in the requested language and failing that will use the language defined in Company preferences in the System language field.
The field System language is not changeable after the account has been created and determines what the fall back language is in case translations of user content for a requested language are missing. Consider this example:
- a company is created with a System language of French
- the administrator creates a new field called la couleur des cheveux with two possible values: rouge and brun
- the system administrator then translated these items into English
- A user that sets their personal preference to using English will be shown the fields in English. However, a user that sets their personal preference to German will be shown the fields in French even though the user interface of the platform will be displayed in German
The field System language has another important impact. When administrators data enter information that is translatable, the platform considers they are data entering in the System language. This is displayed at the top of the user interface whenever a translatable item is being data entered. This is also the reason why it is not possible to change the System language after an account has been created: doing so would create a situation where the platform could display blank translations if a translation for the language requested by the user has not been supplied.
The front office Career Centre displays localized versions of content using a similar algorithm with a few important differences. When a new user navigates to any page in the Career Centre, the users browser language is determined and the following choice is made:
- If the Career Centre has been configured to display in the users language then this will be done. If a particular translation is missing, then the content in the Default frontend language for that front office will be displayed
- If the Career Centre has not been configured to support that language, then the content will be displayed in the Default frontend language
If the change language drop down list is being displayed the user can force the language to one of the languages configured for the Career Centre.
Whereas the back office platform will allow users to choose any of the languages supported by the platform, additional languages for Career Centres must be purchased separately.