The EDI Console
The EDI Console
Extensions > EDI Console is the log of every EDI document in both directions, and the place you act on the ones that went wrong. Reading needs Builder or Viewer; replay and ack reconciliation need DataMagik - Builder.
The counters
| Counter | What it means |
|---|---|
| Total / Inbound / Outbound | Volume. |
| Need review | Documents waiting for a person. This is the exceptions queue. |
| Failed | Documents that could not be processed at all. |
| Duplicates | Re-deliveries that were recorded but not reprocessed. A steady trickle is normal; a spike means a partner is retrying because they are not getting your acknowledgements. |
| Awaiting ack | Documents you sent that nobody has acknowledged yet. |
Filters
Three dropdowns: direction (inbound / outbound), status (routed, acked, review, failed, duplicate) and acknowledgement (awaiting, accepted, rejected). The two combinations worth remembering:
- Inbound + Review — the work queue.
- Outbound + Awaiting ack — documents a partner has not confirmed.
The drill-down
Click any row. The panel shows the decision, the mapped object, the issues and the complete raw payload.
| Field | Read it for |
|---|---|
| Status / Action | What was decided. They differ when the pipeline downgraded a configured action to review. |
| Valid | Envelope arithmetic only — counts and control numbers. |
| Spec | Which mapping read it, or — if none did. |
| Note | The plain-language reason. Start here. |
| Mapped object | What the spec produced. Empty means mapping never ran. |
| Validation issues | Structured problems, including plex_write_unwired. |
| Raw payload | Exactly what arrived. The source of truth for everything else. |
Replay
Replay through pipeline re-runs the entire decision against your current configuration and records the fresh attempt.
What replay re-does: partner resolution, spec resolution, mapping, conformance, and the routing decision.
What replay deliberately does not do: send an acknowledgement, emit a turnaround, or consume a control number. It also runs without the duplicate check — the point of a replay is to re-run a document you have already recorded.
Resend and regenerate
On an outbound document, two more actions appear beside replay:
- Resend — deliver the identical document again, keeping its interchange control number. The existing row gains a note; no new row is written, because it is the same document.
- Regenerate — rebuild the same content under a newly reserved control number, for a partner who has already recorded the old one and would reject a repeat of it. Writes a new row and annotates the original with what replaced it.
Both are Builder-gated, and regenerate asks for confirmation because it consumes a control number. See Sending Documents for which to choose.
The exceptions queue
Filtering to Review is the exceptions queue. Every document in it is waiting for a person.
If the partner has an exception approver configured, each one also raises an approval task for that role or user, which appears in Approvals. With no approver configured, documents still land here but nobody is notified — which is fine if someone watches the console, and a silent backlog if nobody does.
Reconcile ack…
Paste an acknowledgement a partner sent you out of band; DataMagik settles the outbound documents it covers. See Acknowledgements.