Which of Constellation's four view types can actually change data, and where should that edit really live?

A BA wants spreadsheet-style editing: click a cell in the case list, type a new value, done. Your dev team is about to hack it into the List View.

1. Full Page View owns the shell, not the edit.

One Full Page View renders per Case or data object in a three-pane layout. It's read-only. It orchestrates the other views, it doesn't accept typed input itself.

2. Partial View packages data, not data entry.

Partial Views are read-only, fully configurable, and built to be dropped into other views: Details, Preview, and, when enabled, Confirmation. Good for summarising a record. Wrong tool for editing one.

3. List View displays records. It won't let you edit one inline.

List Views run off a data source and render as tables, timelines, or tile galleries, most commonly the open-cases and history lists every Case gets by default. Read-only by design, so an inline-edit cell isn't a configuration option. It's a rebuild.

4. Form View is the only one that writes back.

Pega auto-generates a Form View per workflow Step, excluding Automation Steps, plus the Create and Edit views. These are editable, one to three columns, two is the house best practice. If data changes, a Form View is doing it.

5. So the fix is a step, not a hack.

Route the BA's ask to the case's Edit Form View, or a dedicated Step, instead of forcing editability onto a List View. That keeps the read/write boundary intact and keeps the app auditable.

6. This is a fast way to fail an SSA interview.

A candidate who proposes editable list cells hasn't internalised that Constellation splits views by editability on purpose. Naming the correct view type, and why it's read-only, is the tell that they've actually built on it.

Lesson

Constellation didn't remove the read/write boundary. It just moved it into the view type.

Which view would you have reached for first? Comment below.

Verdict table

6/6 verified against Pega Academy and docs.pega.com.

Claim	Source
Full Page View is a three-pane layout, one per Case or data object, read-only	https://docs.pega.com/bundle/platform/page/platform/user-experience/configuring-full-view.html
Partial Views are read-only by default, configurable, and insertable into other views (Details, Preview, Confirmation)	https://docs.pega.com/bundle/platform/page/platform/user-experience/configuring-partial-views.html
List Views rely on a data source and render as tables, timelines, or tile-based galleries; every Case includes an open-cases list and a history list by default	https://docs.pega.com/bundle/platform/page/platform/user-experience/configuring-list-views.html
Form Views are editable and read-only, generated per workflow Step (excluding Automation Steps), with Create and Edit views auto-generated; 1-3 columns, 2-column recommended	https://docs.pega.com/bundle/platform/page/platform/user-experience/configuring-forms.html
Full Page View corroboration: three-pane layout accommodating case data	https://academy.pega.com/topic/views-constellation/v2
Form View corroboration: one Form View generated per Step, 1-3 columns, 2-column best practice	https://academy.pega.com/topic/form-views/v1