This component requires no authentication.
EDIFACT Parser component expects an incoming message(es) with EDI attachment(s) in it. You can test it using SFTP component like this:
Sample example:
{
"result": [
{
"elements": [
["UNOA", "1"],
["005435656", "1"],
["006415160", "1"],
["060515", "1434"],
["00000000000778"]
],
"name": "UNB"
}
]
}
Sample EDI files you can find here, and here you will see resulting JSON message body after parsing.
The technical notes page gives some technical details about Edifact-parser component like changelog.
This component has no trigger functions. This means it will not be accessible to select as a first component during the integration flow design.
EDIFACT Parse action expects an incoming message(es) with EDI attachment(s) in it.
Sample EDI file you can find here, and here you will see resulting JSON message body after parsing.
Click here to learn more about the elastic.io iPaaS