A list's SQL filters are predefined conditions a user picks from a menu, buttons, checks or switches. They used to be one row combined with OR, so two questions about the same rows could not both be answered: choosing Disabled dropped System tasks, and checking both showed every system task and every disabled one.
Groups
- Declared in configuration
sqlFilters.groupson a table, a query view or a report. No schema change. The client sends the choice grouped, and the server combines each group's choices with OR and the groups with AND. - Per-group rules Each group may declare its own display,
requiredandmultiple. One group can require a choice while another allows several. - Required means nothing until chosen A required filter reads no row until a choice is made. A list that would otherwise open on thousands of rows opens empty and asks.
Everywhere a list is drawn
- One filter bar Every object's SQL filters sit in one bar under the toolbar, a segment per group, a choice in one keeping the others.
- Every view type Any view type of a table or query view can carry the filters, not only a grid.
- The query page The Query tab draws the same filters, and a new query opens on each group's defaults.
- Labels for the reader A group's label can be a label code, resolved in the reader's language before it reaches the client.
The query log records the groups as chosen, so a run can be read back with the exact combination that produced it.