You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Peter Santa (Jira)" <ji...@apache.org> on 2023/04/04 14:08:00 UTC
[jira] [Updated] (FINERACT-1912) Have advanced features for Transaction querying
[ 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
Foe 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:
*** from
*** to
** amount
*** from
*** to
** deposit/withdraw
** externalId - if FINERACT-1760 is already implemented
h1. Solution Concept
Have the solution aligned with the solution of FINERACT-1910.
The API should support passing the required parameters.
h2. Request parameters
|| Parameter||Mandatory/Optional|| ||
|trxDateFrom|optional|inclusive|
|trxDateTo|optional|inclusive|
|creditDebitIndicator|optional|Deposit or withdraw|
|trxAmountFrom|optional|inclusive|
|trxAmountTo|optional|inclusive|
|externalId|optional| |
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
Foe 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:
*** from
*** to
** amount
*** from
*** to
** deposit/withdraw
** externalId - if FINERACT-1760 is already implemented
h1. Solution Concept
Have the solution aligned with the solution of FINERACT-1910.
The API should support passing the required parameters.
h2. Request parameters
|| Parameter||Mandatory/Optional|| ||
|dateFrom|optional|inclusive|
|dateTo|optional|inclusive|
|creditDebitIndicator|optional|Deposit or withdraw|
|amountFrom|optional|inclusive|
|amountTo|optional|inclusive|
|externalId|optional| |
> Have advanced features for Transaction querying
> -----------------------------------------------
>
> Key: FINERACT-1912
> URL: https://issues.apache.org/jira/browse/FINERACT-1912
> Project: Apache Fineract
> Issue Type: New Feature
> Components: Savings
> Reporter: Peter Santa
> Priority: Major
>
> 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
> Foe 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:
> *** from
> *** to
> ** amount
> *** from
> *** to
> ** deposit/withdraw
> ** externalId - if FINERACT-1760 is already implemented
> h1. Solution Concept
> Have the solution aligned with the solution of FINERACT-1910.
> The API should support passing the required parameters.
> h2. Request parameters
> || Parameter||Mandatory/Optional|| ||
> |trxDateFrom|optional|inclusive|
> |trxDateTo|optional|inclusive|
> |creditDebitIndicator|optional|Deposit or withdraw|
> |trxAmountFrom|optional|inclusive|
> |trxAmountTo|optional|inclusive|
> |externalId|optional| |
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)