ChangelogOctober 28, 2021
Sorted JSON
In order to make JEDI easier to read when it returns from our /translate endpoint, we have applied a custom sorting to the JSON renderer. JEDI will now order JEDI as the segments and elements are ordered in EDI. The order be will be preserved in node or browser applications. Other platforms may not keep the key ordering.
{
"interchanges": [
{
"ISA": {
"01": "00",
"02": " "
},
"groups": [
{
"GS": {
"01": "PO",
"02": "SENDERGS",
"08": "004010"
},
"transaction_sets": [
{
"heading": {
"010_ST": {
"01": "850",
"02": "000000001"
},
"020_BEG": {
"01": "00",
"02": "SA",
"03": "A99999-01",
"05": "19970214"
}
},
"detail": {},
"summary": {}
}
],
"GE": {
"01": "1",
"02": "1"
}
}
],
"IEA": {
"01": "1",
"02": "000000001"
},
"delimiters": {
"element": "*",
"segment": "~",
"sub_element": ">"
}
}
]
}
__version field in JEDI documents
__version
to the response of /translate.{
"code": "valid",
"output": {
"__version": "jedi@1.0",
"interchanges": {...},
"meta": {...},
},
}
Trimmed ISA white space in JEDI documents
Added new output option to trim the ISA whitespace if enabled. Today, the ISA in JEDI format looks like
"ISA": {
"01": "00",
"02": " ",
"03": "00",
"04": " ",
"05": "ZZ",
"06": "TCWDEPOT ",
"07": "ZZ",
"08": "FVLI0006 ",
"09": "210202",
"10": "0235",
"11": "U",
"12": "00200",
"13": "005787399",
"14": "0",
"15": "P",
"16": ":"
}
clean_envelope_whitespace
is set to true
, it instead outputs as:"ISA": {
"01": "00",
"02": "",
"03": "00",
"04": "",
"05": "ZZ",
"06": "TCWDEPOT",
"07": "ZZ",
"08": "FVLI0006",
"09": "210202",
"10": "0235",
"11": "U",
"12": "00200",
"13": "005787399",
"14": "0",
"15": "P",
"16": ":",
}
JSON EDI view in the Inspector
You can now toggle between "Rich view" and "JSON view" in the Inspector. The JSON view displays the EDI input in our custom JSON EDI (JEDI for short) format, along with the same annotations that were present in Terminal, for faster manual scanning of the file.

Support missing X12 003XXX versions
Faster EDI Inspector experience on the web
A missing header on responses from EDI Core meant that browsers would always need to issue two synchronous requests in order to translate and validate payloads in EDI Inspector. The addition of the missing headers speeds up the experience considerably, especially for users far away from Virginia, USA.