EdiNation - Acknowledge EDIFACT JSON
[ | version 3.0]
Connector
The connector is permitted for use of the platform background agent.
Connector processing type: Row by row!
Generates an EdifactInterchange object that contains the functional and/or technical CONTRL acknowledgment(s) for the requested EdifactInterchange. The resulting EdifactInterchange uses the UNB and UNG (optional) of the request, with the sender and receiver id/qualifier exchanged.
For comprehensive details and additional configuration options, please refer to the EdiNation API documentation.
Configuration
EdiNation Acknowledge 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.
Detect duplicates: If you need to detect duplicates as in functional groups or transactions with the same reference number, set this flag to true. The default is false.
Transaction reference number: The default is 1. Set this to whatever the CONTRL UNH.MessageReferenceNumber_01 needs to be.
Interchange reference number: The default is 1. Set this to whatever the CONTRL EdifactInterchange.UNB.InterchangeControlReference_5 needs to be.
Acknowledgment for valid transactions: The default is false. Set this to true if you need UCM loops included for all valid transactions as well. By default, UCM loops are generated only for invalid transactions.
Batch acknowledgments: The default is true. Set this to false if you need to generate separate EdifactInterchange for each acknowledgment. By default, all acknowledgments are batched in the same EdifactInterchange.
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.
Technical acknowledgment: The available values are:
-
Default: Generate technical CONTRL according to AcknowledgementRequest_9
-
Enforce: Always generate technical CONTRL
-
Suppress: Never generate technical CONTRL
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.
EdiNation - Edifact Connection
Base URL: The base URL for connecting to the Edination service.
Authorization token: A token for authorizing access to the Edination
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.0.1
- First releasae