JTBD-DO-05 · Data operations
Bulk update a set of records
partially supported. Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.
What the catalogue records
on a deliberately narrow reading: Customer Data Operations v2 adds apply-bulk-customer-action, which applies one of the package's three human decisions — link, dismiss or govern — across up to 500 records in one call, with one transaction and one receipt per record, a run that reads partial rather than completed, and payload-derived idempotency with resume and replay. tests/customer-data-operations-v2.test.js. Still partial, and the row's own word is again the gap: business records have no bulk path — no bulk field update, no bulk stage move, no bulk delete — and every bulked decision keeps its human-only check
Evidence
Proved by this test, which run on every push:
tests/customer-data-operations-v2.test.jsWhat this status does not mean
A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework ships no authentication, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in Data operations
- Import records from CSV — partially supported
- Detect duplicates on import or entry — partially supported
- Merge two Companies or Contacts — partially supported
- Export records — partially supported
- Save and share a filtered view — not supported
- Search across modules — not supported
- See a unified activity timeline for a record — partially supported
- Attach notes or files to a record — not supported