Translating workflows
You can translate workflows in any of the supported languages by adding custom strings for those languages and leveraging the workflows Java API translation bean. This enables users with a language preference that matches the translation to see the workflow tasks that are assigned to them in their selected language.
To use custom strings, you must prepare your workflow for translations:
Item | Workflow Designer attribute | Custom string example |
---|---|---|
Task name* |
|
user.task1.name=The translated name of the task |
Task description* |
|
user.task1.description=The translated description of the task |
Form fields |
|
text.area.label=The translated label of the field |
Form buttons |
|
button.name=The translated name of the button |
Email task |
Emails are translated into the preferred language of the user who completes the task, not the recipient. |
email.body=The translated body of the email |
Custom error message |
|
error.description=The translated description of the error |
* Start forms display the process name instead of the task name and description. You cannot translate the process name.
If you are not yet using the Workflow Designer, you can achieve similar results with the Eclipse plug-in by changing the expression format to ${translation.getMessage('translation.key')}
.