[
https://issues.apache.org/jira/browse/FINERACT-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Santa updated FINERACT-1915:
----------------------------------
Description:
h1. Prerequisites
FINERACT-1911
FINERACT-1910
h1. Goal
Make it possible to filter *Transactions* of Savings account with one request,
that includes conditions for
* attributes of the Transaction itself,
* attributes of the related data tables
The filtering parameters should be applied with "AND" relation.
The *result set should contain* data from the *assigned data table* besides the
Transaction attributes, considering the requested attributes.
h1. Solution Concept
Have the solution concept aligned between
* FINERACT-1910
* FINERACT-1912
* FINERACT-1915
For providing the query parameters, have a similar solution to FIENRACT-1910 ,
but let the caller specify sections in the body for each related data table,
specifying the identifier of the related data table.
Include the requested attributes in the response from the associated data table.
<Solution Concept to be extended by developers>
h1. Notes
Requirements for enhanced result set is included in FINERACT-1916, it might
worth to consider.
h1. Acceptance Criteria
* It is supported to query for {*}transactions{*}, that meets the defined
conditions, and the assigned data table records meets the defined conditions.
* The conditions in the request are defined on a way as the prerequisite
FINERACT-1910 does, and additionally to that it lets the caller specify
sections in the body for each related data table, specifying its name.
* The result set contains the requested attributes from the *assigned data
tables* also.
was:
h1. Prerequisites
FINERACT-1911
FINERACT-1910
h1. Goal
Make it possible to filter *Transactions* of Savings account with one request,
that includes conditions for
* attributes of the Transaction itself,
* attributes of the related data tables
The filtering parameters should be applied with "AND" relation.
The *result set should contain* data from the *assigned data table* besides the
Transaction attributes, considering the requested attributes.
h1. Solution Concept
Have the solution concept aligned between
* FINERACT-1910
* FINERACT-1912
* FINERACT-1915
For providing the query parameters, have a similar solution to FIENRACT-1910 ,
but let the caller specify sections in the body for each related data table,
specifying the identifier of the related data table.
Include the requested attributes in the response from the associated data table.
<Solution Concept to be extended by developers>
h1. Notes
Requirements for enhanced result set is included in FINERACT-1916, it might
worth to consider.
h1. Acceptance Criteria
* It is supported to query for transactions, that meets the defined
conditions, and the assigned data table records meets the defined conditions.
* The conditions in the request are defined on a way as the prerequisite
FINERACT-1910 does, and additionally to that it lets the caller specify
sections in the body for each related data table, specifying its name.
* The result set contains the requested attributes from the assigned data
tables.
> Transaction query - considering assigned data table
> ---------------------------------------------------
>
> Key: FINERACT-1915
> URL: https://issues.apache.org/jira/browse/FINERACT-1915
> Project: Apache Fineract
> Issue Type: New Feature
> Components: Savings
> Reporter: Peter Santa
> Priority: Major
> Labels: BeanSalad
>
> h1. Prerequisites
> FINERACT-1911
> FINERACT-1910
> h1. Goal
> Make it possible to filter *Transactions* of Savings account with one
> request, that includes conditions for
> * attributes of the Transaction itself,
> * attributes of the related data tables
> The filtering parameters should be applied with "AND" relation.
> The *result set should contain* data from the *assigned data table* besides
> the Transaction attributes, considering the requested attributes.
> h1. Solution Concept
> Have the solution concept aligned between
> * FINERACT-1910
> * FINERACT-1912
> * FINERACT-1915
> For providing the query parameters, have a similar solution to FIENRACT-1910
> , but let the caller specify sections in the body for each related data
> table, specifying the identifier of the related data table.
> Include the requested attributes in the response from the associated data
> table.
> <Solution Concept to be extended by developers>
> h1. Notes
> Requirements for enhanced result set is included in FINERACT-1916, it might
> worth to consider.
> h1. Acceptance Criteria
> * It is supported to query for {*}transactions{*}, that meets the defined
> conditions, and the assigned data table records meets the defined conditions.
> * The conditions in the request are defined on a way as the prerequisite
> FINERACT-1910 does, and additionally to that it lets the caller specify
> sections in the body for each related data table, specifying its name.
> * The result set contains the requested attributes from the *assigned data
> tables* also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
