About the Localization wizard |
Use the Localization wizard to make an application available in one or more additional languages. The localization process overrides text in user-visible field value rules that appear in application elements such as user forms and portal displays. The wizard automates many of the steps necessary to create language-specific rulesets.
The Localization wizard is designed to efficiently and automatically identify relevant user interface rules. However, there may be rules that the wizard does not detect caused by unique application configurations. Complex applications will most likely require some manual translations.
Before using the Localization wizard, do the following:
The Localization wizard provides three options:
Click the help button on any form for help about that form.
This wizard creates a work item with prefix pxAP-
. To find open and resolved wizard work items, select > Application > Tools > All Wizards.
These are the basic steps you perform in the wizard when you translate to a new language or verify a translated application.
Step 1: Select languages — Select one or more languages to which you want to translate your application. A translation package will be exported for each of these languages.
Step 2: Select application rulesets — Select one or more unlocked application rulesets and versions you want to include in the translation package. If you have not selected any unlocked rulesets, an error will display. Select Modify Selection to return to the step and select an unlocked ruleset. Otherwise, select Proceed Anyways to export the records for translation.
Step 3: Enable Records — This step allows you to enable records for translations in unlocked ruleset versions only and is recommended for first-time translations. If you did not select an unlocked ruleset in Step 2, this option is unavailable and you can proceed to the next step.
Step 4: Export Translations — The wizard creates a ZIP translation package for each language. The package includes an XML file containing the text strings and other files the translator will need. This step allows you to save the package to a local directory so that you can send it out for translation.
Creating a wizard work item: When you select the Translate to New Language option, The Step 1: Select languages form opens and a wizard work item with the prefix of PXAP
is created.
You can also create a new wizard object when you are in the Wizards in progress list (see next topic) by clicking New, which opens the Step 1 wizard form.
Opening a wizard object that is in progress: Use the Translations in Progress option to display the Wizards in progress worklist. Clicking an item opens the step at which the Localization wizard exited. The list has four columns. The fourth column (last one on the right) indicates the step at which the Localization wizard exited. When you click an item with Import
status, a three-step Localization wizard opens that you use to import the translated package into your system. If you exported multiple translation packages from one wizard object, each package appears as a separate Import item in the list.
Exiting the wizard — You can exit the wizard in any step by clicking Cancel. All your entries up to that point are retained. Use the Translation in Progress option to reopen the wizard.
Rule types that are localized include the following:
Rule Type |
Field |
Notes |
Class (for work types) |
Short Description |
Visible on the portal |
Flow action |
Short Description |
Basis of user selection of the flow action |
Flow action Harness Section |
Caption (button panel, Layout tab) |
Visible on user form |
Flow action Harness Section |
Value (Field panel, |
Visible on user form |
Harness |
Title (Layout panel, |
Visible on user form |
List view |
Field Label
(Display Fields tab) |
Visible on report display |
Summary view |
Group By Caption (Content tab) Caption and Title |
Visible on report display |
Message |
Message |
Localization is needed only for Rule-Message rules presented to users, such as through the Page-Set-Messages method in an activity, or a validation rule. |
The properties listed below are included in the localization process. Some field value rules may already be defined in a language pack for the locale.
Applies To |
Name |
|
@baseclass |
pyActionPrompt |
A sentence corresponding to a longer form of a pyActionLabel, as explanation that be presented as a ToolTip. For example, the pyActionLabel with English text |
@baseclass |
pyButtonLabel |
Generally an imperative verb that conveys a command from the user to the application, such as appears on buttons or links to be clicked. Examples of the English forms are Save, Cancel, Submit, Next, and OK. For example, the pyButtonLabel with English text |
@baseclass |
pyCaption |
An imperative verb or verb plus object that is a request to the user. For example: Select a value, Click to close. May also be single word noun or noun phrase, such as Amount, Received, Due, Limit. Typically used for localized versions of field labels in sections and harnesses, and column headings in reports. For example, the pyButtonLabel with English text |
@baseclass |
pyInstructions |
Application-specific instructions to a user regarding a human task in a flow. These may appear on a worklist. Typically these start with an imperative verb and contain no more than six words. Examples: Verify applicant salary. Check customer credit limit. Confirm receipt of goods. Review mortgage application. |
@baseclass | pyLabel |
Short Descriptions for the work types (concrete class rules derived from Work-) in the application. For example, the PegaSample application includes the work type PegaSample-CustomerRequest, with Short Description |
@baseclass | pyMessageLabel |
You can localize alert messages contained in JavaScripts. For examples, these field values convert messages to the user conveying errors, progress, success, or needed action. Also includes the Where-am-I? form. Examples: Enter a value; field may not be blank. Submitting... Save failed. Contact your administrator. For example, the pyMessageLabel with English text |
@baseclass | pyStatusLabel |
Localized versions of work item status values, such as For example, the pyStatusLabel with English text |
To create your own language pack that includes standard Pega 7 field values, do the following:
Language-specific ruleset Locale |
|
Internationalization and Localization — Concepts and terms
Rules Inspector tool — Localizing forms with the Field Value Inspector About Field Value rules |