[
https://issues.apache.org/jira/browse/FINERACT-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732512#comment-17732512
]
Peter Santa commented on FINERACT-1911:
---------------------------------------
Hi [~bgowda] ,
At a bank there could be use cases, when every transaction has extra
attributes, that are not so general to extend the Fineract's Transaction entity
with them. Some of them could be relevant, if the use case is not a
Fineract-to-Fineract transfer, but between banks, identifying the accounts with
IBANs or other region-specific identifier; or there could be other reasons to
give more attributes to transactions. E.g.:
* debtorIban - IBAN of the debtor's account
* creditorIban - IBAN of the creditor's account
* correlationId - that collects transactions together (e.g. a "main"
transaction and the related transaction-fee)
* settlementDate - in a bank-to-bank transfer, the date then the Clearing and
Settlement Mechanism moved the amount from a bank's account to another one's
* other transaction related attributes...
But, we do not want to extend the Transaction (or whatever it's called in
Fineract) with these attributes, because not all Fineract users would like to
have them, and the list of these attributes might change as new requirements
come, or if other project begins for other customer.
So the idea is to have data table for Transaction entity, instead of the
Savings account (as it is currently).
Best Regards,
Péter
> Assign Data Table to Transaction (Savings)
> ------------------------------------------
>
> Key: FINERACT-1911
> URL: https://issues.apache.org/jira/browse/FINERACT-1911
> Project: Apache Fineract
> Issue Type: New Feature
> Components: Data Tables
> Reporter: Peter Santa
> Priority: Major
> Labels: BeanSalad
>
> h1. Background
> Currently data tables can be assigned to several entity types, but
> transaction is not an option.
> h1. Goal
> The context is mainly Transactions of {*}Saving Accounts{*}, but it would be
> great to implement the feature generally.
> The goal would be to make it possible to
> * {*}assign data table to transactions{*}, and
> * support multi-row and single-row tables - as it is already supported for
> data tables that could be assigned to other entities.
> h1. Acceptance Criteria
> * it is supported to assign *data tables to Transaction entities* of - at
> least - savings accounts, and the solution fits into the current data table
> conception
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
