Payload Matching

Some integration scenarios permit one-to-many mappings. In such cases, there might be no guarantee that the integration platform will prepare messages in the same order as the historical flow. Payload matching allows for comparing the payloads in the same order. The solution is to sort the messages before comparison.

Parameter name	Description	Example
Rule	Free text for rule name	Rule1
Expression Type	Expression type. Available options: unspecified XPath Flat expression 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 Type	Rule type. Available options: Exact match - value from reference and current payload has to be the same Variable - value from reference and current payload is compared based on variable values and variable replacement Mapping object - value from reference and current payload is compared based on mapping object value replacement
Parameter	Additional parameter for Rule Type like Variable or Mapping Object name
Group	Free text grouping field. All rules with from the same group have to be fulfilled to match payloads. At least one group has to be fulfilled to match payloads. Rules within group are linked with AND operator. Groups are linked with OR operator.