Automation Server features a Work portal which is presented in different languages.
This means that all the menus, options and labels in general are automatically available as an out-of-the-box feature for the following languages:
Note that Bizagi supports as well other languages not listed above.
For those languages not mentioned above, translations and adjustments are required on your side, though being completely supported (i.e you will need to input the translations for the menus, options and labels used in Bizagi Work portal).
In case you want to overwrite and customize such menus, options and labels in general, for an already-supported language, you may do so too by following the same approach and steps as for languages not supported out-of-the-box.
Enabling more than one language (localization)
Multi-language support in Bizagi considers also the possibility of having separate profiles for users in the different geographical regions (localization).
Often in large enterprises, i.e those having branch offices in different countries, you could have multiple users spread all around the globe while using a same given set of processes.
In such scenarios, though each user views the Work portal in a given language, in order for them to actually read processes information, business information and organizational definitions in that given language, it would be up to your implementation to input the translations for the names of specific objects of your project (i.e, defining the name of your processes, name of user interface fields, values or parameter entity values, etc for each enabled language).
The following images show how Bizagi Work portal would localize processes as well, for two different users, each working in his/her preferred language.
The sample Inbox at the top being for an English-speaking user while the one at the bottom for a Spanish-speaking user:
The first step for multi-language support is to enable the language you want your Bizagi Work portal in.
If you will be using more than one language as a possibility for your end users, then you would need to enable each of those languages.
Ideally, this is a task done in the development environment when implementing your processes and planning on your project's language support (recommended in order to carry out all due and rigorous user acceptance tests).
However you may also do this in a live production environment, given that such options are presented in Bizagi Work portal, as shown below:
1. Log in to the Work Portal with an account having admin rights.
Then go to the Admin menu, open the Customization category and open the Language settings options.
Move to the Manage languages tab and check the Enabled box(es) corresponding to the language(s) you want to support.
When finished click Save changes.
This same option is also presented alternatively in Bizagi Studio, as described at Enable languages from Bizagi Studio.
Next steps when applicable, are:
•Include translations for Work portal labels only if you chose a language which is not shipped in with Bizagi.
Or similarly, modify and customize the built-in translations for an out-of-the-box language if desired.
To learn how to do this for the Work portal labels, refer to: Including or modifying translations for the Work Portal.
•Localize object names and labels of your own specific implementation, only if you will be using more than one language for your end users.
To learn how to do this, refer to Localizing your processes and their objects.
•Bizagi uses the ISO 639-1 standard to name languages.
This standard uses four letters: the first two letters identify the family language, the second ones identify the country. For example: en-us (American English), en-gb (British English).
If no localization has been defined for a specific language (i.e en-gb), Bizagi will use the localization defined for the parent family language (i.e en).
Complete details on this standard specification relates to the Part 1(ISO 639-1:2002) at https://www.iso.org/iso-639-language-codes.html.
•If you enable a language that requires Unicode characters, you need to make sure your database supports Unicode.
For instance when using Oracle, you have to make sure that the Oracle database uses an Unicode-compliant character set.
•All configuration regarding enabling languages, and inputting or editing translations for any languages necessary is available from either Bizagi Studio or the Work portal administration options.
It is recommended to define language settings and localization in the development environment (though Work portal options can be used), in order to carry out adequate user-acceptance tests before going live.