How to configure a board view
A board shows the instances of one element type as cards, in columns defined by an enumeration property. For a guided walkthrough, see the Board Views tutorial; this page is a task reference.
Create a board
Section titled “Create a board”- Right-click a package in the Explorer → New Board…
- Pick the element type (the “classifier”) whose instances become cards
- Pick the group-by property — an enumeration property (own or inherited)
If the type has exactly one enumeration property it’s chosen for you; if it has several, a Group by property dialog appears; if it has none, the board can’t be created (add an enumeration property to the type first).
Choose or change the group-by property
Section titled “Choose or change the group-by property”The columns come from the group-by property’s enumeration literals. To change it later:
- Use the Group by selector in the board toolbar (shown when the type has more than one enumeration property), or
- Change Group By in the board’s Properties panel
Changing the group-by property resets the column configuration (order, hidden columns, and WIP limits), because the columns themselves change.
Understand the columns
Section titled “Understand the columns”| Column | What it is |
|---|---|
| (No value) | Cards whose group-by property is unset. Dropping a card here clears the value. It can be hidden like any column. |
| One per literal | In metamodel order by default; reorder or hide via the column chooser. |
| Orphan column | Read-only, amber-tinted, at the end. Appears when a stored value matches no current literal (e.g. a literal was renamed at M2). Drag/drop is disabled; fix the data or the literal to clear it. |
Move and order cards
Section titled “Move and order cards”- Between columns — drag a card to write the group-by value onto its element (drop on (No value) to clear it).
- Within a column — set Order by to Manual, then drag cards to rank them. Manual order persists with the board. In automatic sort modes (Name, Newest first, Recently updated, …) within-column drags don’t persist.
Manage columns
Section titled “Manage columns”Contributors get column controls:
- Column chooser — show/hide columns and drag to reorder
- Column header menu — Collapse / Expand and Hide Column
Set WIP limits
Section titled “Set WIP limits”- Right-click a column header → Set WIP Limit…
- Enter a limit (or clear it to remove)
The header count shows count / limit and turns amber when exceeded. Limits warn only — they never block a drop.
Configure cards
Section titled “Configure cards”- Card fields (toolbar) — choose which property values appear on each card, plus optional audit fields
- Add card — the + at the foot of a column creates a new instance of the element type, pre-set to that column’s value, ready to name
- Card menu — Rename, Diagrams… (where the element appears), and Delete from Model
- Search — filter cards by name
Portability
Section titled “Portability”Boards are saved with their package and survive export/import. The group-by property and card fields are stored as portable $id slugs, and enum literals by their storage value, so a board round-trips through .farki even if display names change.
Notes and limits
Section titled “Notes and limits”- Grouping is by enumeration properties only (boolean/classifier grouping isn’t available)
- Only direct instances of the chosen type are shown, not instances of its subtypes
- Boards are live views — no separate save, undo, or redo; a drop is a property edit
- Viewers get a read-only board