Skip to DART content

Data integration and exchange

Bring outside records into DART. Check proposed changes and keep the source behind each result.

Keep the original input

Personnel and training information may already be held in other systems. An integration brings records from another system into DART. Source adapters read the data. Automatic exchanges can import or export defined operational records.

DART keeps the original input and its source ID. If the same change ID arrives with different data, the conflict is held for review. The later copy does not replace the first without a record.

API captures retain the response and the connection revision used to read it. A complete capture can support a preview; a sample or incomplete capture is not enough to apply a full import.

Capture, preview, approval, application, and publication are separate steps. Changed source versions or settings require a fresh plan rather than applying old reviewed data.YesNoRetained fullcaptureResponse + connectionrevisionPreview changeplanMapping and rowversionsDifferent importreviewer?Plan and accessstill current?Applied recordsStable source identityPublish configuredusePages and linked workNew capture orpreviewChanged facts stop oldplan
Capture, preview, approval, application, and publication are separate steps. Changed source versions or settings require a fresh plan rather than applying old reviewed data.

Map and check before applying

Two systems can describe the same fact with different field names or formats. A designer reads a sample and maps its fields. Cleanup steps can convert a value or split a list into records. Extra source fields can be kept under their own names.

The preview shows what would change. Staff check record matching and source ownership before applying the batch. The original data and review history stay available.

Preview saves a change plan and its fingerprint. A different reviewer approves the import. Apply rechecks the plan, current source-row versions, code basis, and reviewer access before committing the changes.

Reusing the same applied import returns its saved Applied result. Changed mapping or source facts need a new capture or preview, rather than overwriting the earlier plan.

Review data rights and security

A working connection needs clear limits on what its source is allowed to change. Connection setup states which source may supply which facts. It names the service account and its scope. Secrets are stored on the server.

A data-authority reviewer and a security reviewer approve the saved setup. Connections start paused. Approval alone does not start them.

Revoked access stops later work. A code change can also require another review before an exchange continues.

The connection’s creator or editor cannot supply its own authority or security approval. The two reviewers must also be different people. Their decisions name the current connection revision.

Scheduled capture additionally needs an active capture-service principal for that revision. Starting and publication remain separate from obtaining reviews.

Run jobs and check receipts

A connection can fail after a request is sent, leaving staff unsure what happened. Workers process saved jobs. Staff can inspect held records and failed attempts through integration health.

A retry uses the same saved input. Wrong source fields need a corrected source record. They are not repaired by repeatedly sending the old one.

Outbound exchanges keep the sent payload and receiver receipt. An uncertain send has a receipt-check path. A receipt is separate from proof that the receiving system applied the data.

A code-review request can pause an exchange and invalidate its previous approved basis. The replacement review binds the current application artifact and settings before processing can continue.

An unclear outbound result needs receipt reconciliation or a retry-safe path. Repeated sends must not invent a receiver acknowledgment or silently produce another outside action.

An approved service processes a saved payload and keeps the receiver result. An unclear send needs reconciliation; receipt evidence does not prove a receiving business task was completed.YesNoReviewedexchangeSettings, code,principalSaved outboundjobExact payload andidentitySend attemptCurrent authorityrecheckedReceiver resultknown?Saved receiptMatched to the payloadUnclear resultCheck receipt beforeretryPause for changedbasisNew code needs review
An approved service processes a saved payload and keeps the receiver result. An unclear send needs reconciliation; receipt evidence does not prove a receiving business task was completed.

Connect agency interfaces during deployment

A named agency system has its own data rules and connection requirements. An agency connection is mapped to its real interface. The agreement identifies authoritative fields and stable IDs. It also defines authentication and failure handling.

The agency supplies the interface details and access. The delivery team tests the mapping and checks the result. The application tools do not imply that a named government system is already connected.

A source agreement should identify the exact records and revisions supplied, the fields it owns, and the local changes it must not overwrite. Import checks are useful only when those ownership rules match the real interface.