Appearance
panel.terminalConfig.footerFields[].parts
Ordered parts concatenated without a separator; each part contains exactly one of text, attribute or context. Retired field parts are rejected before operations are read.
This is a compact property lookup. Use the contextual guide below for the complete feature model, configuration sequence, interactions, examples, and limitations.
- Context
- operatorTerminal panel
- Accepted value
({ text: string } | { attribute: string } | { context: "materialInstance" | "status" })[]- Required
- No — When a display row is supplied.
- Default
- No documented default.
User scenarios
- Present operation context while trying the isolated operator terminal demonstration.
Related parameters
panel.terminalConfig.footerFields[].labelpanel.terminalConfig.footerFields[].parts[].textpanel.terminalConfig.footerFields[].parts[].attributepanel.terminalConfig.footerFields[].parts[].context
Contextual guide and evidence
- Contextual guide: Open the complete human guide
- Source:
apps/panel/src/features/panels/variants/operator-terminal/types/index.ts, symbolTerminalDisplayField - Example coverage: Complete — The configured demonstration contains the exact fixture jsonData. The guide explains omitted defaults, empty arrays, footer precedence, and independently hidden search/scanner controls.
- Demo coverage: Partial — The fixture explicitly sets the operation name as the card title, the operation code as the card subtitle, header context, five footer sections with six colored counts, and visible search/scanner controls. Alternative layouts require source configuration changes. Open the runnable demo .
The panel source named above remains authoritative for runtime behavior. This secondary reference page is generated from the reviewed parameter matrix and does not replace the contextual guide.