Create Recognizer

To create a new recognizer, right-click the recognizer component node and choose Create from the context menu. Then fill in the fields of the recognizer.

Name Meaning
NameName of the recognizer.
ActiveIf the checkmark is set, the recognizer is active.
communication directionCommunication direction to the reference system (e.g. merchandise management or similar).
Inbound : DDocuments are loaded into the reference system.
Outbound : Documents leave the reference system.
Recognizer typesAnsiX12,ediBoxInhouse1),Edifact,VDAFlatFile,Xml, InternalXml2),Json,Text,TexWeave,Tradacoms
File Mask Under File Mask and MatchString you can enter a mask to select the entities / files / messages. File mask checks the file name for contents of the Regular Expressions stored there. If these are the same, the current file is processed.
MatchStringLoads the content of the file, at most the first 16384 characters, and compares it with the stored regular expression. If these are the same, the current file is processed.
character encodingFor character encoding, select the expected encoding.
priorityIf several recognizers apply, you can use the priority to control the order of processing. The greater the value, the higher the priority, i. e. the one with the highest value in the priority is used first.
ActiveHere the detection component can be switched on or off.
communication direction The recognition component is directly dependent on the communication direction ((This leads to misunderstandings if messages are not successfully analyzed but a recognition component is stored in the analyzer, but the communication direction does not fit). (INBOUND/OUTBOUND)

Complete your entries by clicking on Save, so that the new recognition component is transferred to the eBiss database.

Note:Character encoding may vary depending on the sender of the message. To enable reading of different character encodings, the setting Recognize character encoding can be set to Yes.

1)
A specific format of the outdated ediBox.
2)
Analog XML, but for middelware objects encapsulated with an interchange. To be used for the transfer of middleware documents between different nodes.