The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | openDataJobUpload … completeDataJobUpload | Upload the current delivery file. | CAP-PFM-DJE-011 | Its completed session can supply the import. | documented services-platform:docs/data-jobs/uploads.md#Step 4: complete |
| 2 | submitOrganizationDataJob | Submit a keyed organization upsert with reject policy. | CAP-PFM-DJE-012 | The file enters bulk processing. | test |
| 3 | getOrganizationDataJob | Poll job detail until processing settles. | CAP-PFM-DJE-005 | Outcome totals distinguish applications, skips, blocks and conflicts. | documented services-crm:docs/data-jobs.md#Listing a tenant's jobs |
| 4 | submitOrganizationDataJob | Repeat previously applied, revisioned input. | CAP-PFM-DJE-012 | Already applied or superseded upserts receive duplicate or stale outcomes. | test macroservice-libraries:packages/data-jobs/src/tests/integration/keyed-data-jobs.integration.spec.ts#skips a delivery of a revision already applied, which is what a rerun of yesterday’s file is |
| 5 | submitOrganizationDataJob | Deliver new input for a record edited since its previous producer write. | CAP-PFM-DJE-006 | Reject policy preserves the staff edit and reports conflict. | test |
| 6 | retryOrganizationDataJob | Retry branches after their missing head office has arrived. | CAP-PFM-DJE-004 | The retained dependent input now attaches successfully. | test |
| 7 | readOrganizationsBySourceKey | Read a sample of the delivered producer keys. | CAP-PFM-DJE-015 | The supported lookup returns corresponding current records. | test |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 2 | The selected delivery policy explicitly permits replacement. | Submit the input under overwrite policy. | The producer update may replace staff values, with policy retained on the job. | test macroservice-libraries:packages/data-jobs/src/tests/integration/keyed-data-jobs.integration.spec.ts#applies the delivery over the change when the job was submitted to overwrite |
| failure | 2 | The submitter loses bulk access before a later batch. | Inspect the failed job’s access-revoked outcome. | Earlier commits remain and later work stops. | test |
| Id | Statement | Provenance |
|---|---|---|
01 | Repeated input in the keyed fixture does not create another organization for an existing key. | test services-crm:modules/data-jobs/tests/integration/services/operations/record-imports.integration.spec.js#leaves one organization per key after both deliveries, which is what the skips were for |
02 | Reject-policy delivery preserves the staff correction made since the previous producer write. | test macroservice-libraries:packages/data-jobs/src/tests/integration/keyed-data-jobs.integration.spec.ts#refuses the delivery as a conflict and leaves the record alone |
End-to-end policy: none: This API-client journey has no required browser surface; integration assertions support its constituent behaviors, although they do not execute one complete scheduled delivery.