Possible duplicate check

The possible duplicate check validation is comparable with the functional duplicate check in the workflow, but more lightweight: the list of criteria used during this duplicate check is smaller (for example data owner is not considered), ranges on dates and amounts cannot be used.

Similar to the functional duplicate check, it uses an application property called ‘manual.duplicate.validation.criteria’, which contains a comma-separated list of jxpath-criteria on the payment. These criteria are taken into consideration when the duplicate validation is performed. A hash is calculated based upon these criteria and is persisted on the payment when the payment is persisted. Be aware that this duplicate check only considers manually created payments, payments introduced in the system via another channel are ignored.

Important remark: When the list of criteria is changed, even if it’s only the order of the criteria, the hash of the existing payments will become obsolete because the calculation of the hash will be different, even if the payment contains the same data.

If the validation fails on the duplicate check, the user will be presented with a warning screen:

The user has now the same options as for the requested execution date.