Mapping guide: your fields to partner documents
Signal drafts the field mapping from your data to the partner's document format. You confirm it in Lab, prove it in Certification, and run it in Production — the mapping travels with the route as you promote.
1. Directions: OUTBOUND and INBOUND
OUTBOUND (Customer → Signal) maps your system payload — the typed JSON in the payload reference — into the partner's document. INBOUND (Signal → customer mapping) maps partner EDI back into your shape. Lab defaults to OUTBOUND; switch Direction in the Lab runner to test the other way.
2. Confirm in Lab
Open the mapping Signal drafted and confirm each field; correct any field marked Needs review. Press Test in Lab and run Typed JSON, Raw X12 850, and Raw EDIFACT ORDERS. A pass shows the mapped/transformed payload in the Lab result panel with partner contacted: false — mapping proof with no partner contact.
3. Certify the exact connection
Mappings are proven per connection, not per workspace: run partner test traffic from the Certification lane (/dashboard/lab?lane=certification) against the exact partner connection with real acknowledgments. With no ready connection the lane honestly reports No cert-eligible connection yet — keep proving the mapping in Lab meanwhile. SignalEDI never marks certification on its own; approval stays with the partner, in writing.
4. Run it in Production
The approved mapping ships on the immutable approved connection version. The Production lane stays Gated until Lab, Certification, approval, and the go-live gate are met — test traffic never runs from Production, and there is no fake runner.
Still have questions?
Email support@signaledi.com or open a ticket from Help & Support in the dashboard.
Contact support