The Translation functionality allows you to create a full multi-lingual solution for the user. You can provide or import translations for multiple languages for artifacts within the solution.

TotalAgility adheres to the Internationalization (i18n) and Localization (l10n) standards, which define the parameters for adapting computer software to different languages and regions.

Process details, such as activity names within a work queue are displayed extensively throughout solutions; therefore, process elements, such as activity name, SLA description, work types, page renditions and categories are available for translation. If the Enable multilingual processes setting (System > System settings > General) is not enabled, you can translate the process, but the process will only appear in the base language at runtime.

Forms provide the main user interface to your solution; therefore, each item, such as control text, radio buttons, text fields, check boxes, column headings, navigation text, entities, and table header that is visible to the end user is available for translation into one or more languages.

  • On Windows, the Microsoft Virtual keyboard is disabled when using a text box in password mode.

  • If upgrading a form from the previous version, manually save and release the form to make the Work queue and Job list column headings available for translation.

In TotalAgility, you can define the languages that your process supports for translating items so that you can serve target markets without language and regional restrictions. You can select from the list of languages supported by TotalAgility.

Note You can select up to 215 languages for translation.

When you add a language and provide translation, at runtime all the data appears in the correct language set for the browser either through browser settings or through the Language selector control. If translations are not available for the browser language then the elements are displayed in the base language. The Language selector control selections are based on the languages supported by the site. If translations are not available for the browser language then the elements are displayed in the base language.

You can also export and import languages:

  • Use APIs in the Job Service component to get or set the language of a particular job.

    • Use UpdateJobLanguage to pass in the job identifier and language code to set the language for the job.

    • Use GetJobLanguage to pass in the job identifier to return the language for the job.

  • Render any forms displayed in the language of the job by adding a Set Language from Job action.

    Add the action to a form and pass in the job ID. This sets the language of the form when it loads. The translation for the language must be available.

See also: