Feature: has_pagination
Table of Contents
This page is one authored MASD feature in ORE Studio Variability Model § "Projection configuration: how an existing artefact family is shaped". Any profile that fixes this feature's value links here rather than restating its effect.
1. Identity
| Field | Value |
|---|---|
| Literal name | :has_pagination: |
| Bundle | ores.presentation |
| Type | bool |
| Default | false |
2. Effect
Retired as a behavioural toggle on 2026-09-04 (task
9FF6FAD3): the client model template generated the paginated fetch
unconditionally. Every list request carried offset=/=limit and the
model reported the server's total_available_count, and every list
window showed the pagination controls. The literal remains
accepted on entity orgs, and on the profiles listed below, as
documentation only — setting or clearing it no longer changes
generated behaviour, and no entity can silently truncate a list by
leaving it unset.
3. Structural consequence
None — the property never mapped to a column or struct field, and its retirement changed nothing structurally.
4. Used by
5. See also
- ORE Studio Variability Model — the bundle this feature belongs to.