Record Pages
A row that goes somewhere is the whole difference between a table and a spreadsheet.
How a record page works
A record page is scoped to one table. Clicking a row in any grid or board opens it, and every block on it is about that row — which the blocks refer to as $row.
Every table has a derived record page from the day it exists. Author one to override it when the default order of fields is not the order somebody reads them in.
The blocks only a record page has
Record detail
The row's fields, in the order you choose, editable in place. Split them across several blocks when some belong together — the request in one, the purchase order in another.
Related list
The children of this row, from a table that links back to it. The link value is inherited when somebody adds one, so nobody re-states the record they are already looking at.
Timeline
A feed of child rows, newest first, with a composer at the top. Anything typed into it becomes a real row with whatever defaults you set — which is how a maintenance note and a logged repair end up in the same history.
Stepper
Advances a dropdown column, with the transitions you allow. State on a record page moves because a person moved it; a Flow is a different mechanism and has its own panel.
Process panel
Which Flows are running on this row, which Step each is on, who owes the next move, and the order things happened in. It renders no Step data on purpose — a Step's answers are columns on the row and belong to the detail blocks above.