X12 EDI Connector 2.7 - Reference - Mule 4

Name

String

The name for this configuration. Connectors reference the configuration with this name.

x

Expiration Policy

Configures the minimum amount of time that a dynamic configuration instance can remain idle before the runtime considers it eligible for expiration. This does not mean that the platform expires the instance at the exact moment that it becomes eligible. The runtime actually purges the instances as it sees fit.

Mule ID qualifier

ID qualifier for Mule in exchange (ISA segment). This value is used in combination with the Self Identification Interchange ID value, and if one is set the other must also be set. If this value is set, it affects both send and receive message handling. On the receive side, the ISA Interchange Receiver ID Qualifier must match this value. On the send side, this value is used as the default ISA Interchange Sender ID Qualifier when not set in the message data.

Mule interchange ID

ID for Mule in exchange (ISA segment). This value is used in combination with the Self Identification Interchange ID qualifier value, and if one is set the other must also be set. If this value is set, it affects both send and receive message handling. On the receive side, the ISA Interchange Receiver ID must match this value. On the send side, this value is used as the default ISA Interchange Sender ID when not set in the message data.

Mule application code

Application Code for Mule in group (GS segment). If this value is set, it affects both send and receive message handling. On the receive side, the GS Application Receiver’s Code must match this value. On the send side, this value is used as the default GS Application Sender’s Code when when not set in the message data.

Partner ID qualifier

ID qualifier for partner in exchange (ISA segment). This value is used in combination with the Partner Identification Interchange ID value, and if one is set the other must also be set. If this value is set, it affects both send and receive message handling. On the receive side, the ISA Interchange Sender ID Qualifier must match this value. On the send side, this value is used as the default ISA Interchange Receiver ID Qualifier when not set in the message data.

Partner interchange ID

ID for partner in exchange (ISA segment). This value is used in combination with the Partner Identification Interchange ID qualifier value, and if one is set the other must also be set. If this value is set, it affects both send and receive message handling. On the receive side, the ISA Interchange Sender ID must match this value. On the send side, this value is used as the default ISA Interchange Receiver ID when not set in the message data.

Partner application code

Application Code for partner in group (GS segment). If this value is set, it affects both send and receive message handling. On the receive side, the GS Application Sender’s Code must match this value. On the send side, this value is used as the default GS Application Receiver’s Code when not set in the message data.

Form and validation

Schema form and validation level. Schemas used in the configuration must match the form selected, either X12 or HIPAA. SNIP Type 1 and Type 2 validation only applies to HIPAA schemas.

X12

Schema definitions

List of paths for schemas to be used by connector. The paths may be either for file system or classpath.

x

Character encoding

Character encoding for messages. This character encoding is always used for both send and receive messages.

PLATFORM

Character set

Characters allowed in string data. Invalid characters are replaced by the substitution character, if used, or rejected as errors if no substitution character is set or enabled for receive messages in parser options. Either way the invalid characters are logged, and for receive messages are reported in 997 functional acknowledgments.

EXTENDED

Substitution character

Substitution character used to replace invalid characters in string values.

Version identifier suffix

Version identifier code suffix for group (GS segment). If this value is set, it affects both send and receive message handling. On the receive side, the the GS Version, Release, and Industry Identifier Code must consist of the X12 schema version (004010, 005010, etc.) followed by this suffix. If this value is not set, the receive only verifies that the GS version identifier code starts with the configured schema version. On the send side, the combination of the X12 schema version and this suffix is used as the GS version identifier code.

Timezone offset

String

Timezone offset from the UTC to apply to the date and time elements in the Interchange Header (ISA) segment. This field accepts only values compliant with ISO 8601 (which are UTC-based), for example, -01:00, +0100, -0130, and so on.

If you don’t specify a value for this field, the ISA segment date and time is set to the local date and time of the Mule runtime.

Enforce length limits

Enforce minimum and maximum lengths for Parser values. If true, a transaction with values too long or too short is rejected; if false, the values are used anyway and the transaction is not rejected. In either case the error is logged and reported in 997/999 acknowledgments.

Enforce minimum and maximum lengths for Writer values. If true, a transaction with values too long or too short is rejected; if false, the values are used anyway and the transaction is not rejected.

true

Enforce character set

Enforce allowed character set flag. If true, a transaction with invalid characters is rejected; if false, the characters are either passed through or substituted and the transaction is not rejected. In either case the error is reported in 997/999 acknowledgments.

true

Enforce value repeats

Enforce repetition count limits for receive values. If true, a transaction with values repeated too many or too few times is rejected; if false, the value are accepted and the transaction is not rejected. In either case the error is reported in 997/999 acknowledgments.

true

Allow unknown segments

Allow unknown segments in a transaction set. If false, a transaction containing any unknown segments is rejected; if true, unknown segments are ignored and the transaction is not rejected. In either case the error is reported in 997/999 acknowledgments.

false

Enforce segment order

Enforce segment order in a transaction set. If true, a transaction with segments out of order is rejected; if false and the segment can be reordered the transaction is not rejected. In either case the error is reported in 997/999 acknowledgments.

true

Allow unused segments

Allow segments marked as 'Unused' in a transaction set. If false, a transaction containing segments marked as unused in the schema is rejected; if true, the transaction is not rejected and the unused segments are ignored. In either case the error is reported in 997/999 acknowledgments.

false

Enforce segment repeats

Enforce segment repetition count limits in a transaction set. If true, a transaction with a segment repeated too many times is rejected; if false, the transaction is not rejected. In either case the error is reported in 997/999 acknowledgments.

true

Require unique interchanges

Require unique Interchange Control Numbers (ISA13) for received interchanges. The normal behavior is to record the interchange numbers previously processed and reject any duplicate interchange numbers from the same partner (as determined by the interchange sender and receiver identification). If false, this instead allows processing of the received interchange to continue and leaves it to the application flow to track numbers and handle appropriately.

true

Require unique groups

Enforce globally unique Group Control Numbers (GS06) for received functional groups. By default, group numbers only need to be unique with an interchange. If true, this instead requires group numbers to be unique across all interchanges received from the same partner and application (as determined by the interchange sender and receiver identification, combined with the functional group sender and receiver application codes).

false

Require unique transactions

Enforce globally unique Transaction Set Control Numbers (ST02) for received transaction sets. By default, transaction set control numbers only need to be unique with a particular functional group. If true, this instead requires transaction set numbers to be unique across all functional groups received from the same partner and application (as determined by the interchange sender and receiver identification, combined with the functional group sender and receiver application codes).

false

Store time-to-live

Minimum number of days to store interchange, group, and transaction set numbers for checking uniqueness. This value is only used when unique interchange, group, and/or transaction set numbers are required by the configuration. The default persistent object store from the Mule configuration is always used for storing the received identifier numbers, and this parameter sets the entry time-to-live for these stored values.

30

Acknowledge every transaction

Include a separate AK2/AK5 (997) or AK2/IK5 (999) acknowledgment for every received transaction set. By default, only transaction sets containing errors are included in the acknowledgment, with transaction sets which aren’t included implicitly acknowledged. Changing this flag causes each received transaction set to be explicitly acknowledged.

false

Generate 999 acknowledgments

Generate 999 Implementation Acknowledgments, rather than 997 Functional Acknowledgments. By default, 997 Functional Acknowledgment transaction sets are generated for each received interchange. Changing this flag causes 999 Implementation Acknowledgments to be generated instead. Note that the support for 999 Implementation Acknowledgments does not include CTX segment generation.

false

Report segment details

Report segment error details to sender in 997/999. If true, the details of any segment errors are included in a generated 997/999. If false, the details are not included.

true

Include Acknowledgment schema

Expect 997 or 999 Functional Acknowledgments and include 997/999 schema. By default, the schema for 997/999 acknowledgment transaction sets is automatically included in the set of schemas used by X12 Connector. If false, you need to directly specify the 997 and/or 999 schema if you want these to be processed as input. The schemas used for generating 997 or 999 Functional Acknowledgments are hardcoded and cannot be modified.

true

Data element separator

Data element separator character. The configured value is used by default for all output messages, but can be overridden at the message level.

*

Component element separator

Component element separator character. The configured value is used by default for all output messages, but can be overridden at the message level.

>

Repetition separator

Repetition separator character (if used). The configured value is used by default for all output messages, but can be overridden at the message level. The value 'U' means repetitions are not used.

U

Segment terminator

Segment terminator character. The configured value is used by default for all output messages, but can be overridden at the message level.

~

Segment line ending

Line ending to add between segments. This allows you to add line endings between segments to improve the readability of the output message text.

NONE

Unique group numbers

Send globally unique Group Control Numbers (GS06). By default, functional group control numbers are assigned sequentially within each interchange and are reused in different interchanges. If true, this instead assigns unique group numbers across all interchanges sent to the same partner and application (as determined by the interchange sender and receiver identification, combined with the functional group sender and receiver application codes).

false

Unique transaction numbers

Send globally unique Transaction Set Control Numbers (ST02). By default, transaction set control numbers are assigned sequentially within each functional group and are reused in different groups. If true, this instead assigns unique transaction set numbers across all interchanges sent to the same partner and application (as determined by the interchange sender and receiver identification, combined with the functional group sender and receiver application codes).

false

Implementation reference

Implementation convention reference for transactions (ST03). If this value is set, it is used as the ST03 Implementation Convention Reference unless overridden in the message parameters.

Initial interchange number

The initial Interchange Control Number used for outgoing messages.

1

Initial group number

The initial Group Control Number used for outgoing messages.

1

Initial transaction number

The initial Transaction Set Control Number used for outgoing messages.

1

Request acknowledgments

Request acknowledgments i.e. TA1 for sent transactions flag (ISA14). If true, TA1 acknowledgments are requested for all sent transactions.

false

Default usage indicator

Default interchange usage indicator (ISA15): I for Information, P for Production Data, and T for Test Data.

P

Acknowledgement schema path

Enforce conditional rules

Conditional rules are applied in a transaction. If true, a transaction with values not meeting conditional rules is rejected. If false, the values are used anyway and the transaction is not rejected.

false

Truncate values exceeding the length limits

Works when enforce length values are true. If true, values exceeding the maximum length are trimmed. If false, the values are written as-is.

false

Enforce code set validations

Boolean

If true, enforces code set validations, as defined in the X12 schemas.

false

Configuration

String

The name of the configuration to use.

x

Read Content

#[payload]

Target Variable

The name of a variable that stores the operation’s output.

Target Value

An expression to evaluate against the operation’s output and to store the outcome of that expression in the target variable.

#[payload]

Configuration

String

The name of the configuration to use.

x

Write Content

#[payload]

Streaming Strategy

Configure if repeatable streams should be used and their behavior.

Target Variable

The name of a variable that stores the operation’s output.

Target Value

An expression to evaluate against the operation’s output and to store the outcome of that expression in the target variable.

#[payload]

Configuration

String

The name of the configuration to use.

x

Write Content

#[payload]

Target Variable

The name of a variable that stores the operation’s output.

Target Value

An expression to evaluate against the operation’s output and to store the outcome of that expression in the target variable.

#[payload]