Skip to main content


Pega Platform™ applications collect and process important case data. By defining the fields that are displayed at runtime, you can collect information from users or present case information for review. For example, when providing search criteria to book accommodations, users enter each search criteria in a separate field. The criteria return results that are displayed as read-only information.

Each field is a named, reusable UI component. Each field stores a unique value that is associated with a case. The combination of the field name and the stored value defines a data element in a case. For example, a field named Metro area and a value of Boston would make up one data element.

When you create a field, you also assign a field type. The field type identifies the type of information that is stored in the system. By assigning a field type, you ensure that users provide valid information in the field and that the system displays data in the correct format.

For example, a field named Metro area would be assigned a field type of Text and store the value Boston, as shown in the following Booking form.

Example: Booking field types

Check your knowledge with the following interaction:

Simple field types

In Pega Platform, you can assign a simple field type to a field. The following table shows a list of simple field types and the information each type stores.

Field Type Type of Data Field Example
Text (single-line) Any single line of text.
Text (paragraph) A large text box that accepts multiple lines of text.
Boolean Allows users to select a check box to indicate one of two possible responses.
Currency Currency symbols and value are stored based on the default currency type.
Date & time UTC (Coordinated Universal Time) value normalized to Greenwich Mean Time (GMT). Date automatically displays in a localized format.
Date only Calendar date with a localized format.
Decimal Numbers with a fractional component. Use this field type when fractions are needed.
Email Valid email format with an @ symbol. An email field is an action-oriented control, meaning the value stored in the field is displayed as a link. For an email, the link initiates users' default email application.
Integer Positive and negative whole numbers, including the value zero (0).
Percentage Positive and negative decimal numbers entered as a decimal and displayed as a percentage. For example, .5 displays as 50%.
Phone Digits display in a localized format. A phone field is an action-oriented control, meaning the value stored in the field displays as a link. For example, if users access the application on a mobile device, the phone number link initiates a phone call.
Picklist A list of predefined values.
Time only UTC (Coordinated Universal Time) value normalized to Greenwich Mean Time (GMT).
URL Web address. A URL field is an action-oriented control, meaning the value stored in the field displays as a link. For a URL, the link initiates the user's default browser and opens the target web page.
Address A region-specific address format. The UI displays the Country field as a dropdown list. Depending on that selection, the UI displays a set of country-specific fields.
Image of the Address field type.
User reference

Enter or select a user ID that exists in the system. The drop-down or search field shows a list of every operator mapped to the current application rule.

current user
Tip: An integer field stores only the value that begins at the first non-zero digit. For values that do not require arithmetic calculations, use a text field type.

Fancy field types

You can also add more complicated field types, such as fancy fields. Users can add an address, and the system responds by displaying a map. The system can also display controls to attach a document or display a field to enter or select an existing user ID. The following table shows a list of fancy field types and the information each type stores.

Field type Type of data Example
Attachment Documents or files.
attach resume
Location Address input or automatic geolocation.
location map


Primary fields

Primary fields are the fields that are the most relevant to a case type. Designate fields as primary fields from the case type data model or the data object. The case type data model automatically designates the Label and Description fields as primary by default.

Primary fields are automatically displayed on the Create, Edit, and Details views, which reduces the need for additional UI configuration.

Note: Primary fields are only available in the view-based Constellation architecture. For more information about primary fields, see Configuring primary fields.

Check your knowledge with the following interaction:

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice