Consider Pizzeria database:
The core setting of Kanban view is the Status column that define the list of columns to render in the view. Status column should be a text column with single choice option or a lookup to such a column. Column’s Colorization options, if provided, affect the color of the header. And, order of choices matters.
Kanban card layout resembles the tile in Tile views, so view settings are not much different, just some minor additions.
All record’s actions are hidden beside the ⋮ (three vertical dots) menu button. To enable quick navigation there is “Click action” view’s setting to control what happens when the user clicks on a card.
Small “plus” buttons in table header allow the user to add record with status pre-selected. This option is controlled via views’ Allowed Actions’ “New with status” checkbox.
Cards are draggable, given drag and drop is enabled in view’s Allowed Actions, and the record and status column are editable.
The reason for extra options for “New with status” and “Drag and drop” is that not all types of workflow allow arbitrary status setting. Some workflows require to start from the beginning. Even for demo Pizza database you probably should not put the pizza in the oven without preparing it first. Or moving from status to status may require filling in some fields.
When Kanban view is on the dashboard its “New with status” and “Drag and drop” options are controlled via “New” and “Edit” flags respectively.
- Calendar views enable drag-and-drop, given the calendar is based on Date column and record and date column are updateable.
- There is a new flag in a dashboard section to control the appearance of Print/Edit/Send buttons.
- You can now use reference columns in Delete workflow action.