[ 
https://issues.apache.org/jira/browse/FINERACT-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17729600#comment-17729600
 ] 

Muthu edited comment on FINERACT-1912 at 6/6/23 5:59 AM:
---------------------------------------------------------

[~peter.santa]  The current PR for this feature supports the following,
 # pagination
 # sorting
 # Filtering support for following
 ** transactionDate:

 * 
 ** 
 *** greather-than-or-equal
 *** less-than-or-equal
 *** greater-than
 *** less-than
 ** amount
 *** greather-than-or-equal
 *** less-than-or-equal
 *** greater-than
 *** less-than
 ** transactionType
 *** Multiple Transaction Types comma separated(deposit,withdrawal)


was (Author: JIRAUSER300189):
[~peter.santa]  The current PR for this feature supports the following,
 # pagination
 # sorting
 # Filtering support for following

 * 
 ** transaction date:
 *** greather-than-or-equal
 *** less-than-or-equal
 *** greater-than
 *** less-than
 ** amount
 *** greather-than-or-equal
 *** less-than-or-equal
 *** greater-than
 *** less-than
 ** transactionTypes
 *** Multiple Transaction Types comma separated(deposit,withdrawal)

> 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: Mihaly Dallos
>            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
>  * 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)

Reply via email to