Major Description
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.
Attachments
Issue Links
- links to