Interface standards: row actions, status card, company picker

Row action structure

• Place: the right-most, fixed 128 px wide action column.
• Top row: at most the main action (edit, blue pencil) and the three-dot menu opener; a test allows at most 3 buttons in the top row.
• Menu: every other row action is a menu item (icon + caption), grouped under labels when there are many; the status switch at the end, delete last, after a separator.
• No empty menu: the template builds the menu first and draws the opener only if it contains an item.
• Details opener: at the right of the bottom row, turning 180° when open. Exception: with 1–2 actions direct buttons.
• Checked at phone width (390 px) too; the structure is guarded by tests/round_20261101ab_row_actions_uniform_test.php.

Status card

• A card of its own (dlb-status-card) at the top of the 40% left column, captioned Status, with two radio buttons: Active (green) and Inactive (grey); the first element on a single-column form. Unified on about 55 forms.
• Status set: active (1), inactive (0); deleted (9) is the trash of the two kinds of deletion.
• Exceptions: the invoice (processing state) and the API account (sign-in flow). Test: tests/round_20261031w_company_taxhu_status_test.php.

Company picker

• In one input group: an ID tag following the hidden ID field; a name search (match list while typing, arrow keys, Enter, Escape); a new company button.
• The data of the new company button comes from one common endpoint (common/companypicker); it appears only with the right to create companies (canSave on the company module for a new record) and opens an empty partner form in a new tab.
• Exceptions: the company group and company pair of filter panels and chip pickers that assign several items.

Known limitations

The lists of NDA acceptances and the issue register do not check the empty menu condition: the three dots are always drawn there.