Fields and Field Types
Fields model single instances of data that is needed to resolve a Case. Each field consists of a name and a Field Type. The Field Type defines the format that information must be in to ensure its accuracy. Fields are used to define the attributes of a data object, and single-value fields can also be added directly to a form in a Case Type to gather information from a user.
As a Pega Business Architect, identifying the fields and Field Types associated with the information required for Case resolution is integral to the creation of the application's Data Model.
In this topic, you examine fields and the available Field Types in Pega Platform™.
Fields are named, reusable UI components that collect, display, and store single pieces of information that are required when processing a Case. Fields can be added directly to a Case Type to capture information input by a user that is important to the resolution of a Case, or fields can be used to describe a data object.
In the following figure, the Customer data object consists of fields including Account ID, Coverage level, Email address, Enrollment, First Name, Full Name, Globally unique ID (which is automatically generated by Pega Platform™), and Last Name:
Note: Account ID is designated as a Primary Field. You designate Primary Fields to automatically add the most relevant fields to certain Case Views, reducing the amount of UI configuration that is necessary. Pega Platform automatically generates a Primary Fields View and adds it to the Create, Edit, and Details Views. For the relevant training materials, see Designate Primary Fields.
When you create a field, you also assign a Field Type. The Field Type determines the format of the data that can be entered into the field, and, as a result, the type of information that is stored in the system. Field Types also determine the type of control that is automatically paired with the field in the user interface. 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:
When creating a field, Pega Platform predicts the Field Type. By default, the Field Type is Text (single line). In the example below, when you name the field Arrival date, the system detects date in the name and sets the Field Type to Date only.
Tip: Verify your field type is correct before clicking Submit.
Pega Platform includes a variety of Field Types for use in an application.
Pega Field Types
The following table shows a list of simple Field Types available in Pega and the information that each type stores.
|Type of Data
|Any single line of text.
|A large text box that accepts multiple lines of text.
|Allows users to select a checkbox to indicate one of two possible responses.
|Currency symbols and values 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.
|Calendar date with a localized format.
|Numbers with a fractional component. Use this Field Type when fractions are needed.
|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.
|Positive and negative whole numbers, including the value zero (0).
|Positive and negative decimal numbers entered as a decimal and displayed as a percentage. For example, .5 displays as 50%.
|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.
|A list of predefined values.
|UTC (Coordinated Universal Time) value normalized to Greenwich Mean Time (GMT).
|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.
|Documents or files.
|Address input or automatic geolocation.
|Displays the results of a Prediction. Predictions contain fields, which you can configure on the UX tab as standard text and decimal fields. If you have access to Prediction Studio, the Prediction field displays a link to the source Prediction.
|You can use this field to display the probability of missing a service-level-agreement.
|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.
Enter or select a user ID that exists in the system. The drop-down list or search field shows a list of every operator mapped to the current application rule.
Note: For additional information on the concept of fields and Field Types as they relate to the Data Model, see Configuring fields associated with Case and Data Objects.
Check your knowledge with the following interaction: