CnIndexPage's manifest config.actions[] is row-level (each row gets these in its Actions context menu). There's no manifest-driven way to add a custom item to the top-level Actions dropdown (which today exposes Refresh / Import / Export / Copy selected / Delete selected as built-in items).
Today consuming apps that want a page-level custom action either:
- Use the
#actions slot in a custom wrapper component (loses manifest declarative-ness)
- Add a row-level action that doesn't really make sense per-row
Proposal: a new manifest key config.headerActions[] (or config.pageActions[]) with the same { id, label, icon, handler } shape as the existing row-level actions[], rendered inside the existing CnActionsBar's overflow dropdown.
Used by ConductionNL/integriq#828 (the View logs button could be page-level — currently row-level as a workaround).
CnIndexPage's manifestconfig.actions[]is row-level (each row gets these in its Actions context menu). There's no manifest-driven way to add a custom item to the top-level Actions dropdown (which today exposes Refresh / Import / Export / Copy selected / Delete selected as built-in items).Today consuming apps that want a page-level custom action either:
#actionsslot in a custom wrapper component (loses manifest declarative-ness)Proposal: a new manifest key
config.headerActions[](orconfig.pageActions[]) with the same{ id, label, icon, handler }shape as the existing row-levelactions[], rendered inside the existing CnActionsBar's overflow dropdown.Used by ConductionNL/integriq#828 (the
View logsbutton could be page-level — currently row-level as a workaround).