Back Forward Rules Inspector
Localizing forms and reports with the Field Value inspector tool

Use the Field Value inspector tool to find, review, and update field value rules in a language-specific RuleSet that are associated with labels, captions, messages, ToolTips, and other text elements on user forms and portal displays.

Typically, use the Localization wizard first. Then use the Field Value Inspector tool to review results in the context of the application being localized. You can review, revise, or add field value rules to provide a more effective and more complete localization.

Before enabling this tool, complete these preparations. This tool can help you check, finalize, or maintain field value rules for localization — field values created in a language-specific RuleSet. Typically, these field values are created using the localization wizard. See About the Localization wizard.

  1. Review your profile to confirm that a language-specific RuleSet is included for the target language, for example Mortgage_ES for field value rules in Spanish that apply to the Mortgage RuleSet.
  2. Select Switch Work Pool > work pool name from the Application menu to establish the appropriate work pool.
  3. Select > User Interface > Tools > Locale Settings. change your own locale to the value that represents the target language. See About the Set Locale tool.
  4. The Designer Studio is never localized. In the Designer Studio header, open a portal that application users use, where name is the name of a portal rule available in your own access group.

On the Designer Studio Developer toolbar, select Inspector References > Field Values to turn on the Field Value inspector tool. Return to the portal for application users.

Each element can contain one or more of the following icons:

The first two icons (with a white A) refer to text that is not initially visible, such as a ToolTip. The second two icons (with a black A) refer to visible text, such as a field label or caption.

The two icons with a red slash indicate that no field value rule is found in the language-specific RuleSet; this result indicates that localization is incomplete. Click a globe icon to open or create a field value rule.

To review and modify localization of list view and summary value rules:

  1. Complete the steps described in the Preparation section above.
  2. Select Inspection Prefs > Field Values to start the Field Value inspector.
  3. In the Designer Studio, open a List View or Summary View form for a rule to be localized. Confirm that the Localize? check box (on the HTML tab) is selected, or resave the rule after selecting this check box.
  4. Click the Actions > Run. The resulting report may be empty; its contents are not significant.
  5. Click  Field Value Inventory at the top level of the report output.
  6. Each row of the resulting window has a text value (in the base language) and an icon. Click an icon to start the Field Value manager.
  7. Review, create, or modify language-specific values as appropriate with the Field Value manager. Click Save.

TipAs a best practice, perform final testing and polishing of a localized application in a setting governed by the portal rule of the application, not the Designer Studio. To enable such testing: OSMAE 5/8/07

  1. Update the WorkManager portal (or other portal rule used in the application) to reference the gadget Data-Gadget.FieldValueInspector, a standard HTML rule. For example, you can add that to the Narrow Column array on the Tabs tab of the Portal form.
  2. Update the Access of Role to Object rule for an access role available to the application users so that they are allowed to modify and delete field value rules. (In contrast, the standard Access of Role to Object rule named PegaRULES:WorkMgr4.Rule-Obj-FieldValue allows review, but not update, of field value rules).
  3. Ensure that the users testing the localization have access, through access groups, to the RuleSet versions containing the localized field values.
  4. Log in using the modified portal. At this point, you can test and refine field rules in the context of day-to-day use of the application.
  5. When testing and policing is complete, back out the changes you made in steps 1 and 2.

Applications commonly localize these elements:

The system-generated HTML includes calls to the PublicAPI Java function getLocalizedTextForString() to convert text.

Definitions language-specific RuleSet, locale, organization RuleSet
Related topics About Field Value rules
About the Localization wizard
Localization — Concepts and terms

Up About the Rules Inspector tool