Orkestia
Blog
Cockpit app

Cards in the chat

How Orkestia Cockpit draws what the Assistant and app chats answer with — tables you can sort, filter and copy, charts, KPI tiles, timelines, record details, diffs — and how to move a wide card into a panel beside the chat

The Assistant and the chats of your apps answer with cards when a table or a chart says more than a paragraph. The platform decides which card an answer gets; Cockpit draws it. The wire shapes are in the card catalog, and DGI explains how an answer becomes a card.

What Cockpit draws

CardUsed for
Table, DatagridA list of records: sort, filter and copy
ChartNumbers the platform read this turn, as bars, a line or a pie: Charts and tiles
KPI tilesHeadline numbers, each with an optional unit, change and trend
TimelineSteps or spans on one time axis, with status and duration
Record detailOne record: badges, grouped fields and links to related lists
DiffBefore and after values of a change
Logs, Flow, Run monitor, Routine calendarOutput, structure, a live run, upcoming runs
Confirm, Form, Select, Plan, ConnectQuestions and approvals that wait for you

Two views the platform can send, the schema browser and the SQL console, are not drawn yet. When one arrives you get the answer's text instead.

Tables

The table shows the rows the platform sent. The answer's text says how many it found, so a table that lists fewer rows than the text says was capped on the way.

ControlDoes
A column headerSorts by it: ascending, then descending, then back to the order the platform sent. Numbers sort as numbers, times by time, text in natural order (runner-2 before runner-10). Empty cells always go last
Filter rowsAppears once there are more than 8 rows. Keeps the rows that contain every word you type, in any cell
The count50 rows, or 3 of 50 rows while a filter is on
Copy CSVCopies the rows shown, in the order shown, with times as the platform sent them. Text that starts with =, + or @ is kept as text so a spreadsheet does not run it
Row and table buttonsAsk a follow-up question in the chat, as before

A note under the table says when the platform capped the result.

Datagrid

A datagrid is a table the platform builds for larger or typed results: badges, yes/no and numbers keep their form. In Cockpit it is read-only. It sorts, filters and copies the rows it holds, and when the platform has more rows than it sent it says showing 50 of 1,240 and that sorting and filtering only reach the rows shown. Paging, sorting on the platform and the SQL console need a card answer Cockpit's chat cannot send yet.

Charts and tiles

  • Chart: bar, line or pie. Hover a bar or point for its value. A missing value in a line chart is a gap, not a zero. The footer names the unit, the source and when it was read.
  • KPI tiles: a tile has a label and a value, and may show a unit, a change and a ▲ or ▼ trend.

Ask for them by name: chart the open tickets by status, chat tickets by priority as KPI tiles, how much will I pay this month?. The platform may still answer with a table; ask again with as a bar chart.

A card beside the chat

Wide cards (tables, datagrids, flows, logs, run monitors, the calendar, timelines, diffs and record details) have a panel button in the corner that shows when you hover the card. It moves that card into a panel on the right of the chat, with room for every column.

  • One card is open at a time. Opening another replaces it; × closes it.
  • The panel belongs to the chat that opened it. Leaving the chat closes it.
  • It takes the place of the coding panel while it is open, is at most 62% of the window and can be dragged wider or narrower.
  • Buttons inside a card in the panel work as they do in the chat.

Leaving a chat while it answers

An answer keeps being written when you open another page. Come back and the live progress and Stop are there, the composer says your next message sends when the answer lands, and the answer appears when it is done.