Pick the slot that matches the panel's role. after-fields is the default
for most "additional settings" panels — it sits in the field column, before
the related-entity grids.
Fallback behavior — see FormSlotCoordinator. If the registered slot is
missing in the current form (CodeGen hasn't been rerun against the new
template emitter), the panel walks forward in the chain until it finds an
existing slot. after-everything is always emitted by the container, so
fallback never dead-ends. Pre-CodeGen-regen forms show every panel at the
bottom of the form; post-regen forms show them in the preferred position.
Well-known slot positions where panels can be injected into a generated entity form. Used as the
slotfield in a panel's registration metadata.Slot positions inside the form, top to bottom:
┌─
│ [top-area slot] ← CodeGen-emitted; rare (entities with top-area section)
│ [before-fields slot] ← CodeGen-emitted; banners / warnings above field panels
│
│
│ [after-fields slot] ← CodeGen-emitted; typed config knobs, secondary settings — most common slot
│
│
│ [after-related slot] ← CodeGen-emitted; bottom-of-form addenda
│ [after-everything slot] ← Container-emitted; ALWAYS present (fallback target)
└─
Pick the slot that matches the panel's role.
after-fieldsis the default for most "additional settings" panels — it sits in the field column, before the related-entity grids.Fallback behavior — see
FormSlotCoordinator. If the registered slot is missing in the current form (CodeGen hasn't been rerun against the new template emitter), the panel walks forward in the chain until it finds an existing slot.after-everythingis always emitted by the container, so fallback never dead-ends. Pre-CodeGen-regen forms show every panel at the bottom of the form; post-regen forms show them in the preferred position.