The SelectionBase is a “super” class that eBiss uses to hold all the details of a message in memory. Parts of this information are first determined for an incoming message at the receiving channel or backendobjectReceiver. Then later when applying the EntityAnalyzer. Different complex types and data elements are populated at different times. Access to the SelectionBase can be used in the process context to use the MessageSelector Messages according to specific filter criteria via XPath Selections¹⁾.

The SelectionBase branches to:

1. /SelectionBase/InputMessages
2. /SelectionBase/OutputMessages

Here, message details of messages thrown against a job are in the /SelectionBase/InputMessages path, while messages generated within a job are instantiated in the /SelectionBase/OutputMessages path. Example: boolean check if the²⁾ message going to the job is a document with entity type “Document”. Message contains a Document with entity type “Edifact.Slsrpt.D96A”….

/SelectionBase/InputMessages/Documents/EntityType/@Name = "Edifact.Slsrpt.D96A"

Note: It allows e.g. a Alternative Select³⁾ of messages without the otherwise used EntitySelector.

Note: Using the GetMessageAsSelectionBase() function, messages or the XPath Selections be debugged in a suitable mapping.

Note: In the Managed File Transfer Context, the SelectionBase can also be applied to file information determined from a receive channel to the message. The file information is stored in the path

/SelectionBase/InputMessages/Attachments

and therefore e.g. the filename can be evaluated with:

/SelectionBase/InputMessages/Attachments/@Filename

.

Note: The SelectionBase cannot be accessed in a EntityIfCase because the EntityIfCase objects can only be applied after a EntityLoader and therefore they only see the document context.