technical

Live drivers & outbox

How connection polling turns inbound files into parse + writeback + ack runs and populates the outbox.

startPolling(connectionId) starts a ticker that synthesizes an inbound X12 for one of that connection's supported transactions every ~20 seconds. Real drivers (SFTP, AS2, API) plug into the same enqueue path.

Enqueue path

  1. Fetch or synthesize inbound EDI
  2. parseX12 → build ParseResult
  3. generate999 → acknowledgment
  4. If a mapping exists for the txn code, generateFromMapping → outbound
  5. Push both artifacts to the run's outbox with simulated delivery