Rules Inspector tool
Localizing forms and reports with the Field Value Inspector

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 BYRNB 2/17/10Switch Work Pool > work pool name from the Application menu to establish the appropriate work pool.
3. Select BYRNB 2/17/10> 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. Select BYRNB 2/17/10> Open Portal > name to open a portal that application users use, where name is the name of a portal rule available in your own access group.

Select BYRNB 2/17/10 > Rules Inspector > Field Value Rules (or the keyboard shortcut CTRL+ALT+W) to turn on the field value inspector. Return to the portal for application users.

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

• — Field value in attribute exists
• — Field value in attribute does not exist
• — Field value in text exists
• — Field value in text does not exist

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.

Click any of the four icons to access its field value rule (if any). Complete the Field Value Manager window and click Save to create or revise a field value rule for the element.

After you complete this form for one or more elements, click the Refresh button () to redisplay the work object form or other portal element with updated translation values and icons.

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

1. Complete the steps described in the Preparation section above.
2. Select BYRNB 2/17/10 > Rules Inspector > Field Value Rules 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? checkbox (on the HTML tab) is selected, or resave the rule after selecting this check box.
4. Click the Run toolbar button (). 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.

As 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:

• pyActionLabel — Short description text for flow actions
• pyActionPrompt — Labels for input fields on flow actions
• pyButtonLabel — Labels on buttons and URLs
• pyCaption — Labels on field values
• pyConfirmationNote — Text on a Confirm harness form
• pyHistoryMemo — Text in work object history
• pyInstructions — Instructions in assignments, visible on worklist display
• pyMessageLabel — Error message text VAGUE
• pyStatusLabel — Work object status values REALLY?
• pyStatusWork — Work object status values

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