Accept All Files Inspector

Apart from the description (mandatory), no configuration is necessary here. All files (empty files also) are accepted by this File Inspector.

Accept Empty Files Inspector

Apart from the description (mandatory), no configuration is necessary here. Only empty files are accepted by this File Inspector. A file is also considered empty if it only consists of spaces.

EDIFACT Inspector

The EDIFACT Inspector checks the EDIFACT message for specified values of, for example, sender, receiver, type, version, release and organisation. The wildcard "*" means that all values are allowed. All input fields can also contain regular expressions. Please use the prefix "regex:".

(1) Sender: You can also use placeholders for additional IDs from the Partner Administration (also applies to recipient). This allows you to generally configure the File Inspector. The specific values then come from the partner channels assigned to the Content Inspector. Example: "@partner:ILN@".

(2) Release: Several allowed releases can be specified, separated by a semicolon (;). Example: "96A".

(3) USH segment: Settings for signed EDIFACT. Selectable values are Possible, No, Mandatory.

IDoc Inspector

The IDoc Inspector checks the fields of the IDoc header segment against the specified values.

JSON Inspector

The JSON Inspector checks if the mandatory JSONPath expressions return a non-empty result.

(4) Mandatory: Marks whether a JSONPath expression is mandatory.

(5) JPath: The JSONPath expression that is applied to the JSON document. Note: See function execute json xpath() for an example to the JSONPath expression shown here. Example: $.store.book[*].author

PDF Inspector

Apart from a description (mandatory), no configuration is necessary here. The PDF Inspector checks if this is a PDF file.

Plain Text Inspector

The Plain Text Inspector checks the entire plain text file line by line to see if the defined rules apply. A new rule can be created via the context menu and is defined by items (1) through (4).

(6) Rule type: There are three types of rules: Is in message, Is start of message, Is end of message.

(7) Condition: Possible condition values are

• begins with

• ends with

• contains

• equals

• regex (regular expression)

(8) Value: The value to compare with.

(9) Start , End: If > 0, only the substring between these indices (starting with 1) is compared during the line by line reading in of the data. Note: Start value must be smaller than the end value.

The plain text file is read in line by line. The order in the list of rules is not relevant for the overall evaluation.

If there are only rules of type Is in message, the overall evaluation is true if one of these rules is true.

If there is at least one rule of type Is start of message, one of these has to be true and there also has to be at least one rule of type Is end of message, which also has to be true for the overall evaluation to be true. Rules of type Is in message will be ignored.

If there is at least one rule of type Is end of message and there is no rule of type Is start of message, at least one rule of type Is end of message has to be true for the overall evaluation to be true. Rules of type Is in message will be ignored.

Regex Inspector

A regular expression can be specified in this file inspector to check the entire file. Example: ^.*somekeyword.*

Tradacoms Inspector

(10) Description: Must be filled in as a mandatory field. All remaining field comparison values are optional. The wildcard * means that all values are allowed.

X12 Inspector

(11) Key icon: You can also use placeholders for additional IDs from the Partner Administration. This allows you to generally configure the File Inspector. The specific values then come from the partner channels assigned to the Content Inspector. Example: "@partner:ILN@".

Apart from the description, all other field comparison values are optional. The wildcard * means that all values are allowed.

XML Inspector

The XML Inspector checks if the mandatory XPath expressions produce subnodes.

(12) Mandatory: Marks whether an XPath expression is mandatory. Note: One of these mandatory entries must at least be specified.

(13) XPath expression: The XPath expression that is applied to the XML document. Example: "/ORDERS/ORDER".

XML V4 Inspector

Needs the (separately licensed) XML V4 parser. Otherwise, has to be configured like the XML Inspector but, just like the XML V4 parser, is much faster.