About the Localization wizard |
PROJ-121 5.3 ZELEK 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 work object forms and portal displays. The wizard automates many of the steps necessary to create language-specific RuleSets.
How the localization process works
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:
Starting the Localization wizard
Click the help button () on any form for help about that form.
This wizard creates a work object with prefix pxAP-
.
To find open and resolved wizard work objects, select > Application > Tools > All Wizards.BYRNB 2/23/10
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 Application RuleSets — Select one or more unlocked application RuleSets and versions you want to include in the translation package. Unless you choose otherwise, the rules in these applications are verified in step 2.
Step 2: Verify Localization Is On — The wizard verifies that the rules are enabled to allow localization and can be saved during validation. It selects the Localize? option in the rule forms for sections, flow actions, harnesses, list views, and summary views if necessary.
Step 3: Manual Tasks — The wizard lists rules that require corrections or updates so that they can be localized. The wizard form provides links to the rule forms and to Help topics for tips on how to correct the issues. You make the corrections or updates as necessary.
Step 4: 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 5: Check for Language Packs — Indicate whether you will acquire a Pegasystems language pack, which provide translated strings that are used in the standard Pega RuleSet user interface rules. This step appears only if you have chosen a language in Step 4 for which a Pegasystems language pack is not in your Process Commander system.
Step 6: Set Options — Indicate whether you want to include fields that have already been translated in your ZIP translation package file. Doing so allows translators to review phrases that were used earlier and help the translators maintain consistency. Also specify whether you want to include base field values from RuleSets in addition to those you selected in Step 1.
Step 7: Export Translations — The wizard creates a ZIP translation package for each language. The package includes an Excel spreadsheet 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.
Step 8: Import Translations — Upload and import to your system the ZIP file containing the translated fields. The Localization wizard takes you through the process in three steps:
Creating a wizard work object: When you select the
Translate to a New Language option, The Step 1:
Select Application RuleSets form opens and a wizard work
object 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
List New 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 have 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 on the menu bar. All your entries up to that point are retained. Use the List New Translation in Progress option to reopen the wizard.
Resolving a wizard — You can withdraw and resolve a wizard item in any step by clicking Cancel.
Using the wizard in your localization project
The following work flow represent a typical implementation of the wizard in a localization project. Bear in mind that it is an iterative process. You may need to repeat steps to ensure that the RuleSets meet your site requirements.
In this example, an application was developed using RuleSet version 01-01-01. You want to create a localized version of the application.
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 work object form |
Flow action Harness Section |
Value (Field panel, |
Visible on work object form |
Harness |
Title (Layout panel, |
Visible on work object 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. You need not override the language pack rule if the value it provides in the Localized Label field is appropriate for your application and user community.
Applies To |
Name |
|
@baseclass |
pyActionPrompt |
A sentence corresponding to a longer form of a pyActionLabel, as explanation that be presented as a ToolTip.R-18938 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. R-18938 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. R-18938 May also be single word noun or noun phrase, such as Amount, Received, Due, Limit. Typically used for localized versions of field labels in section rules and harness rules, and column headings in reports.R-18938 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 |
Rule-HTML-Fragment LocalizedStrings 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 object status values, such as
For example, the pyStatusLabel with English
text |
To create your own language pack that includes standard Process Commander 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 |