@ema.co/mcp-toolkit 2026.2.5 → 2026.2.13

package/.context/public/guides/dashboard-operations.md

@@ -221,6 +221,69 @@ When document `type` is not available, inferred from extension:
 | `.jpg`/`.jpeg` | `image/jpeg` |
 | Other | `application/octet-stream` |
 
+## Dashboard Columns: How They Work
+
+### Output Columns Come From resultMappings
+
+For dashboard personas, the **output columns** visible in the dashboard UI are determined **entirely** by which node outputs are mapped to `WORKFLOW_OUTPUT` via `resultMappings` in the workflow_def. Each `resultMapping` entry creates one output column in the dashboard.
+
+```json
+"results": {
+  "entity_extraction.invoice_number": {
+    "actionName": "entity_extraction",
+    "outputName": "invoice_number"
+  },
+  "entity_extraction.amount": {
+    "actionName": "entity_extraction",
+    "outputName": "amount"
+  },
+  "call_llm.summary": {
+    "actionName": "call_llm",
+    "outputName": "response_with_sources"
+  },
+  "categorizer.category": {
+    "actionName": "categorizer",
+    "outputName": "category"
+  }
+}
+```
+
+This creates 4 output columns: `entity_extraction.invoice_number`, `entity_extraction.amount`, `call_llm.summary`, and `categorizer.category`.
+
+**Key rules:**
+- If you forget to map a node output, that column **won't appear** in the dashboard
+- If you map the wrong output, you'll see unexpected data
+- Column display name in the UI = the result mapping key (e.g., `entity_extraction.invoice_number`)
+
+### Input Columns Come From the Trigger
+
+Dashboard input columns (what users fill in or upload per row) come from the `document_trigger` outputs:
+- `document_content`: For uploaded files (PDF, images, etc.)
+- `row_data`: For text/number inputs from dashboard columns
+
+Wire these to your processing nodes:
+- `entity_extraction.document` ← `trigger.document_content`
+- `call_llm.context` ← `trigger.row_data`
+
+### Column Ordering
+
+**Dashboard column order is determined by the order of resultMappings in the workflow_def.**
+
+To reorder columns, you must **remove** them from the result mappings and **re-add** them in the desired order. There is no separate "reorder" API -- the order in the JSON is the order in the UI.
+
+```
+// To change order from [Amount, Date, Status] to [Status, Date, Amount]:
+// 1. Remove all three from results
+// 2. Re-add in desired order:
+"results": {
+  "extract.status": { "actionName": "extract", "outputName": "status" },
+  "extract.date": { "actionName": "extract", "outputName": "date" },
+  "extract.amount": { "actionName": "extract", "outputName": "amount" }
+}
+```
+
+**Important:** Once columns are created and saved, the output type and multi-value settings cannot be modified via the UI. To change these, you must update the workflow_def directly.
+
 ## Common Patterns
 
 ### List Dashboard Rows