An entry action can carry values from its row into the form, by mapping result columns to template fields: the row's term URI into a \"term\" field, its title into a \"title\" field. A mapping can also lock the field it fills, for values the action decides rather than proposes. Columns used this way are hidden from the table, so a column that should stay visible is duplicated in the query under a second name for the mapping.

A row's button disappears when a mapped value the template requires is empty for that row — which is how a query hides \"retract\" on rows the visitor did not publish, by leaving the value blank for everyone else.