Localized rules
Translation packages contain a localization-ready copy of the text that appears in customer-facing UI components, such as buttons and sections. The translation wizard sources the text from the relevant application rules without changing their properties or relations. This approach separates the language of the application from its architecture, which helps with localization of the product into many languages.
Localization ruleset
When you import a localized translation package, the localization wizard saves the translation in a localized ruleset. The wizard creates a target ruleset, or if the ruleset already exists, imports the translation to the existing localized ruleset. A language-specific ruleset is a variant of the application ruleset, whose name consists of an application ruleset name followed by a single underscore and a locale code. For example, for the application defined in the ALPHA ruleset, ALPHA_it identifies the ruleset as an Italian localization.
You can create and edit language-specific rulesets manually. If you want your application to use dialects, you can manually add sub-rulesets for the dialects in the parent language ruleset. For example, the ALPHA ruleset can contain an ALPHA_PT parent that holds ALPHA_PT_br for Brazilian Portuguese and ALPHA_PT_pt for European Portuguese.
Language-specific rulesets should contain only field value rules that represent words or phrases from customer-facing UI components. Consequently, the ruleset does not need to include rules that determine the functions of the application, such as decision or flow rules.
Localized rules
The following table lists the rule types and the fields in the rules that the localization wizard includes in the translation package.
| Rule type | Field | Notes |
| Class (for work types) | Short description | Visible in the portal. |
| Correspondence | Correspondence | The TextToTranslate.xml file does not include
correspondence rules. Each correspondence rule generates a separate
Translation.html file. To localize a correspondence rule, you
must create a separate correspondence rule for the target language, and add the
translated text manually to the rule. |
| Currency | Currency | The application converts currency symbols, but does not automatically convert currencies according to the exchange rate. |
| Field value | Static text in the UI | Visible on the user form. The wizard sources field values automatically for translation. For more information, see Localized rules. |
| Flow action |
| Visible on the user form. |
| Harness |
| Visible on the user form. |
| Message | Message | Localization is needed only for Rule-Message rules that are displayed to users, for example by the Page-Set-Messages method in an activity or a validation rule. |
| Report definition |
| Visible in the report display. |
| Section |
| Visible on the user form. |
Previous topic Preparing your application for translation Next topic Localized rule types