Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Creating a field value

Suggest edit
Updated on April 5, 2022

Create field a value to support groups of localizable labels.

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.

  1. In the header of Dev Studio, click CreateData ModelField Value

  2. In the Label field, enter a description for the field value.

  3. In the Field Name field, enter the name of a single-value property.

  4. If this field value supports language localization by using a language-specific ruleset, enter language-specific descriptive text for the value.

    For example, the standard field value Work-.pyRootCause.Facilities makes a value "Facilities" available as a selection choice for the value of the Work-.pyRootCause property. To present a French-language version of facilities, copy this standard rule into a language-specific RuleSet (ending in _FR to match a locale) and enter "Équipements" as the Localized Label.

    1. Click View additional configuration options.

    2. In the Translated value field, enter a literal constant that is an acceptable value for the Field Name property, using only letters, numbers, single spaces, and a hyphen. The value might appear in a selection list or other aspects of the application user interface, so choose text that is meaningful to your user community. Enter no more than 64 characters. If the class and Field Name key parts together identify a Single Value property that has a Maximum Length value less than 64, that limit applies.

  5. Click Create and open.

  6. Click Save.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us