You are here: Reference > Tools, accelerators, and wizards > Rules Inspector tools > Localizing forms and reports with the Field Value Inspector

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.

Preparation

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.

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.
Select Switch Work Pool > work pool name from the Application menu to establish the appropriate work pool.
Select Designer Studio> User Interface > Tools > Locale Settings. change your own locale to the value that represents the target language. See About the Set Locale tool.
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.

Icons and their meaning

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:

— 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.

Working with the Field Value Manager window

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 user form or other portal element with updated translation values and icons.

Field	Description
Field value	Identifies the three key parts of the field value rule (which may not yet exist). Click the magnifying glass icon to open the field value rule, if you need to see the rule form.
Base Language Translation	Presents the original text value on the harness, section, or flow action form in the application RuleSet.
Current Translation for locale	Enter or revise this text to create an appropriate localized value.
Context	Select a class to become Applies To value — first key part — of the field value rule.

Testing in the WorkManager portal

As a best practice, test a localized application in a setting governed by the portal rule of the application, not the Designer Studio. To enable such testing:

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.
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).
Ensure that the users testing the localization have access, through access groups, to the RuleSet versions containing the localized field values.
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.
When testing and policing is complete, back out the changes you made in steps 1 and 2.

Notes

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 item history
pyInstructions — Instructions in assignments, visible on worklist display
pyMessageLabel — Error message text
pyStatusLabel — Work object status values
pyStatusWork — Work object status values

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

About Field Value rules
About the Localization wizard
Localization — Concepts and terms

About the Rules Inspector tool

Open topic with navigation

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