Mapping Review

A mapping rule connects a source field to a target field under a connector profile. Its version, types, transform rule and effective date explain how a record should be interpreted when a revision runs. The Connector Administrator maintains those rules. The Integration Owner identifies the intended version on the integration definition, then validation freezes that version for review.

The Independent Reviewer decides on the revision, not on a loosely named pipeline. Their pending decision identifies the source revision and can carry a reason and evidence reference. They can inspect the definition’s connector profile and the corresponding mapping rules before approving. When a rule needs correction, returning the decision gives the owner a clear action while retaining the earlier validation trace.

• Field pairs. Each mapping states the source and target fields and their types, so a transform has a visible input and destination.
• Version and timing. Mapping version and effective date let the team distinguish a reviewed contract from a later edit.
• Decision evidence. Review decisions and evidence documents connect the field contract to the approval on a specific revision.

Use the source and target system owners to check business meaning as well as syntax. A text field that parses successfully may still mean a different kind of identifier in the destination. Record that decision in the rule and its review evidence before the integration is enabled.

Agree which fields are required by the destination, how empty values should be handled and how transformed values are checked. Decide how a version is named and when an effective date applies. The review procedure should specify who can return a revision, what reason they must record, and what evidence is sufficient to approve a changed transform. Assign a different person to the owner and reviewer responsibilities.

Where several source fields contribute to one target, write each rule clearly enough that an operator can diagnose a rejected output. Keep examples of expected source and target values in the team’s operating material. The app’s mapping record identifies the rule and the version used by a definition.

Suppose a source sends a regional customer code while the destination expects a normalized code. The Connector Administrator records the source field, target field, types and transform rule on the profile’s mapping. The Integration Owner drafts a revision, selects that profile and identifies the mapping version. Validation writes an operation run with numbered steps, freezes the version and opens a pending independent decision.

The Independent Reviewer compares the intended transform with the attached evidence. If the target value would be wrong, they return the decision with the specific reason. The owner works with the administrator on the rule and requests validation of the corrected revision. Approval should apply only to the version examined; the subsequent sync output can then be compared against that fixed mapping version.

• Mapping Rules — Current field pairs, versions and transforms for profile review.
• Pending Review Decisions — Revision decisions waiting for the reviewer.
• Validated Definitions — Definitions whose mapping version is ready for a decision.

Read validate a mapping and review a revision. The implementation guide sets the first review rehearsal.