Profile scoring

Input Agents can be configured to accept incoming data only if certain parameters match. Depending on the type of the Input Agent, those are file names, sender ID, the MIME type of the mail body, etc.

It is possible that several active profiles are eligible to receive a specific message when the conditions are overlapping. In order to select the profile that is most suitable, a scoring is carried out for the matching profiles. The scoring is performed for the following Input Agents/data sources.


  • Input Agent "AS2"

  • Input Agent "SMTP"

  • Input Agent "FTP"

  • Input Agent "OFTP"

  • Input Agent "SSH"

Scoring rules


  • Only those profiles that match the message are considered.

  • More precise information has priority over inaccurate information. Example: Two profiles with Input Agents of type AS2 process files that match the file pattern * (so all files). One profile has a specified subject, the other does not evaluate the subject. If a message with a matching subject is received, the profile that evaluates the subject will be started.

  • Stronger matchings have priority over lesser ones. Example: We have a profile with file pattern * and another one with file pattern *.txt. If an incoming message contains a file abc.txt, the message will be processed by the profile with file pattern *.txt. If the file has the name abc.xml, only the profile with the file pattern * will match and be used for the processing.

  • The individual parameters have different weights.

  • Strong weighting for address information/optional sender identification.

  • Medium weighting for the subject (for email) and the path (for FTP).

  • Weak weighting for the file pattern.


The following scenario is intended to provide a better understanding.

A communication partner sends emails that contain either an invoice or an invoice cancellation in the email body. Both document types have a different structure and therefore have to be processed by different profiles. The email sender and recipients are the same for both document types. The subject line is either Invoice or Invoice Cancellation. The subject is checked with operator contains.

Two profiles are created that only differ in the evaluation of the email subject. One with the comparison term Invoice, the other with Invoice Cancellation.

If an email with subject Invoice Cancellation is received, both profiles match at first. However, only the profile with comparison term Invoice Cancellation is started, because it matches the subject more precisely. If an email with the subject Invoice is received, only the other profile matches.

Scoring examples

Example 1


Incoming email with subject Hello world and attachment 1234.txt


Profile A: The pattern for the subject is Hello* and the file pattern is 123*
Profile B: The pattern for the subject is Hello w* and the file pattern is 1*


Profile B is used because the subject matches more precisely there and the subject is 'more important' in the scoring than the file pattern.

Example 2


FTP (inbound): Uploaded file in /data/sample.txt


Profile A: No path is specified and the file pattern is *.txt
Profile B: The path is specified as /data and the file pattern is *.*


Profile B is used here as well because a specified path is weighted higher than the file pattern.


Note: The add-on module "Data Flow" enables you to simulate which profile is going to receive a specific message.