You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Benura Abeywardena (Jira)" <ji...@apache.org> on 2021/10/26 12:27:00 UTC
[jira] [Commented] (FINERACT-1417) Introduce a new pivot date to
filter the savings transactions.
[ https://issues.apache.org/jira/browse/FINERACT-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434321#comment-17434321 ]
Benura Abeywardena commented on FINERACT-1417:
----------------------------------------------
[~avikganguly010] Please add changes if there's any
> Introduce a new pivot date to filter the savings transactions.
> --------------------------------------------------------------
>
> Key: FINERACT-1417
> URL: https://issues.apache.org/jira/browse/FINERACT-1417
> Project: Apache Fineract
> Issue Type: New Feature
> Components: Savings
> Reporter: Benura Abeywardena
> Assignee: Benura Abeywardena
> Priority: Major
> Fix For: 1.6.0
>
>
> Current fineract code base use multiple for loops to calculate the transaction related data on a savings transaction. This adds an unnecessary latency to a transaction request. By introducing a pivot date, this number of iterations can be reduced with the help of savings account summary available. However, in this scenario back dated transactions will not be allowed. Since, there can be scenarios where back dated transactions are needed, a global configuration is introduced to prevent breaking the existing use cases completely.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)