Localization

Localization feature allows you to run your processes in other languages. In emakin every started workflow instance has a culture identifier that specifies the language of a workflow instance. It sets as a preference of the initiator when 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 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 a change is applied, you can open the localization editor from 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.

After a language is added, you can click "Details" button to edit localization texts. Emakin will scan your processes and list of texts to localize. Non localized texts will be marked as red if 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 the localization texts in a scripting environment. For example, updating task instruction dynamically with localized equivalent.

Please see $Localization section for more details.