Query Results Block – one form per record¶
The Query Results Block draws the records of a query as a stack of forms, one per record. Optionally a full-text search box sits above them. Use it when every record needs more than a row – a card with several fields and buttons – and a full list definition is not needed.
This page is part of the widget reference.
1. At a glance¶
| Purpose | Query results as forms, with an optional search |
| Typical use | Knowledge articles with search, the latest announcements, team members as cards |
| Related | Query Result List (with paging, toolbar and export), Catalog (tiles with filters and groups) |
2. Settings¶
In addition, the widget has the settings every widget has.
| Setting | Meaning | Default |
|---|---|---|
| "Query" | The query that supplies the records | none – required |
| "Form" | The form each record is drawn with – a form of the entity of the query | none – required |
| "Title" | A heading above the records (plain text) | none |
| "Display Search" | Shows a full-text search box above the records | off |
| "Search Placeholder" | The hint inside the search box (plain text) | none |
3. Behaviour¶
- At most 300 records are drawn, in the order of the query.
- The search box only appears when the entity of the query takes part in the full-text search. A search narrows the records of the query to those that match the text. A new input cancels a search that is still running.
- Each form runs against its record; buttons in the form act on that record.
- With "Auto Refresh" the records are searched again with the text the user entered.
4. Example¶
Knowledge base. "Query" "Published articles", "Form" "Article teaser", "Title" "Knowledge base", "Display Search" on, "Search Placeholder" "Search articles...".
5. Limitations¶
- No paging, no toolbar and no export. Records beyond 300 are not shown.
- Without full-text search on the entity, "Display Search" has no effect.
- Every record is a complete form. Many records with large forms take noticeably longer to draw.