Choose against the task constraints
A hypothetical queue has 127 filtered records and 20 records on its first page. Four visible records are individually selected. The example bulk action assigns an owner; it does not approve payments or delete records. Filtering and selection are distinct state.
| Condition | Select this page | Select all filtered records |
|---|---|---|
| Scope after activation | Exactly the 20 visible IDs | The 127 IDs matching the stated snapshot |
| User sees four selected rows | Show the current selected total before expanding | Offer a distinctly labelled broader action |
| Filter changes | Define whether selected IDs persist | Revalidate broader selection against its filter/version |
Label the two scopes separately and show the operative selected count beside the action. Do not add a separate confirmation merely to repeat a clearly stated assignment; do revalidate eligible IDs at execution and report skipped records.
Selection totals must match the action
| State | Selected count | Meaning |
|---|---|---|
| Four row checks | 4 | Only those four IDs |
| Select this page | 20 | All visible IDs, including the four |
| Select all filtered | 127 | All matching IDs, including this page |
After selecting this page, is the count 24?
Show the worked answer
No. The original four are part of the twenty visible IDs. Set membership produces twenty unique selected records, not twenty plus four.
Check the chosen interaction
- The action label names its selection scope.
- Changing pages does not silently change selected IDs.
- Partial execution reports completed and skipped identities.