Building Blocks
Menu
SystemFoundationComponentsPatternsThemesIncluded
CatalogsLive catalogsHow catalogs work
GuidesDocs
Pattern

List → editor → back

Primary flow

RequiredSource pattern
ContractList → editor → back
Job
Primary flow
Requirement
must specify
States / rules
Back in the bar
Specified means
Not separately stated in this row.
Hardest context
Editor dead end
Example

Chevron back

Counter-example

Browser back only

Flow

Trigger: The primary product flow moves from a collection of records into one record’s editing context and back again.

  1. Enter from a list whose filters, sort, selection, and scroll position establish context.Enter from a list whose filters, sort, selection, and scroll position establish context.
  2. Open the chosen record without losing where the user came from.Open the chosen record without losing where the user came from.
  3. Edit with the record identity and save state continuously understandable.Edit with the record identity and save state continuously understandable.
  4. Warn or recover deliberately when navigating away with unsaved work.Warn or recover deliberately when navigating away with unsaved work.
  5. After save or cancel, return to the prior collection context when that is still valid.After save or cancel, return to the prior collection context when that is still valid.
  6. Restore enough list state that the user can continue rather than restarting the task.Restore enough list state that the user can continue rather than restarting the task.

Typical Building Blocks composition

Composition below is baseline guidance for the pattern; it does not rename or add source checklist rows.

List row or tableApp shell / navigationForm controlsButtonUnsaved-state feedback

Flow rules

  • Back means return to work context, not merely navigate to an arbitrary parent URL.
  • Preserve filters and selection when possible.
  • Do not silently discard unsaved changes.

Responsive behavior

The list and editor may become separate full-screen contexts at sm; preserving origin and return state matters more as simultaneous panes disappear.

Accessibility is tested across the sequence.

Keyboard order, focus movement, state announcements, touch targets, cancellation, and recovery must be verified for the whole flow—not only for each participating component in isolation.

Recovery is part of the pattern.

A complete pattern defines what the user sees when the happy path breaks, what is preserved, where focus goes, and how the user safely resumes or exits.

Catalog connection

A product Catalog can show this pattern only when the product actually implements the flow. If it is absent, keep the section honestly Not yet rather than mounting a fictional working pattern.