====== EntityAnalyzer ====== The job step EntityAnalyzer is the most important component in the process automation. It analyzes the content of an entity (sender, recipient, document, file, mail, attachment, etc.) by means of type repository definitions and creates the necessary interchange or document definitions. The information of the currently used analyzer is used in the repository. ~~ GENERATED src="eBiss.ClassLib.Resources.JobSteps.EntityAnalyzer" changed="" ~~ ^Properties^^ ^Name^Description^ |**Type**|Class name of the jobstep| |**Name**|Name for the jobstep that will appears in the job designer| |**Description**|Optional description for the jobstep| |**Analyze interchange only**|Stop analyse after interchange was analysed. Only interchange check and partner identification will be done, no documents will be created!| |**Switch sender and recipient**|In some cases, sender and recipient recognition must be switched| |**Partner connection handling**|Options are: | |**Repository**|Use only this repository| |**Defined analyzer**|If the repository is selected, then an analyzer can be selected from it. Then only this analyzer will be used. Name changes of the repository and/or the analyzer as well as the change of the repository property are not automatically corrected and require an adjustment!| |**Extended Tasks**|A task is created if the partner found does not match the partner already set.| |**Force Analyze**|Analyze the message in any case, also if already analyzed. The default value is false.| For the EntityAnalyzer jobstep to examine the entities, the entity needs the repository objects (Recognizer, Analyzer, Entitytypes). Depending on the format of the entity (character string, binary format), the relevant recognizer is assigned. This returns a Recognizer instance either for character strings, or for binary formats. The Recognizer instance is used to search all associated Analyzer objects of the Recognizer within the EntityAnalyzer job step until the correct one is found and assigned. The analyzer examines the entity according to its type (Interchange, document). In an Interchange, the corresponding communication partners are identified from the entity and the entity is stored in the database. For a document, this is created in the database. {{:images:sign_warning.png?nolink|}}**Note:** If a message is not recognized by the analyzer, this can have various causes. The following chapter deals with the common causes.\\ ===== Common Errors ===== * There is no active detection component for the current message direction. * The character encoding is not recognized. * The type is recognized, but the read component throws an error. That the reading component has an incorrect od. No automatic character code setting. * The file mask in the recognition component does not match the current file name. * The MatchString in Recognizer is not found. * The detection type is set incorrectly. * The priority of the detection component is set too low. * This type is unknown to the analyzer. That The entity type assignment is missing in the analyzer. * The entity type is not known in the repository. * The job step analyzer is restricted to a specific repository and the current message type is not part of it. ===== The following JobSteps are usually connected to the EntityAnalyzer ===== * [[en:prozessdefinition:jobs:jobsteps:kommunikation:channelreceiver]] * [[en:prozessdefinition:jobs:jobsteps:kommunikation:channelsender]] * [[en:prozessdefinition:jobs:jobsteps:allgemein:delegatorjob]] * [[en:prozessdefinition:jobs:jobsteps:allgemein:EntitySelector]] * [[en:prozessdefinition:jobs:jobsteps:allgemein:MessageSelector]] * [[en:prozessdefinition:jobs:jobsteps:allgemein:TaskNotificatorEx]] * [[en:prozessdefinition:jobs:jobsteps:allgemein:ValueProviderUpdateJob]] * [[en:prozessdefinition:jobs:jobsteps:supplier:tradeitemmanagerfillcache]]