If SearchTableClass is set, use it to index any reply documents

List of properties can be set as settings in the configuration file format is a comma separated list of property names

This holds Reply Documents As EnsLib.EDI.Document

How to treat received batch Interchange documents:
- Whole Batch : Don't process child documents individually; accumulate and send the whole batch as one composite document
- Single-Session Batch : Forward each document in the batch as part of a single session, including a final parent document object containing the batch header and trailer segments
- Multi-Session Batch : Forward each document in the batch in its own session, followed by the parent document object containing the batch header and trailer segments
- Individual : Forward each child document in the batch in its own session; do not forward parent batch document objects

Category to apply to incoming EDIFACT document type names to produce a complete DocType specification.

Combines with the document type name to produce a DocType assignment. This setting may also contain multiple comma-separated type names followed by = and then a DocTypeCategory or full DocType value to apply to documents declared as that type.
A trailing asterisk (*) at the end of a given partial type Name will match any types with that beginning part.

An example: DocSchemaCategory='D96A, REC*=D04A, REQOTE=D05B'
Note that a DocType assignment may be needed for Validation or SearchTableClass indexing.

Colon-separated Local ID:Qualifier codes representing this (receiving) facility and application

These are used in constructing reply document headers.

The '@' symbol represents using the corresponding field from the incoming message.

If your ID must contain a literal @ symbol, escape it with backslash: '\@'

Control of response handling - Send back reply documents immediately upon receipt of an Interchange:
- Never : Do not send back any Immediate reply
- All : Generate a reply for every TransactionSet in an Interchange
- Errors : Only generate a reply for TransactionSets in which errors are detected
- Success : Only generate a reply for TransactionSets in which are accepted without errors

Store a set of searchable properties associated with each EDIFACT TransactionSet processed.

These records will be stored in the named SearchTable class, if any.

Configuration items to which to send Documents

Process the file without error even if to enhance readability newlines have been added after or in place of segment terminators

Comma-separated string specifying types of Validation to perform

Set to 1 to block documents that don't pass default validation. Default validation checks for DocType assignment and BuildMapStatus success. This is equivalent to 'dm'

'd' - require DocType
'm' - require successful BuildMap status

Is the current message the first in a batch? (used for starting a new session on the first message in a batch)

Return the segment terminator string that the Parser and the document.ImportFromIOStream() method will use.

Add discarded characters to IO Archive

Override this method to construct a customized batch reply document. Inputs are the original document and the child reply array and the status code that the framework produced in processing the original document.

Override this method to construct a customized reply document. Inputs are the original document and the reply code and the status code that the framework produced in processing the original document. If you change the status code but do not construct a reply document, the framework will use the new value to construct a standard reply document.

Callbacks from Parser: Called by the Parser at the end of a document

Return an array of connections for drawing lines on the config diagram

This user callback method is called via initConfig() from %OnNew() or in the case of SOAP Services from OnPreSOAP()

Note: pDocIn is not declared as EnsLib.EDI.EDIFACT.Document so that subclasses can handle other types and transform them before calling ##super().

Override this method to implement your own custom method for resolving the DocType of an incoming Message Returning nonzero means you are overriding the framework's standard DocType resolution.

Override this method to implement your own custom method for validating an incoming Document Return non-zero to prevent default validation of the message (if any);

Accept only specified document names; resolve DocType and perform requested validation if any

Return the DocType that this service will assign to this document