[
https://issues.apache.org/jira/browse/FINERACT-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Santa updated FINERACT-1912:
----------------------------------
Description:
h1. 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.
h1. 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 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 to perform a
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>{}}}{color:#212121}/savingsaccounts/<{color}{{{}account_id>{}}}{color:#212121}?associations=all{color}
h1. Solution Concept
Have the solution concept aligned between
* FINERACT-1910
* FINERACT-1912
* FINERACT-1915
The API should support passing the required parameters.
<Solution Concept to be extended by developers>
was:
h1. 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.
h1. 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
* 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>{}}}{color:#212121}/savingsaccounts/<{color}{{{}account_id>{}}}{color:#212121}?associations=all{color}
h1. Solution Concept
Have the solution concept aligned between
* FINERACT-1910
* FINERACT-1912
* FINERACT-1915
The API should support passing the required parameters.
<Solution Concept to be extended by developers>
> Transaction query - Advanced
> ----------------------------
>
> Key: FINERACT-1912
> URL: https://issues.apache.org/jira/browse/FINERACT-1912
> Project: Apache Fineract
> Issue Type: New Feature
> Components: Savings
> Reporter: Peter Santa
> Assignee: James Dailey
> Priority: Major
> Labels: BeanSalad
>
> h1. 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.
> h1. 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 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 to perform a
> 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>{}}}{color:#212121}/savingsaccounts/<{color}{{{}account_id>{}}}{color:#212121}?associations=all{color}
> h1. Solution Concept
> Have the solution concept aligned between
> * FINERACT-1910
> * FINERACT-1912
> * FINERACT-1915
> The API should support passing the required parameters.
> <Solution Concept to be extended by developers>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
