...
Parameter name | Description | Example | ||
Description | Free text for the exception rule | Field1 | ||
|---|---|---|---|---|
Expression Type | Expression type. Available options:
This field is optional for all interfaces where there is a single type of output. However, for interfaces that output might be both XML and flat file, it is mandatory to specify the expression type. | XPath | ||
Expression | Path pointing to the field/node where the exception should be applied. | //ORDER/DATE/text() (XPATH expression) or START_TAG(BGM+220+)&&END_TAG(+)&& (Flat file expression) or $.order.date (JSONPath expression) REGEX(BGM\+220\+(.*)\+) (REGEX expression) | ||
Rule | Rule to be applied to the field. | |||
| Marks the compared fields with yellow color as a "warning". | |||
| In case compared values are different Int4 Suite compares them with specified variable. If reference/current value pair from comparison matches variable values result is marked as "warning". Variable name used for checking the values has to be specified in the Processing Parameter column. | |||
| In case compared values are different Int4 Suite compares them with specified values in the Mapping Object. If reference/current value pair from comparison matches mapping values result is marked as "warning". Mapping Object name used for checking the values has to be specified in the Processing Parameter column. | |||
| Even if it is different in the content, it is not highlighted. | |||
| The difference will be highlighted green in the test report.
|
| ||
Parameter | Used in correlation with Warning Rules. |
...