| Batch Transactions | An interchange can contain multiple transactions. When this is not checked, the connector creates a separate output file for each transaction in the interchange. When checked, the connector groups all transactions into a single output file. Only applicable when the Translation Type is TRADACOM to XML. |
| Encoding | Specifies the character encoding (such as ASCII or UTF-8). |
| Expand Qualifier Values | When checked, XML elements containing an EDI qualifier include child elements containing the qualifier code and value. Only applicable when the Translation Type is TRADACOM to XML. For example:
<N101>
<Code>ST</Code>
<Value>Ship To</Value>
</N101> |
| Generate Description As | When translating TRADACOM into XML, descriptions of the TRADACOM segments and elements can be provided as context for the TRADACOM data. Use this dropdown to choose whether to add this context as an XML comment or as XML attributes. |
| Local File Scheme | A scheme for assigning filenames to messages that are output by the connector. You can use macros in your filenames dynamically to include information such as identifiers and timestamps. For more information, see Macros. |
| Nest Loops | When checked, the connector detects EDI structures that have hierarchical relationships embedded in the EDI data, and generates XML with these hierarchical relationships represented as parent-child relationships. |
| Processing Delay | The amount of time (in seconds) by which the processing of files placed in the Transactions tab is delayed. This is a legacy setting. Best practice is to use a File connector to manage local file systems instead of this setting. |
| Strict Schema Validation | Whether the connector should Ignore, Warn, or Fail when the following are detected: repeat counts above the allowed number, missing required elements or segments, invalid qualifier and code values, disallowed element lengths, and invalid element values. Choosing Disable turns off the schema validation checks. |
| Track Transaction Types | Whether to add transaction types as tracked headers to processed messages. |
| Validate Identifiers | Check this to ensure that the identifiers in the translated document match the identifiers in the connector’s configuration. |
| Duplicate File Action | How the connector should behave when it receives a message with a control number that the connector has seen before (a duplicate). When set to Ignore, the connector silently skips the duplicate and continues processing. When set to Warn, the connector processes the file but returns a warning. When set to Fail, the connector does not accept the file and returns an error. |
| Upload Schema | Use this to upload a schema and install it in the connector’s Schema folder. If a schema already exists, you are asked if you want to overwrite it. |
| Reset State | EDI connectors keep track of control numbers that have been used and increment that number to ensure that future runs do not duplicate data. Use this button to reset the counter to its initial state without changing any of the configured settings. |
