When building an application, you often need to use a list of allowed values for a specific property. If the list of allowed values is short, mostly static, and common, for all case types in the application, the list of allowed values may be defined in a local list on the property record.
If the list of allowed values is large, expected to change frequently, or may be specific for each case type, you can use a field value.
Field values provide an alternate method for defining allowed values for properties. Field values enable you to manage the list of allowed values separately from the property. Managing the allowed values separately from the property enables you to reuse a single property, and customize the allowed values based on the context of the property.
For example, in a Pega application, every case instance has a status, which changes as the case progresses through the case life cycle. The status of a case is set using the property named .pyStatusWork. The list of allowed values for setting .pyStatusWork is defined using field values.
You can add different field values for a single property in the same context, or in separate contexts using the Apply to: class setting for each value. You can also use rulesets to maintain different versions of each field value in each context.
|Applies To||Field Name||Field Value||Ruleset:Version|
In the table above, the Pega-provided property used to set the status of a case — .pyStatusWork — uses a common set of allowed values as defined in the Work- context. This common set of allowed values is available for all applications built on the Pega platform.
Additional custom values are defined for the HRApps application. These values are usable in the TGB-HRApps-Work-Candidate and the TGB-HRApps-Work-Onboarding contexts (case types).
Field values also support localization of words, phrases, and sentences that appear on portal displays, reports, and user forms.