Integration Definitions

An integration definition carries the business identity of a pipeline: its number, name, organization, owner, scheduled date and connector profile. It also carries the revision, mapping version, watermarks, synced count and errors observed as work progresses. The Integration Owner uses this record to request validation and independent review. The Integration Operator uses it to find the reviewed scope before synchronization.

The definition’s status gives the team a current position. The history and run records explain how it reached that position. A completed definition therefore does not replace the evidence of attempts, receipts or a later correction. Keeping those records linked matters when a destination reports fewer records than the source expected.

• Draft and validation. The owner drafts a revision, then requests validation of its selected connector and mapping version.
• Review and enablement. A separate reviewer decides on the exact revision; an approved revision can be enabled for the scheduled work.
• Execution and history. Synchronization updates counts and watermarks while preserving runs, attempts, outputs and status history.

The owner should use the definition number to coordinate with the operator and reviewer. A revision number distinguishes a correction from the executed predecessor. The external request reference helps match a run to the destination’s own acknowledgement.

Decide what each pipeline name means, the organization boundary, who owns it, and which connector profile applies. Choose the schedule with the source and destination teams, including how their local time zones affect the operating cycle. Agree how source and destination watermarks are read, and what an acceptable count difference means for this pipeline. Those decisions should be written as operating instructions for reviewers and operators.

A mapping version should be fixed before the owner asks for review. If a profile or mapping changes after validation, request another revision rather than treating a reviewed decision as permission for different work. The reviewer needs evidence tied to the revision they are deciding on.

Suppose a nightly customer update is due after the source system closes its day. The Integration Owner selects the organization’s connector profile, records the scheduled date and checks the mapping version. Validation creates a run and numbered steps and moves the definition from Draft to Validated. The Independent Reviewer sees the pending decision, checks the exact revision and approves it. The owner enables that revision.

During the scheduled run, the operator compares the execution’s source and destination watermarks and checks the synced count and errors. If the count is short, the operator opens the attempt and run trace before deciding on a correction. A completed status alone is not the basis for a clean handoff; the receipt and per-scope outcome explain what actually happened.

• Definition Status Board — Pipeline revisions grouped by current status without losing their owner and mapping version.
• Validated Definitions — Revisions ready for the independent decision.

See validation, review and synchronization for the handoffs around a definition.