Background

Currently transactions of a Saving Account cannot be filtered - either all of them are in the response (using ...?associations=all), or none of them.

Pagination and sorting is not supported.

Goal

For Transactions related to - at least - Savings Account, support having:

pagination - following the concept in Fineract, implemented already for other entities
sorting - following the concept in Fineract, implemented already for other entities
- by ID - default
- by transaction.date - system time or business date specified by Fineract, when the transaction has been inserted
- by submittedOnDate - the date, specified in the REST request when initiating the transaction
filtering for
- transaction date:
  - greather-than-or-equal
  - less-than-or-equal
- amount
  - greather-than-or-equal
  - less-than-or-equal
- deposit/withdraw
- externalId - if FINERACT-1760 is already implemented

The filtering parameters should be applied with "AND" relation.

The response should have the transaction details on a similar way, as it is in the transactions array of:

<url>/savingsaccounts/<account_id>?associations=all

Have the solution concept aligned between

The API should support passing the required parameters.

Swagger:

is a child of

FINERACT-1917 Major improvement to Savings Account

FINERACT-1874 Release Apache Fineract 1.9.0

is related to

FINERACT-1943 Transaction query - Advanced - Extend filtering with submittedOnDate

relates to

FINERACT-1910 Data Table query - Advanced

links to

GitHub Pull Request #3158

(1 links to)