Query regex matching strategies

Use RSQL query language. Intro here: https://aboullaite.me/rsql/.

Zero-based page index (0..n). Default is 0.

Size of the page to be returned. Max page size allowed is 100, default is 10.

A list of one or more sorting criteria each in the format 'property(,asc|desc)' with direction being case-insensitive.
If sorting direction is not provided, default direction is 'asc'.
Default sorting criteria: 'ident'.

Standard response for successful HTTP requests.

Meta data about the current page and query.

Size of the page as specified by the query.

Page number of total pages available.

Total count of all elements available for the query.

Total count of all pages available for the query.

Type of the assignment target ident, i.e. is it the ident of an ORDER or the ident of a DOCUMENT.

NOTE: This does not necessarily need to be the actual targetType of the resulting assignments, as for the ident of orders with a single associated document the payment will be assigned to the document instead.
Must not be null.
Must be one of:

DOCUMENT

ORDER

Should the strategy fail instead of searching an target for each regex match if the regex matched multiple times.

Specifies the regular expression that we will try to find in payment description.
Must not be empty.
Size must be between 0 and 255.

If specified, this will be used instead of the regular expression's match to search for the ident. Supports referencing capture groups, e.g. $123 or ${name} and $ can be escaped with \$.
Example:

with a payment description of INV/01234567/89
a regularExpression of (\d*)/(\d*) would match 01234567/89, with the capture groups 01234567 and 89
a replaceWith of $1-$2 would yield 01234567-89

Therefor the payment would be assigned to an invoice with ident 01234567-89.
Size must be between 0 and 255.

Unique ident of the matching strategy.
Must have size between 1 and 100 and match with the regular expression '[a-zA-Z0-9_.~-]{1,100}'.

error response for all http error codes in range 4XX

textual representation of http status code, e.g. 'BAD_REQUEST' for status code 400

message describing the error

timestamp in UTC when the error occurred

URL path where the error occurred

UUID generated by the server to identify the error occurred, should be stated in case of any inquiries

optional list of multiple errors occurred

error response for all http error codes in range 5XX

textual representation of http status code, e.g. 'BAD_REQUEST' for status code 400

message describing the error

timestamp in UTC when the error occurred

URL path where the error occurred

UUID generated by the server to identify the error occurred, should be stated in case of any inquiries

optional list of multiple errors occurred

200Standard response for successful HTTP requests.

4XXerror response for all http error codes in range 4XX

5XXerror response for all http error codes in range 5XX