attention_list
Pages one queue or area of open pendenzen using the same filters, ranking and collapse rules as attention_summary, returning items with decision options and deep links. Reads only.
Instructions
Page one queue or one area of Pendenzen: the same providers, the same capability filter and the same collapse and ranking as attention_summary, so the two faces never describe a queue differently. Returns { computedAt, items:[AttentionItem], nextCursor?, failed:[queueId] }. Filter by queueId (a single queue), area ('bank' | 'sales' | ...), or urgency ('overdue' | 'due' | 'open'); page with limit (default 20) and the opaque cursor from a prior nextCursor. A denied queue is absent, a thrown provider is named in failed[], and nothing here clears, dismisses or approves anything: every AttentionItem carries its decisionOptions[] (the owning surface's exits as existing write verbs with their fixed input and per-item idempotencyKey, see attention_summary), its suggestedInvoiceId, reasonCode/reasonKey and consequenceKey/consequence, and a deepLink descriptor into its owning surface for the hard case. Reads only. THE WHOLE LIST IN SECTIONS (D178): pass grouping ('by_area' | 'by_kind') and the answer is instead { computedAt, grouping, visibleQueues, total, incomplete, failed, approvalBatchMode, sections:[{ key, count, queues, items, nextCursor? }] } over EVERY item (never a top-n): by_area sections bank, accounting, sales, system (bank first; inside bank the Vorschläge, then the waiting bank lines, then the rest by urgency); by_kind sections approve (Vorschläge), do (work a person carries out), note (to look at). Every item carries count (the units it stands for: 1, or N for an aggregate row such as one bank account's waiting lines), area and kind; a section's count is the units of all its rows; total is the sum of the sections and equals attention_summary.total for the same caller. limit is the page size per section (default 25); a section with more rows carries nextCursor, and { grouping, section, cursor } answers that one section from there. approvalBatchMode is the workspace setting attention.approval_batch_mode (tick | single | all_with_confirm), how the Studio approves several bank Vorschläge: each approval is still one approve_drafted_action call, and only a row with batchable: true (a decision on a bank line: book_bank_line, ignore_bank_line, confirm_match; never a changed one) is ever batched. A Vorschlag that names a bank line carries that line's signed amountMinor (credit positive, debit negative), its currency and subtitleParams.date/counterparty/target/targetKind, but only for a caller who may read the bank (read_sales); a batchable one carries posts: true when approving it mints a journal entry (a booking to accounts or by a Buchungsregel, a settlement, an unpaid payment run) and posts: false when it books nothing (a line set aside, a match to an existing entry). A Vorschlag whose records changed since the proposal cannot be approved: it carries changedSinceProposal and kind do, and a stale one (voided by an approval attempt) stays listed with stale: true while its bank line is still open, its one exit the link to that line.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| area | No | ||
| limit | No | ||
| cursor | No | ||
| queueId | No | ||
| section | No | ||
| urgency | No | ||
| grouping | No | ||
| workspaceId | Yes |