Choose a panel variant

The configurator has 16 registered renderers. Choose a renderer by the user problem first, then open its guide for the complete capability model, prerequisites, interactions, defaults, limitations, working configurations, demo evidence, and exact parameter links.

This page is a decision map, not a substitute for those guides. The parameter lookup is a secondary leaf-level reference after the feature is understood.

Composition and presentation

Variant	Choose it when	Complete guide
group	Several panels must remain visible together in rows or columns.	Group
message	A layout needs localized plain explanatory text.	Message
tabs	Users switch among alternative child panels in the same region.	Tabs
condition	Exactly one child branch must be selected from variable or object-selection state.	Condition

Object browsing and editing

Variant	Choose it when	Complete guide
table	Users browse, filter, sort, page, select, and act on rows.	Table
tree	Users navigate a root object and linked descendants hierarchically.	Tree
attributes	Users inspect or edit the object selected in another panel.	Attributes
files	Users browse, preview, download, or manage files linked to a selected object.	Files
tiptapPanel	Users read or edit rich text standalone or on a selected object.	Tiptap panel
textEditorPanel	Existing configurations need the renderer-selection compatibility shell around Tiptap.	Text editor panel

Planning and process views

Variant	Choose it when	Complete guide
gantt	Users inspect and manipulate an already loaded production schedule.	Gantt
scheduleOperations	A Gantt action opens unscheduled operations for drag allocation. It is not a normal standalone surface.	Schedule operations
calendar	Users inspect the working calendar for an object selected elsewhere.	Calendar
bpmn	Users view or edit a method-backed process graph.	BPMN

Administration

Variant	Choose it when	Complete guide
metaTypesCrud	Administrators manage root MetaTypes through the packaged CRUD surface.	MetaTypes CRUD
coreApps	Administrators need one of the built-in organization, roles, applications, data-model, or settings surfaces.	Core Apps

Decide by interaction pattern

• Use Group when all child panels must remain visible; use Tabs when only one alternative is active.
• Use Table for flat collections and Tree for link-driven hierarchy.
• Use Condition to select one branch; use the shared events and conditions guide to produce the state that drives it.
• Use Tiptap panel for new rich-text configuration. Use Text editor panel only when its renderer-policy compatibility behavior is required.
• Configure Schedule operations through the Gantt action flow, not as an independent top-level panel.

Next task

After choosing a variant:

1. Read its guide completely, including prerequisites and limitations.
2. Follow its minimal configuration before adapting the realistic scenario.
3. Open a linked runnable demo when the guide identifies one.
4. Use the exact property links in the guide only for leaf-level lookup.