The Event Definitions page shows a status column (enabled/disabled) that you can click to toggle state, but there's no way to filter the list by status (even within Search field). On instances with a lot of event definitions, it'd be useful to narrow down to just the enabled ones (or just the disabled ones) without scanning the whole list.
The backend already defines status as an EntityAttribute on EventDefinitionsResource, but it isn't registered in SEARCH_FIELD_MAPPING, and the frontend doesn't wire it up as a filter. Tags got a similar treatment recently via a custom filter component (EventDefinitionTagsFilter.tsx), so this would follow that pattern.
Notes
- Backend: add
status to SEARCH_FIELD_MAPPING in EventDefinitionsResource.java
- Frontend: register a filter for the
status attribute — either the generic boolean dropdown if PaginatedEntityTable supports it, or a small custom component
- The underlying data is already there (
EventDefinition.state is an ENABLED/DISABLED enum), so this appears to be UI/wiring only
The Event Definitions page shows a status column (enabled/disabled) that you can click to toggle state, but there's no way to filter the list by status (even within Search field). On instances with a lot of event definitions, it'd be useful to narrow down to just the enabled ones (or just the disabled ones) without scanning the whole list.
The backend already defines
statusas anEntityAttributeonEventDefinitionsResource, but it isn't registered inSEARCH_FIELD_MAPPING, and the frontend doesn't wire it up as a filter. Tags got a similar treatment recently via a custom filter component (EventDefinitionTagsFilter.tsx), so this would follow that pattern.Notes
statustoSEARCH_FIELD_MAPPINGinEventDefinitionsResource.javastatusattribute — either the generic boolean dropdown ifPaginatedEntityTablesupports it, or a small custom componentEventDefinition.stateis anENABLED/DISABLEDenum), so this appears to be UI/wiring only