# Customer workflows and KPI dashboards ## Customer and contacts workbench The master list selects a customer. Its detail area combines a customer editor and related contacts. The contact creation form receives the selected customer identity from the composition, so the author does not recreate that binding for every field. The handler source is included in [server Lua](workspace-manual://workspace-xml-4/server-lua). ```xml

``` Use a direct GraphQL mutation for the customer patch; keep compound contact creation or normalization in the action handler. Test switching selection with a dirty draft, required inputs, server rejection, and a successful persisted change. Do not replace the selected customer ID with an arbitrary text field. ## Operations KPI dashboard This example combines commercial totals, metric summaries, time-series trends and recent orders. Metric IDs in its source are placeholders: replace them with your tenant's metric IDs before publishing. Labels, units and sample counts should tell a reader what each number means and which data it represents. ```xml

``` Empty series must remain valid output, with null aggregates distinguished from zero. The Lua loader's output contract covers that distinction. An authorization failure is an error state, not an empty metric series. Test both populated and empty data and keep filters/selection in declared state. ## Searchable customer directory This directory combines an editable search filter with cursor pagination and a selected-record detail panel. Applying a search resets both the cursor and the selection in one update. The result query accepts a null initial cursor, while the detail panel waits for a selected ID. Previous navigation uses visited cursors in the current browser session; changing the cursor outside the pager clears that history. Query permissions and filters still run on the server. ```xml query { __typename } ``` `pager` reads the named panel's `endCursor` and `hasNextPage` paths. Buttons disable while that panel loads; Next also disables when the server reports the final page. Use `reset-state` on related filters to avoid reusing a cursor from different query criteria. The record-browser composite still owns only its selection/detail layout; this recipe shows explicit panels when adding search and pagination. For a unit returned with query data, compose a panel with `kpi-summary` and bind its metric's `t:unit` to that response path. The convenience `metric-panel` uses a static unit and a fixed metric-series query; use the explicit composition when the selection also determines currency or units. Lua read handlers can return formatted display strings, as shown in [Returning display values](workspace-manual://workspace-xml-4/server-lua).