Appearance
apps/panel 0.82.1
Released on 15 September 2026. Previous release: 0.82.0.
What changed
- The new display part
{ "context": "status" }shows the operation status with the same label as the status badge on the card, for examplePausedorIn work(Пауза,В работеin Russian). It works in the card title, subtitle and rows for that card's operation, and inheaderFieldsand footer field rows for the open operation. - The
Statusrow of the built-in footer uses this label. Previously it showed the raw system name, for examplepaused. - The footer operator section shows two more rows under the operator name:
ProfessionandPersonnel no.. The terminal reads them from theprofessionandpersonnelNumberfields of the signed-in user's profile. - All cards on a list page have the same height: the tallest card on the page sets it. The planned start and the bottom line with the status and the open arrow stay at the bottom of every card. The two-line limits for titles and values are unchanged.
- In a terminal narrower than 900 px, the operator section keeps the minimum width of the other footer sections, and the sections wrap onto a second row. Previously the operator section could shrink to a few characters, and the footer grew much taller.
- In the demonstration, the footer
Statusrow shows the label, the demonstration profile returnsОператор станков с ЧПУand00417, and the operation with long values is nowОП-023on the second page, so the cards on the first page stay compact.
Configuration
To show the readable status in the header of the open operation, add a row with the status part to headerFields. Listing headerFields replaces the built-in header rows, so repeat the rows you want to keep:
json
{
"panel": {
"type": "operatorTerminal",
"terminalConfig": {
"headerFields": [
{ "label": "Операция", "parts": [{ "attribute": "name" }] },
{ "label": "Статус", "parts": [{ "context": "status" }] }
]
}
}
}With a configured WorkOrderOperation source, the terminal takes the status from state.systemName; include that attribute in attributeList, otherwise the part shows —.
Known limitations
- The API contract does not define
professionandpersonnelNumberyet. Only the local demonstration profile returns them; with a real profile the two rows show—. - Status values without a known label, such as a new system name, are shown unchanged.
Updated documentation
- The operation status section describes the
statuspart, where it resolves and how it differs fromstate.systemName. - The footer and countdown section describes the operator rows and the status label in the built-in footer, and the card description describes equal-height cards and the demonstration operation
ОП-023.