You can create request forms as well as task forms (for a People activity) that support different languages. To do so, you create a new form, plus a default properties file and additional properties files for each language supported. The properties file contains externalized strings for schema-based keyIdentifiers. The steps to accomplish this support for requests are described below.
For details on task forms, see Providing Multilingual Support for Task Forms in the
Human Tasks
topics elsewhere in this help.
Create a new request form and a default properties file:
Accept the default name and location for the properties file, or select the dialog button next to Property File to name and store your file. Do not use an underscore in the name.
When you externalize strings, the following events occur:
Schema elements in the form are generated by identifier rather than by name to allow for runtime replacement of strings found in a properties file.
A new link is added within the form to indicate multilingual support:
The list of schema elements is added to the properties file as a key-value pair.
The properties file that you create is the default externalized strings file.
For each additional language you want to support, do the following:
Make a copy of the default properties file and paste it into the forms folder.
Name the copied file with the syntax described in
Naming Convention for a .properties File. Basically, you must use the exact same name for each file, followed by an underscore, followed by an ISO 639 Code for the Representation of Names of Languages.
Open the file in a text editor and replace the existing values with another language.
To test your properties, specify a language when you login to Process Central. For example: