Localizing forms

If your organization supports multiple languages, you can make forms available in multiple languages so users can work with forms in their own languages. You localize a form by exporting it and then creating a translated properties file for each locale that you want to support.

When you export a form, Unica Plan creates a compressed file that contains a form properties file for your locale. You can create a copy of the properties file for each locale your organization supports. Then, you can translate the group names, field names, descriptions, and help tips into the appropriate language for each locale. If the form uses lookup tables and the database contains localized versions of the lookup tables, you can edit the properties file to reference the correct lookup tables.

Properties file names

Properties file names must be in the following format.


where <form_name> is the name of the form, and <locale> is a locale code. The following locale codes are recognized.

Code Language
de_DE German
en_GB English (Great Britain)
en_US English (United States)
es_ES Spanish
fr_FR French
it_IT Italian
ja_JP Japanese
ko_KR Korean
pt_BR Portuguese
ru_RU Russian
zh_CN Simplified Chinese
zh_TW Traditional Chinese

Example properties file

columngroup.group1.description=first group
columngroup.offer.description=second group
columngroup.offer2.description=third group
column.business_unit_id.label=Business Unit
column.business_unit_id.message= Business Unit is a mandatory field
column.business_unit_id.helptip= Business Unit is used for
column.init_type_id.label= Initiative Type
column.init_type_id.message= Initiative Type is a mandatory field
column.offer_codes.label=Offer Code(s)
column.effective_date.label=Effective Date
column.drop_date.label=Drop Date
tvccolumngroup.group1.description=group1 description
tvccolumngroup.group1.helptip=group1 helptip
tvccolumn.tvc_not_used_ref_1.label=Single Marketing Object

Localizing forms by editing

You can also localize forms by having users in the locale open the form and manually edit the names and descriptions. When the user saves the form, Unica Plan saves the translations that the user entered. Then, the translated form displays for other users with that default locale. However, this process takes more time and is efficient only when the number of forms and the number of supported locales are small.

How Unica Plan determines the properties file to use

When a user displays a form, Unica Plan uses the properties file for the first locale in this list for which a properties file exists.

  1. User's locale
  2. Default locale for the system
  3. Locale in which the form was created