Appearance
panel.request
Required object with exactly one of metaTypeName or customRequest. Checked before any read and before full-screen mode; unread Table keys typeName, filter, getSelectedObjectForEventId, linkName, reverse, linkedAttribute and methodName are rejected. No demo fallback when absent.
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
TableRequestMetaType | TableRequestCustom- Required
- Yes
- Default
- No documented default.
User scenarios
- Present operation context while trying the isolated operator terminal demonstration.
Related parameters
Contextual guide and evidence
- Contextual guide: Open the complete human guide
- Source:
apps/panel/src/features/panels/variants/operator-terminal/utils/validate-terminal-config.ts, symbolvalidateTerminalRequest - Example coverage: Complete — The operation-source guide shows a standard request and the configured demonstration shows a GET custom request. Both configure reads; production workflow commands remain unavailable.
- Demo coverage: Partial — Opening the fixture reads operations through GET /terminal/operations and dataPath operations. It exercises the custom source with default id identifiers; other sources and identifier mappings require configuration changes. Open the runnable demo .