More about Field Value rules

An example: values of pyStatusWork

Create field value rules 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 rule instance 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 value rules define one subset of allowable values for this status, using the three key parts:

Class	Field Name	Field Value
Work-	pyStatusWork	New
Work--	pyStatusWork	Open
Work-	pyStatusWork	Pending
Work-	pyStatusWork	Resolved-Completed
Work-	pyStatusWork	Resolved-Duplicate
Work-	pyStatusWork	Resolved-Rejected

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:

Class	Field Name	Field Value
Work-	pyStatusWork	New-Scanned
Work-	pyStatusWork	New-PhoneTranscription
Work-	pyStatusWork	Pending-Customer
Work-	pyStatusWork	Pending-Supplier
Work-	pyStatusWork	Resolved-Withdrawn

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

Examining field values with the Rules Inspector tool

To aid in localizing work object forms, you can easily identify and update field value rules referenced in a harness, section, or flow action rule. Select Run > Rules Inspector > Field Value Rules to enable or disable this capability. See Rules Inspector tool — Localizing with the Field Value Inspector.

Functions for localization

These standard rules support localization based on field value rules: (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
• HTML Property rule GetLocalizedValue

	locale
	Property form — Completing the General tab — Tables Internationalization and Localization — Concepts and terms
	Atlas — Standard Field Values

About Field Value rules