← All articles
9 min read

Pega Constellation Patterns Explained: One Home Loan Form, Five Decisions

Pega & Enterprise PlatformsPegaConstellationFormsCalculated FieldForm Refresh

Pega Constellation Patterns Explained: One Home Loan Form, Five Decisions

A Constellation form works best when you name the need first and pick the pattern second. This post uses one home loan form with five requirements. It then compares the four ways to react to what a user types. It ends with how to break up a form that has grown too big.

The home loan scenario is invented. The patterns, settings and limits are real, and they come from the Pega Platform '26 documentation.

Why patterns, not buttons

In traditional Pega UI, a requirement often became a button with an Action Set behind it. Constellation has no Action Sets. Pega's documentation says actions are modelled in the Case Designer. Business rules sit in the models at the centre, and the UI follows from them.

So a requirement that once needed a button now needs a pattern in the model. The skill is knowing which pattern fits which need.

The basics, in one paragraph

Constellation has four view types: Full Page, Partial, List and Form. Full Page, Partial and List are read only. The Form is the one you edit. Inside a Form view, field groups hold fields, and each field has a type. In Constellation, the field type also sets the visual representation of the field, so choosing the type is a UI decision as much as a data one.

One form, five requirements

Picture the first screen of a Loan submission case, called Personal details. Five requirements land on it.

Pin Requirement Pattern
1 Find an existing customer, don't retype them Data reference, shown as Search and select
2 Pick a country, then show only its states Cascading dropdown
3 Make the simple fields quick to fill Field type, then Display as
4 Show the monthly repayment as they type Calculated field
5 When employment type changes, suggest the documents needed Form refresh condition

Pin 1: Find an existing customer

Customer is a data reference to the Customer data object. It is not embedded data. Pega describes a data reference as capturing records that the system sources from a data object. Embedded data stores and sources from inside the case instance.

For a single-record reference field, Pega '26 offers six Display as options: Combobox, Dropdown, Table, Simple table, Search and select, and Cards. Views built before '26 show Autocomplete where '26 shows Combobox.

Pega's own wording helps you choose:

  • Dropdown is useful where there is a limited number of choices.
  • Combobox is useful to sort through a large number of options.
  • Search and select is for complex search operations on large sets of data.

In the example app, Customer ID is a Combobox, which works for seven customers. At bank scale the same field becomes Search and select. The officer searches by first name, last name or full name, and picks one result.

To set it up, you choose the display field and the "Search for" categories. You then choose the search groups with their criteria fields, and the result columns. The data page must be queryable. Pega notes that non-queryable data pages are not displayed.

One limit matters. Reference fields do not support create, update or delete operations yet. So you cannot add a new customer from inside the field.

Pin 2: Cascading dropdowns

Country and state are two Picklists, and each one's options come from a data page. The state's data page takes the country as a parameter. Pick a country, and the state list follows. Pega's own forum guidance says that with the right data model, a form refresh is not needed for this.

One thing to test in your own app: what happens to a value already picked when the parent changes. We found no source that says either way, so this post does not claim one.

Pin 3: Pick the type, then the display

Choose the field type first, then the Display as option.

The list is Field type Display as
A few fixed values that belong to the case, such as marital status Picklist Radio buttons or Dropdown
A long list of fixed values Picklist Search box
Real records, a limited set Data reference Dropdown
Real records, a large set Data reference Combobox
Real records, found by several criteria Data reference Search and select

Pega's Picklist page offers radio buttons, drop-down lists and a search box, with Dropdown as the default. It gives no threshold for radio buttons versus a dropdown. "About five or fewer values for radio buttons" is our own rule of thumb, not Pega's.

Store a date as Date only, not as text. A date modelled as text cannot be linked to a calendar control manually. Date only gives a calendar picker.

Pin 4: The calculated field

Show the monthly repayment as the officer enters the amount, term and rate. That is a calculated field.

On the field, open Advanced and tick "This is a calculated field (read-only)". Then set an expression or a decision table. All types of calculated fields support expressions.

The result is read only. So don't use a calculated field when the user must be able to override the value. Keep the expression light.

Pin 5: The form refresh

The officer changes employment type from Salaried to Self-employed. The documents needed should now suggest the last two tax returns.

On the flow action, a form refresh condition says: when this property changes, run this data transform. Three facts to keep in mind:

  • It runs on the server.
  • Its data transform is intended to provide suggested values for dependent fields only. To set a value unconditionally, use post-processing on the flow action.
  • Its message does not prevent the user from submitting incorrect data. Use a validate rule for that.

Pega also notes that only the property change event is supported, and that Declare Expression updates do not trigger a refresh.

Which one, when?

Four patterns react to what the user does. They are not interchangeable.

Need on the form Pattern Why Don't use it when
Show, hide or require a field, such as Customer ID only when "Are you an existing customer?" is ticked Custom condition Validated in the browser, with an instant response The condition needs data outside the view. A When rule runs on the server and triggers a refresh
A derived, read only value, such as the monthly repayment Calculated field Read only, worked out from an expression or decision table The user must be able to override it
One change should suggest values for dependent fields, such as employment type Form refresh condition Runs on the server and suggests values for dependent fields only You only want to show or hide a field, or you need to force a value
Stop bad data at submit, such as income below the minimum Validate rule A refresh message does not block submit You only want to hint at or default a value

Breaking up a big form

A thirty-field screen is a design problem. Pega's own guidance is to use fewer than ten fields for each form. Pega's design system also gives an order: try each option only if you've already tried the one before it.

The full order starts with Stages, Parallel process and Conditional fields. Four options apply inside a single stage.

Option Use when Home loan example
Field groups One task, one sitting, fewer than ten fields Applicant details
Multi-step form One user, one assignment, sequential. Avoid more than five to seven steps Create Loan submission, with Personal details first
Hierarchical form Complex but not sequential. Groups show as tabs. Never inside a multi-step form Not a fit for a sequential loan application
Separate steps A real handoff to another person or queue Documents, collected later from the applicant

A multi-step form breaks a single assignment into several focused screens, with a stepper and Next and Previous buttons. Pega also warns that too few fields on a screen means more clicks, so combine thin screens.

The home loan lands on a multi-step form, plus a separate documents step.

What is real and what is invented

The bank, the customers, the loan products and the thirty-field form are invented to tell the story. The patterns, the setting names, the limits and the quoted guidance are real. I read them from the Pega Platform '26 documentation in November 2026. Pega Academy and the design system pages carry no version. So the fewer-than-ten-fields advice is attributed to "Pega's own guidance". The form labels change between releases, so check them on your own environment.

Pega documentation: Configuring a single-record reference field, Configuring run-time presentation for a Flow Action, Conditional logic in Views, Creating a calculated field and Adding a Multi-Step form. Also the Pega design system Forms pattern.

Takeaway

Name the need. Pick the pattern. The form follows.

More explainers at ssmone.cloud.