Advanced Settings

In addition to the basic/mandatory configurations mentioned in the basic account set-up guide, you can adjust several other account-level settings to fine-tune the way that EDI Generator will handle your EDI transactions.

Processing

This section mainly controls how EDIG will process incoming documents on your account, send back responses, etc.

Preserve CR/LF characters (newlines) in incoming files

By default, the EDI Generator will remove the CR/LF characters (newlines) from the incoming EDI files before processing them. This setting can be enabled to omit that and step and preserve those characters for the processing. This setting must be enabled, if your partner is using newline as the segment separator.

Outgoing Filename Format

Controls naming format of outgoing files (e.g. invoices generated from the web interface, or EDIs composed from outbox).

If not specified, EDIG will use the default format ${txnType}${displayType}_${timestamp}.edi.txt

Response Filename Format

Controls naming format of files that are sent back as a response to an originally incoming file (e.g. auto-generated X12 997 initial ACK, for an incoming PO). If not specified, EDIG will use the Outgoing Filename Format itself, or fall back to the latter’s default.

Ignore incoming documents from

If you receive EDIs from some sender, that you wish to ignore/skip processing, but have no other way to prevent them from being pushed to EDIG, you can specify such senders’ ISA identifiers here. EDIG will completely skip ingesting of files that match these ISAs, without processing/forwarding them further or saving them in your inbox.

Process incoming EDIFACT files

Turn this on to enable accepting and processing of EDIFACT files, in addition to X12. Currently, EDIG offers limited support for handling EDIFACT files, including JSON conversion based on partner/document type definitions, and forwarding to external integrations. When EDIFACT support becomes mainstream, the setting may be removed from this section.

File naming

Files sent out by EDIG are named using a common naming standard, configurable under Processing section of your organization configuration. You can use following placeholder expressions to insert contextual details to the filename, such as timestamps and sender/recipient identification values.

Partner references (partner.<fieldName>): supported fields

These come from the associated partner, e.g. the final intended recipient of a document generated by EDIG. Use these fields if you wish to adjust the filename based on each recipient, or if your partner expects any of their identification information (such as their own AS2 ID, or ISA/GS identifiers) on the files that you send to them.

Following fields are also available, however they would generally not be suitable/meaningful for use in filenames; you may be able to use some of them, such as the description, to pass more contextual (per-partner) information to the filename generation step:

Tenant references (tenant.<fieldName>) supported fields

These come from your tenant/organization settings. Use these fields if you wish to include your own identification information (such as your AS2 ID, or ISA/GS identifiers) on the files that you send to your partners (or if your partner has requested you to do so).

Following fields from your account configuration are also available, however they would generally not be suitable/meaningful for use in filenames:

Response file naming

Sometimes an EDI file may be sent as a direct response to an incoming document, i.e. it is directly associated with an “original” document. This setting allows you to further customize the names of such “response” files, by including metadata/fields from the original document.

In addition to fields described above under File naming, you can use an ${original.<fieldName>} syntax to include desired properties of the original document into the final filename.

Document references (original.<fieldName>): supported fields

Following fields are also available, however they would generally not be suitable/meaningful for use in filenames: