Localization feature allows you to run your processes in other languages. In emakin every started workflow instance has an a culture identifier that specifies the language of a workflow instance. It set from sets as a preference of the initiator user when a an instance has been started, and cannot be changed later.
Instance culture specifies the language of displayed labels in forms but it does not change cultural information like number formats or date formats. This kind of formatting respects to the active user preferences.
In emakin, designed process language is not important, you can use any language to design. After a design is completed, or an a change is applied, you can open the localization editor from process a designer.
After a localization editor is opened you can add any other languages with "Add New" button and select language to localize the process.
Each added language has an 2 letter identifier of language. List of language identifier can be found at List of ISO 639-1 codes
After a language is added, you can click to "Details" button to edit localization texts. Emakin will be scan your process processes and list of texts to localize. Non localized texts will be marked as red but it's not mandatory. If do not localize original string is used.
Scriptingif they're mandatory, if not original string will be used.
After localization is completed, depending on the active user language, preference process will be displayed and run in localized language.
Accessing from Scripting Environment
In some cases you may need access to the localization texts in a scripting environment. For example, updating task instruction dynamically with localized equivalent.
Localization entries are stored in $Localization object and accessed in following format:
| Code Block | ||
|---|---|---|
| ||
$Localization.<Group>.<Source Text> |
Please see $Localization section for more details.