Multilingual environment

In a multilingual environment, we recommend selecting English as the Alvao system language, which usually serves as a common communication language across all teams. Then define all configuration items, such as object type names, in English. You can further translate some items into other languages.

Translation steps

1. In the Alvao WebApp, select the Administration - Settings - Languages.

2. On the Languages page, select Download translation workbook and enter the name of the file to which the translation documents should be saved. The saved file is in XML format.

3. Open the file in Microsoft Excel.

4. Each row of the table corresponds to one item to be translated. The value column contains the original text in English (or in the language of the Alvao system). Add its translations in the columns for the selected preferred languages.

   tip

   The fields where translations need to be added are underlined. The required action is also described in the columns To Do for each preferred language. The columns may contain the following values:

   • translate - the text must be translated initially.
   • update translation - the existing translation needs to be updated because the original text in the value column has been changed since the last translation.
   • - (dash) - the translation already exists and is up to date.

5. Once the translation is complete in Microsoft Excel, save the file again in XML format.

6. In the Alvao WebApp again select the Administration - Settings - Languages and use the Upload translations command to upload the file.

tip

If different translators will be translating each language, send each translator a table with only the languages they are translating into. Remove the other languages from the table before sending it to the translator. When you import the table into Alvao, only the translations into the languages that are included in the file will be loaded. Do not remove the first 4 columns from the file that identify the text to be translated.

note

The type of item to be translated (e.g. service name, SLA name, etc.) can be determined by the values in the Table and Attribute columns, which contain the name of the database table and the column in which the text is stored.

warning

Table view settings usually contain filters that depend on the user's preferred language. By adding translations, users may find that the filters no longer work and have to set them up again in their preferred language.

What can be translated

Following configuration items can be translated.

• Asset Management
  • Object type
  • Property name
• Service Desk

  • Service

    • Service name
    • Service description
    • Service keywords

  • SLA

    • SLA name
    • SLA description

  • Process

    • Process name
    • Ticket status name
    • Ticket status description
    • Instructions for solvers
    • Notification for approvers template
    • Ticket status change notification for requesters template

  • Priority

    • Priority name (high, medium, ...)

  • Ticket relationships

    • Link type name

  • Ticket custom fields

    • Field name

    • Field description

    • Values in the list of values for fields of type int and nvarchar

      note

      Translations of custom field value lists are disabled by default. You can enable them on each custom field separately by enabling the Enable translation option.

  • Custom notifications

    • Subject and text of notification