More about Field Values

Example of pyStatusWork values

Create field values to defines an acceptable value for a certain subset that you reference in the Subset Name field of the General tab on the Property form.

A field value has three key parts: a class name, a field name, and a field value. Two or more field value instances where the first two key parts are identical are known as a subset. This is the unit of property validation.

For example, the class Work- contains a standard property named pyStatusWork of mode Single Value. Standard field values define one subset of allowable values for this status, using the three key parts:

These six instance records form one subset. You can create more field value instances using the same class and field name, adding to this subset. You can create more instances with the same class but a different name, creating another subset.

Your application RuleSet can include additional status values, such as the following examples:

The word Resolved as the first portion of this property value is significant. If you create additional field values to define other resolved status values, start the value with this word.

Examining field values with the Field Value Inspector

To aid in localizing user forms, you can easily identify and update field values referenced in a harness, section, or flow action. Select Live UI and then select the field. The field value appear in the Localize tabe of the Live UI tool See Localizing forms with the Field Value inspector tool.

Functions for localization

These standard rules support localization based on field values: (In most cases, automatically generated facilities call these functions in the appropriate places; you do not need to reference them explicitly.)

• Activity @baseclass.GetLocalizedTextForString
• Function getLocalizedValue() in the PegaRULES String library
• Function getLocalizedText() in the PegaRULES Utility library
• Control rule GetLocalizedValue

About Field Values

Open topic with navigation