EdiNation - Validate EDIFACT JSON
[ | version 3.1]
Connector
The connector is permitted for use of the platform background agent.
Connector processing type: Row by row!
Validates an EdifactInterchange object according to the EDIFACT standard rules for each version and transaction. Returns an OperationResult object with a status field and an array of error details if any.
For comprehensive details and additional configuration options, please refer to the EdiNation API documentation.
Configuration
EdiNation - Edifact Connection
Base URL: The base URL for connecting to the Edination service.
Authorization token: A token for authorizing access to the Edination
EdiNation - Validate EDIFACT JSON Settings
Error behavior: The available values are:
-
Fail and return response: The connector fails at the specified line but generates output with error details.
-
Fail without response: The connector fails - the error will be displayed only in the log.
-
Do not fail and return response: The connector does not fail but generates output records that may be marked with an error and detailed information.
Skip trailer: You are allowed to validate an EdifactInterchange with missing interchange, functional group, or transaction trailers (UNZ, UNE, UNT). This is because these will be automatically applied during the Write operation so you don't have to worry about counting the items. By default, it is expected that all trailers are present when you validate the EdifactInterchange and by default, this is set to false. To skip all trailer validation, set this to true.
Structure only: This is equivalent to HIPAA Snip level 1, where only the structure and control segments are validated. By default, this is set to false, however, if you want to not validate things such as data types, a number of repetitions, or dates, set this to true.
Use eancom 3: The default syntax for EANCOM transactions. By default, all EANCOM transactions will be validated according to the rules of Syntax 4. Set this flag to true if you need Syntax 3 to be used.
Decimal point: The available values are:
-
Point
-
Comma
Syntax set: In case you need to validate against a syntax set, different than UNOA and UNOB, populate this field with all of the allowed symbols, URL-escaped.
Input & Output Schema
Input
JSON (ver. 1.0.0)
| Column | Data type | Allow null | Description |
|---|---|---|---|
| JSON | JSON | No | Input/Output in JSON format |
Note
The input for this connector is a JSON object, which uses curly braces { } rather than square brackets [ ].
Output
EdiNation - EDIFACT Response
| Column | Data type | Allow null | Description |
|---|---|---|---|
| StatusCode | Integer | No | A numerical response from the server to an HTTP request sent to an API (see below). |
| JSON | JSON | Yes | The resulting JSON object produced from the API call |
| Message | String | Yes | If the Status is "error," the error message is displayed. |
| Status | String | Yes | The result of the EDIFACT to JSON conversion process |
Status Code
- 200 Success
- 400 Bad request - When the file stream is invalid or the form-data is not set properly.
- 500 Server error - Something went wrong on EdiNation's side.
Note
The API will respond with HTTP 200 OK even if the contents of the file can't be translated.
Release notes
3.1.3
- First release