MODULE 4 · User Interface

Forms, fields and field groups

Original learning guide · Pega ’25 path · Content v1.0.0

Learning objectives

Understand the concept

A form should follow the way a user thinks about a task. Group related fields and give each field a meaningful label. Required, read-only and editable settings have different purposes and should match the workflow state.

Constellation organizes user experiences around views, fields, templates and supported patterns. Build views from the data and tasks a persona needs. Use conditional behavior for relevant information, and provide clear validation messages close to the affected field. Accessibility includes meaningful labels, keyboard operation and errors that do not rely on color alone.

Group contact and income information separately. Review the reading and tab order, then verify which fields become read-only after submission.

IntakeAssessmentDecisionResolution

A configuration example

Create an applicant-details view with contact and income field groups. Display employer information only when employment status makes it relevant. Explain validation in user language, such as “Enter an amount greater than zero.”

Application: Loan Origination
Case type: Loan Request
Learning focus: Forms, fields and field groups

Given: a known applicant and a documented policy
When: the configured step or rule executes
Then: compare actual data and routing with the expected outcome

Conceptual configuration plan, not an importable Pega rule. Labels and tools vary by release. Use the official mission environment to inspect current screens.

Try it yourself

Group contact and income information separately. Review the reading and tab order, then verify which fields become read-only after submission.

Design a compact intake form. Tab through the fields in a logical order. Check required fields and conditional sections. Test the same task at a mobile width and with longer translated labels.

For this lesson, focus your notes on forms, fields and field groups. Record the inputs, configuration choice, observed result and one alternative that you rejected.

Common mistake

Hiding a field in the interface does not enforce authorization. Sensitive data must also be protected by server-side access rules.

Knowledge check

Should conditional visibility be used as the only control for sensitive information?

Check your understanding

No. Visibility controls presentation. Authorization controls whether a user is allowed to access data or perform an action.

Go deeper with official resources

Pega Academy System Architect mission
Official ’25 certification objectives