Group List
A ready-to-integrate list for user groups, built on Document List.
Ready-made group listing
Group List extends Document List and provides group-oriented defaults. Map the appropriate group collection in the host application, then customize columns, row links and actions as required.
In APPNETOS DNS Control, AppnetosDnsControl\Admin\Group\GroupList maps AdminGroupCollection
and displays group name, active state and a delete button. Group names link to the editor; delete
buttons call the application-specific JavaScript integration.
How lists work
Unlike a picker, a Document List renders its initial rows immediately during the normal page response. Search and pagination refresh the relevant list content asynchronously with AJAX, avoiding a full page reload. The underlying document collection is queried for the requested page rather than rendering the entire collection.
Lists can display clickable links, boolean indicators and JavaScript-driven buttons. The application controls which data is exposed in each row and which actions are available. Authorization must still be enforced by the application and its server-side endpoints.
DNS Control implementation
protected function getCollection(): BaseGroupCollection|null
{
return Registry::get(AdminGroupCollection::class);
}
The DNS Control extension also overrides getFields() and getRows(array
$documents). Its search() AJAX method adds application translations and
delegates to parent::search(). The parent list continues to handle pagination, sorting
and
refresh.
Customizing Group List
- Override
getCollection()to map the appropriate group collection. - Override
getFields()to select the visible columns. - Override
getRows()to add edit links, status indicators or application-specific actions. - Use inherited search, sort, filter and template hooks when further customization is required.
Templates, Bootstrap and translations
The shared list renders through versioned Bootstrap templates. Supported Bootstrap versions are maintained in the Core App, while all templates can be replaced by application-specific Twig files. Core Apps that need translations provide them in 81 languages. Custom column labels and application actions can use the host application’s own translations.