Exploring Fields

You define the presentation of your application's user interface (UI) by configuring out-of-the-box fields and field settings. This prescribed approach to defining the fields and field settings simplifies user interface development by auto-generating Views based on the data structure. This allows the application development team to focus on configuring the business logic instead of styling.

For example, in a process for hiring new employees, you can create fields that correspond with the personal details of a candidate, such as a name, surname, and an interview date. You define the respective field types as two Text fields and a Date field. When you display the fields in an editable View, the system renders them as two text boxes and a calendar control. You can also set the Required status for each field to Always, ensuring the new employee provides the necessary information.

Pega Platform includes fields with predefined configurations that you can integrate into Views. These fields help you maintain consistency and reduce development time while you customize application logic. The basic field settings that are shared by most fields and appear in different contexts throughout your UI configuration menus include:

• Field Type
• Label settings
• Editing options
• Additional text
• Form messages, such as warnings
• Field behavior, including required status

The following image displays the field settings associated with a field named First Name:

The following topic contains information that is important for your understanding of common field settings and controls and for passing the certification exam: Configuring common field settings.

Define Primary Fields to automatically add the most relevant fields to your Cases and reduce the amount of UI configuration that is necessary. Primary fields also ensure users are provided with the most relevant Case information to support faster Case resolution.

You can designate fields as Primary Fields in your Data Objects and Case Type Data Models to streamline UI configuration. The system automatically adds these designated Primary fields to the Create, Edit, Details, and List Views, so you do not need to add them to each View manually. This approach ensures consistent access to important information throughout the Case Lifecycle. The Case Type data model automatically designates the Label and Description fields as primary by default.

For example, in a Case Type that captures customer information, you define the Name, Email, and Address fields as Primary Fields. Then, you access the Address Data Object and define its Primary Fields, such as Street, City, and Country. The system then automatically adds the Primary fields to the Create View, as shown in the following figure:

When authoring Views, you can group individual fields in clusters to visually present related data together. Field groups help you organize your fields under a single header, and provide you with tools to add instructions or temporarily hide the fields in collapsible sections.

For example, in a product return application in the Product Details View, you can create a field group called Select product that groups together the fields Product, Cost (Product), and Proof, as seen in the following image:

At run time, the system displays fields in a field group with a vertical line on the left. This visual cue helps users distinguish grouped fields from standalone fields. The following image shows a sample field group called Main info: