[jira] [Updated] (FINERACT-670) Transaction 'Notes' should be displayed in summary of transaction
[ https://issues.apache.org/jira/browse/FINERACT-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-670: -- Fix Version/s: (was: 1.9.0) > Transaction 'Notes' should be displayed in summary of transaction > - > > Key: FINERACT-670 > URL: https://issues.apache.org/jira/browse/FINERACT-670 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: GSOC, Volunteer, gci, p1 > Fix For: 3.0.0 > > > Whenever we make Transactions like Loan Repayments, we can capture Notes. But > currently, after transaction is done ,these notes can be seen in Loan > Account tab rather than in Transaction Details. This makes it difficult to > determine which transaction the note applied to. > Expected: Notes should be shown in Transaction details page. Likewise, this > notes field should be part of the fields that would get displayed in a > transaction details report. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-676) Address issue with creating rejected data table at savings account level
[ https://issues.apache.org/jira/browse/FINERACT-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-676: -- Fix Version/s: (was: 1.9.0) > Address issue with creating rejected data table at savings account level > - > > Key: FINERACT-676 > URL: https://issues.apache.org/jira/browse/FINERACT-676 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-595) Should allow user to specify an account nickname
[ https://issues.apache.org/jira/browse/FINERACT-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-595: -- Fix Version/s: (was: 1.9.0) > Should allow user to specify an account nickname > > > Key: FINERACT-595 > URL: https://issues.apache.org/jira/browse/FINERACT-595 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.8.0 >Reporter: Rajan Maurya >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, confirm, gsoc, p2, patch > Fix For: 3.0.0 > > > *Summary:* > For users to be able to quickly identify their accounts when doing transfers > or payments, we should allow them to specify an account nickname. > We would have to decide if the account nickname is just stored locally in the > app on the device or if the account nickname would be stored at the platform > level for Apache Fineract. > Storing it the Apache Fineract level, would allow the user to have account > nickname persist across the mobile and online banking apps. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-769) Adding Loan Collaterals to an existing Loan account
[ https://issues.apache.org/jira/browse/FINERACT-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-769: -- Fix Version/s: (was: 1.9.0) > Adding Loan Collaterals to an existing Loan account > > > Key: FINERACT-769 > URL: https://issues.apache.org/jira/browse/FINERACT-769 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.8.0 >Reporter: Santosh Math >Assignee: Rahul Pawar >Priority: Minor > Labels: gci, gsoc, gsoc2019, p2 > Fix For: 3.0.0 > > > Currently, we can add collateral in loan account application level. We can't > add it to existing loan account. Same need to implemented. > Current behavior is given here: > [https://mifosforge.jira.com/wiki/spaces/docs/pages/72909199/How+to+Add+Collateral+to+a+Loan+Account] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-463) Dashboard showing no data for 'Amount Collected for Today' even though there are transactions today
[ https://issues.apache.org/jira/browse/FINERACT-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-463: -- Fix Version/s: (was: 1.9.0) > Dashboard showing no data for 'Amount Collected for Today' even though there > are transactions today > - > > Key: FINERACT-463 > URL: https://issues.apache.org/jira/browse/FINERACT-463 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, community-app, p1, > verify > Fix For: 3.0.0 > > Attachments: dashboard.png > > > Reported by Onyedikachi Nwosu > 1. Create a new office and create a client under the new office. > 2. perform a deposit of 10,000 to a savings account and issued a loan to the > value of 10,000 for the same client. > As can be seen from the attached screenshot, On the dashboard, Amount > Disbursed for Today reflects the 10,000 loan, but the Amount Collected for > Today does not reflect 10,000 savings made. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-471) Preview feature for uploaded document
[ https://issues.apache.org/jira/browse/FINERACT-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-471: -- Fix Version/s: (was: 1.9.0) > Preview feature for uploaded document > - > > Key: FINERACT-471 > URL: https://issues.apache.org/jira/browse/FINERACT-471 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization, System >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > Fix For: 3.0.0 > > > Enhance Request by Boniphace Fredrick > Original Description: > Currently the system allows to upload a document and once you want to view it > again there is only one option ie, to download it. > This act can probably violate client's privacy( ie, client information > vulnerability) for example if a user(eg. Loan officer) uses somebody computer > to access system, so there is possibility he/she can download a document and > forget to delete if from that local machine > Therefore I suggest there should first an option to preview the document fist > maybe as a pdf and then a user can choose either to download, print or just > view it only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-674) Address issue with creating rejected data table at loan account level
[ https://issues.apache.org/jira/browse/FINERACT-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-674: -- Fix Version/s: (was: 1.9.0) > Address issue with creating rejected data table at loan account level > -- > > Key: FINERACT-674 > URL: https://issues.apache.org/jira/browse/FINERACT-674 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-276: -- Fix Version/s: (was: 1.9.0) > Job scheduler timezones not handled correctly > - > > Key: FINERACT-276 > URL: https://issues.apache.org/jira/browse/FINERACT-276 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > Fix For: 3.0.0 > > > Reported by Sander at https://mifosforge.jira.com/browse/MIFOSX-1269 > Original Description: > When investigating some issues with the overdue loan portfolio we found out > that the current way the jobs are handled can cause differences in the > figures for tenants by not picking up the correct date. > The server has the timezone set to UTC/GMT. When a cronjob is added with a > cron entry to run at 0:01 every day, the java scheduler converts this into > the timezone of the tenant (UTC+3 in this example). In this case this results > in the actual schedule to be kicked off at 21:01 the day before. > When the job then triggers it on 21:01 on 01-06-2014 it uses the mysql > CURDATE() feature to decide on the current date, but this returns in UTC, > therefore reporting everything against 01-06-2014, instead of 02-06-2014 > which was the expected (based on timezone UTC+3). > In this case the arrears are updated incorrectly, but same applies to > prepayments and all other jobs that happen in the gap between UTC and the > tenant timezone. > Workaround: Update the cronjob entry to run at 03:01 (UTC+3) by default, this > then gets converted into 0:01 (UTC) and therefore it uses 02-06-2014 as the > date. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-672) Address issue with creating rejected data table at group level
[ https://issues.apache.org/jira/browse/FINERACT-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-672: -- Fix Version/s: (was: 1.9.0) > Address issue with creating rejected data table at group level > --- > > Key: FINERACT-672 > URL: https://issues.apache.org/jira/browse/FINERACT-672 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-736) Update API docs for associating pre-defined nominal interest rates to loan products
[ https://issues.apache.org/jira/browse/FINERACT-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-736: -- Fix Version/s: (was: 1.9.0) > Update API docs for associating pre-defined nominal interest rates to loan > products > --- > > Key: FINERACT-736 > URL: https://issues.apache.org/jira/browse/FINERACT-736 > Project: Apache Fineract > Issue Type: Sub-task >Affects Versions: 1.8.0 >Reporter: Vishwas Babu A J >Priority: Major > Labels: gsoc2019 > Fix For: 3.0.0 > > > With > [https://github.com/apache/fineract/commit/aaa61695cf27419a2bc9e018fc6e2715512a1094] > , the functionality for "Associating pre-defined nominal interest rates to > loan products" has been added in > [https://github.com/apache/fineract/tree/Fineract-614.] > The API documentation for the same needs to be updated at > [https://github.com/apache/fineract/blob/Fineract-614/api-docs/apiLive.htm] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-643) Journal Entries are not filterable by type of entry: system
[ https://issues.apache.org/jira/browse/FINERACT-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-643: -- Fix Version/s: (was: 1.9.0) > Journal Entries are not filterable by type of entry: system > --- > > Key: FINERACT-643 > URL: https://issues.apache.org/jira/browse/FINERACT-643 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, gci, p2 > Fix For: 3.0.0 > > > Related Front -End Issue: > https://github.com/openMF/web-app/issues/236 > As a developer, I am unable to implement the filter for Journal Entries by > type of entry: system, as the only parameter available to filter entries by > type is manualEntriesOnly which filters manual entries (as clear from its > name). There is no way to filter system entries from server-side. > (similar issue in community-app) > Due to a large number of entries in database (over 8), its essential to > implement it from server-side because the default implementation of sending a > HTTP request to get all the entries at once and implementing the logic on > client-side will be too costly for people with slow internet connections. > > Refer: [https://demo.openmf.org/api-docs/apiLive.htm#journalentries_list] > Expected Behaviour: > Journal Entries should be filterable by type of entry: system apart from the > manual as well from the server-side so that it can be implemented on the > client side. > h2. Actual Behaviour > Journal Entries are not filterable by type of entry: system from the > server-side due to which filter by type of entry cannot be implemented > properly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-641) Withdrawal fee support for overdrawing account
[ https://issues.apache.org/jira/browse/FINERACT-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-641: -- Fix Version/s: (was: 1.9.0) > Withdrawal fee support for overdrawing account > --- > > Key: FINERACT-641 > URL: https://issues.apache.org/jira/browse/FINERACT-641 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, p1 > Fix For: 3.0.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > Currently, Savings Withdrawal fee only applicable if withdrawal is done when > balance is greater than zero. > If try to overdraw from savings account, withdrawal fee won't support and > it's throwing the error. > Expected: Withdrawal fee should support overdrawn account . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-652) Deliver status is not getting updated to 'Delivered' (status:300) even message is delivered to the mobile
[ https://issues.apache.org/jira/browse/FINERACT-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-652: -- Fix Version/s: (was: 1.9.0) > Deliver status is not getting updated to 'Delivered' (status:300) even > message is delivered to the mobile > -- > > Key: FINERACT-652 > URL: https://issues.apache.org/jira/browse/FINERACT-652 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.8.0 >Reporter: Santosh Math >Assignee: Benura Lasan Abeywardena >Priority: Critical > Labels: 2019-mifos-gsoc, GCI-2019, GSOC, Volunteer, p1 > Fix For: 3.0.0 > > > The following are the sms status: > Pending: 100 > Waiting for Delivery Report: 150 > Sent sms: 200 > Delivered sms: 300 > Failed sms: 400 > Even sms is delivered to given mobile number the status in the database is > not getting updating from 150 to 300. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-784) Description Field while creating share product should not be mandatory
[ https://issues.apache.org/jira/browse/FINERACT-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-784: -- Fix Version/s: (was: 1.9.0) > Description Field while creating share product should not be mandatory > -- > > Key: FINERACT-784 > URL: https://issues.apache.org/jira/browse/FINERACT-784 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Affects Versions: 1.3.1, 1.8.0 >Reporter: Santosh Math >Priority: Minor > Labels: GCI-2019, p1 > Fix For: 3.0.0 > > > Go to Admin>Products>Share Products and click on 'Create Share Product'. > In create page, Description field is mandatory. It shouldn't be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-690) Global configuration to disallow the change of overdue charges on a loan product to affect the already created loans.
[ https://issues.apache.org/jira/browse/FINERACT-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-690: -- Fix Version/s: (was: 1.9.0) > Global configuration to disallow the change of overdue charges on a loan > product to affect the already created loans. > - > > Key: FINERACT-690 > URL: https://issues.apache.org/jira/browse/FINERACT-690 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Affects Versions: 1.8.0 >Reporter: Mexina Daniel >Priority: Major > Labels: GSoC, p1 > Fix For: 3.0.0 > > > For now when you attach an overdue charge to a loan product which did not > have previously, it affect the active loans that were created without a > penalty. > Am suggesting for the system to have a configuration to allow are disallow > this feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-691) GCM to FCM upgrade in Fineract Back-end for notification
[ https://issues.apache.org/jira/browse/FINERACT-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-691: -- Fix Version/s: (was: 1.9.0) > GCM to FCM upgrade in Fineract Back-end for notification > > > Key: FINERACT-691 > URL: https://issues.apache.org/jira/browse/FINERACT-691 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Ankur Sharma >Assignee: Nayan Ambali >Priority: Major > Labels: p1 > Fix For: 3.0.0 > > > Currently, Fineract codebase supports GCM which a deprecated version. We need > to switch to FCM for our mobile apps to support notification feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-843) Mifos Calculation of reinstallment day
[ https://issues.apache.org/jira/browse/FINERACT-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-843: -- Fix Version/s: (was: 1.9.0) > Mifos Calculation of reinstallment day > -- > > Key: FINERACT-843 > URL: https://issues.apache.org/jira/browse/FINERACT-843 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Affects Versions: 1.8.0 >Reporter: Jose Alberto Hernandez Maldonado >Priority: Minor > Labels: easyfix, features > Fix For: 3.0.0 > > Attachments: 01__Terms_Settings.png, 02__Schedule.png > > > Problem > How to configure a Loan with 2 specific installments in a Month. > # The first one occurs every 15th oh the Month. > # The Second must occurs the last day of the Month. > Solution > We detect two cases: > If the date is before 15th day, then the next is (fixed) to the 15th day of > the current month, > Else If the date is after 15th day, then the next date will be end of month > (calculated) with the java LocalDate method class. > * In both cases, as Mifos X applies the Business rule for no working days. > > Finally we defined a new EnumType called SemiWeeks for that case -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-657) Enhancement of Standing Instruction dealing with insufficient fund in Savings Account
[ https://issues.apache.org/jira/browse/FINERACT-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-657: -- Fix Version/s: (was: 1.9.0) > Enhancement of Standing Instruction dealing with insufficient fund in > Savings Account > -- > > Key: FINERACT-657 > URL: https://issues.apache.org/jira/browse/FINERACT-657 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.7.3, 1.8.2, 1.8.1, 1.8.0 >Reporter: Santosh Math >Assignee: Francis Guchie >Priority: Major > Labels: p2 > Fix For: 3.0.0 > > > (Original Description By Zayyad in mailing list) > Current Behaviour: > If there isn't sufficient funds in the linked savings account, Scheduler jobs > for "Execute Standing Instruction" gets failed. And the repayment doesn't > happen. > Expected Behaviour: > We have had an enquiry before that if the linked savings doesn’t have enough, > then the system should recover the whole amount available in the account and > once the account is credited with any other amount the same is deducted until > the amount due is fully collected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-701) In Individual Collection sheet and Collection Sheet, Not able to select previous year dates(2018) through date picker.
[ https://issues.apache.org/jira/browse/FINERACT-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-701: -- Fix Version/s: (was: 1.9.0) > In Individual Collection sheet and Collection Sheet, Not able to select > previous year dates(2018) through date picker. > -- > > Key: FINERACT-701 > URL: https://issues.apache.org/jira/browse/FINERACT-701 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Critical > Labels: GCI-2019, gsoc > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-752) savings interest, posting wrong interest amount when savings-interest-posting-current-period-end is enable
[ https://issues.apache.org/jira/browse/FINERACT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-752: -- Fix Version/s: (was: 1.9.0) > savings interest, posting wrong interest amount when > savings-interest-posting-current-period-end is enable > > > Key: FINERACT-752 > URL: https://issues.apache.org/jira/browse/FINERACT-752 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.3.1, 1.8.0 >Reporter: andrewDzakpasu >Priority: Critical > Labels: p1 > Fix For: 3.0.0 > > Attachments: fineract79.png, fineract80.png > > Time Spent: 40m > Remaining Estimate: 0h > > When savings-interest-posting-current-period-end is enable the amount of > interest posted is twice the amount when > savings-interest-posting-current-period-end is disabled. > > i was able to replicate this on these two accounts > 1.[https://staging.openmf.org/#/viewsavingaccount/79] when > savings-interest-posting-current-period-end is disable > 2.[https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > savings-interest-posting-current-period-end is enable. > > > To replicate. > # create a savings account with voluntary product with withdrawal fee of 300 > # opening balance 20013 activation date 1-03-2019 > # approve and activate 1-03-2019 > # post interest on 25-03-2019 > # make a withdrawal of 19500 on 26-03-2019 > # you will notice the interest posting total amounts to 296 on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > which is wrong > # whilst on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]79 > the amount is 187 which is correct . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-854) Use prepared statements instead of string concatenated SQL everywhere
[
https://issues.apache.org/jira/browse/FINERACT-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-854:
--
Fix Version/s: (was: 1.9.0)
> Use prepared statements instead of string concatenated SQL everywhere
> -
>
> Key: FINERACT-854
> URL: https://issues.apache.org/jira/browse/FINERACT-854
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Security
>Reporter: Michael Vorburger
>Assignee: Joseph Makara
>Priority: Major
> Labels: beginner, scalability, security, technical
> Fix For: 3.0.0
>
>
> The Fineract code base in many places creates SQL statements through String
> concatenation. This is prone to SQL injection. This is mitigated by the use
> of helpers utilities such as
> {{org.apache.fineract.infrastructure.core.api.ApiParameterHelper.sqlEncodeString(String)}}
> and
> {{org.apache.fineract.infrastructure.security.utils.SQLInjectionValidator.validateSQLInput(String)}}
> but I opine that those are workarounds... the better solution, both for
> security and likely also helping with performance (at least a little bit,
> knowing how much would require measuring it...), would be to use JDBC
> prepared statements with '?' placeholders and passing all raw arguments,
> instead of embedding them in the query String.
> FINERACT-808 root cause analysis brought this up, and I'm about to raise a PR
> for FINERACT-808 which makes a start; the goal of this issue is to use the
> new {{org.apache.fineract.infrastructure.security.utils.SQLBuilder}}
> everywhere, and eventually be able to get completely rid of
> {{ApiParameterHelper}} and {{SQLInjectionValidator}}.
> This issue should also include work to scan the code base for places where
> SQL Strings are concatenated without even using the existing helpers.
> FINERACT-853 could potentially help with that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-791) Transfer of fund from saving balance to shares
[ https://issues.apache.org/jira/browse/FINERACT-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-791: -- Fix Version/s: (was: 1.9.0) > Transfer of fund from saving balance to shares > -- > > Key: FINERACT-791 > URL: https://issues.apache.org/jira/browse/FINERACT-791 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings, Shares >Affects Versions: 1.0.0 >Reporter: Mexina Daniel >Assignee: Benura Abeywardena >Priority: Major > Labels: gsoc, p1 > Fix For: 3.0.0 > > > This improvement will enable to use saving balance to purchase a share > through the feature of transfer fund. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-608) Share Dividends wrongly calculated
[ https://issues.apache.org/jira/browse/FINERACT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-608: -- Fix Version/s: (was: 1.9.0) > Share Dividends wrongly calculated > -- > > Key: FINERACT-608 > URL: https://issues.apache.org/jira/browse/FINERACT-608 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.8.0 >Reporter: Ippez Roberts >Priority: Critical > Fix For: 3.0.0 > > > I have seen some behavior with Share Account and Dividend. > I initiated a dividend payout of 100,000 to 4 clients with shares as below > > *Product>>Share Product>>Share Account (product name)>>Dividends* > ||Name||Dividend Period Start Date||Dividend Period End Date||Dividend > Amount||Status|| > |Share Account|01 January 2017|31 December 2017|100,000|Dividend Approved| > > |*Client Name*|*No. of Shares*| > |Asienzo|38 (approved) 1 pending approval| > |Mureo|40 (approved)| > |Drani|6 (approved)| > |Amatura|0| > |*TOTAL SHARES*|*84 (approved) 1 pending approval*| > > The distribution of dividend is as follow which to me is wrong. > > ||Client Name||Share Account||Dividend Amount||Status|| > |Asienzo Clara|21-1-0|29,260.01|Dividend Initiated| > |Mureo Stella|21-2-3|61,078.95|Dividend Initiated| > |Drani Joseph|21-3-1|8,192.8|Dividend Initiated| > |Amatura Women's Group|21-4-0|1,468.24|Dividend Initiated| > *Justification* > # Dividend per share = 100,000/84 = 1,190.48 ==> This is because there are > 84 approved shares, the 1 pending approval doesn't get dividend. > # Amatura Women's Group doesn't qualify for dividend because there is no > share purchased though they have opened a share account. > # To me the share distribution table should be as below:- > ||Client Name||Share Account||Dividend Amount||Status|| > |Asienzo Clara|21-1-0|45,238.24|Dividend Initiated| > |Mureo Stella|21-2-3|47,619.2|Dividend Initiated| > |Drani Joseph|21-3-1|7,142.88|Dividend Initiated| > |Amatura Women's Group|21-4-0|0|Dividend Initiated| > > Example, If we are calculating dividend for 2017, we get the total shares at > the organisation since inception of the organisation e.g if the organisation > started in 2003, we shall get total shares from 2003 upto 31st Dec 2017. Say > its 360 shares. > > Then if the approved dividend to be given to members is 720,000, we then get > how much each share will get i.e 720,000/360 = *2,000* > Now that we know each share gets 2,000, this will be the multiplying factor > for each members total share. > > Eg. > *Client Name Total Shares Dividend* > Client 1 1 > 2,000 > Client 2 5 > 10,000 > Client 3 10 > 20,000 > Client 4 0 0 > ... etc > > *TOTAL 360 > 720,000* > > Total amount given to clients should be equal to approved dividend. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-647) Allow rescheduling of loan with recalculation of interest enabled
[ https://issues.apache.org/jira/browse/FINERACT-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-647: -- Fix Version/s: (was: 1.9.0) > Allow rescheduling of loan with recalculation of interest enabled > - > > Key: FINERACT-647 > URL: https://issues.apache.org/jira/browse/FINERACT-647 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.8.0 >Reporter: Mexina Daniel >Priority: Major > Labels: large, p2 > Fix For: 3.0.0 > > > There is a need of allowing the loan which has enabled interest recalculation > to be rescheduled once needed. > for now the system does not allow that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-478) Savings overdraft fee with charge time type 'overdraft fee' and charge calculation '%amount' is not working
[ https://issues.apache.org/jira/browse/FINERACT-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-478: -- Fix Version/s: (was: 1.9.0) > Savings overdraft fee with charge time type 'overdraft fee' and charge > calculation '%amount' is not working > --- > > Key: FINERACT-478 > URL: https://issues.apache.org/jira/browse/FINERACT-478 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Savings >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, gsoc, p1 > Fix For: 3.0.0 > > > 1. Go to charges and select charge applied to 'Savings and deposits' > 2. Fill other required inputs with > Charge Time type: overdraft fee > Charge calculation : % amount. > Amount : 1 > > After submission , it is throwing error: > > "validation.msg.charges.charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivity" > Expected: > 1.This feature of overdraft fee with charge calculation as % amount need to > be implemented. > 2. Until the feature is implemented, the following proper error message > should be thrown in stead of above mentioned: > ""validation.msg: > charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivityand > yet to be implemented for overdraft fee" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-789) Wrong Journal Entry Posting on Disburse to savings.
[ https://issues.apache.org/jira/browse/FINERACT-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-789: -- Fix Version/s: (was: 1.9.0) > Wrong Journal Entry Posting on Disburse to savings. > --- > > Key: FINERACT-789 > URL: https://issues.apache.org/jira/browse/FINERACT-789 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.1, 1.8.0 > Environment: All >Reporter: Nyota Macharia >Priority: Critical > Labels: p1 > Fix For: 3.0.0 > > > When a loan with a fee charged at disbursement is disbursed to savings the > the journal entries happen as follows: Eg. Loan of 50,000 with 1% processing > fees charged at disbursement. > # Loan Portfolio is debited by by 50,000. This is okay. > # Liability Transfer is credited by 50,000. This is okay. > # Fee income is credited with 500. This is okay. > # Loan fund source is debit with 500. This is the error, Liability Transfer > should be debited. > # Savings Portfolio is credited with 49,500. This is okay. > # Liability transfer is debited with 49,500. this is okay. > As you can see the end result is that liability transfer is left with a > balance with in fact it is a control account. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-597) mifos -- splitting savings into member and donor(sponsor) for a single saving stream
[ https://issues.apache.org/jira/browse/FINERACT-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-597: -- Fix Version/s: (was: 1.9.0) > mifos -- splitting savings into member and donor(sponsor) for a single saving > stream > > > Key: FINERACT-597 > URL: https://issues.apache.org/jira/browse/FINERACT-597 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.8.0 > Environment: software(cloud) >Reporter: Simon Peter Mulima >Priority: Major > Labels: gsoc, p2 > Fix For: 3.0.0 > > > Hello it would be good to split accounts(saving stream) within an > individual's saving account such that u can separate saving money streams > from for example ( if parents were contributing for their child) a father , > mother and the child *OR* if an individual is receiving topup contributions > from an association which are dependent on themselves making a saving( the > association will give you a saving only if u also contribute and it is > necessary to show what each party has contributed) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-687) Automatic application of Late Penalty should not happen in certain scenarios
[ https://issues.apache.org/jira/browse/FINERACT-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-687: -- Fix Version/s: (was: 1.9.0) > Automatic application of Late Penalty should not happen in certain scenarios > > > Key: FINERACT-687 > URL: https://issues.apache.org/jira/browse/FINERACT-687 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Affects Versions: 1.8.0 >Reporter: sapana >Priority: Major > Labels: gsoc2019, p1 > Fix For: 3.0.0 > > > Currently, late penalty charges are applied automatically depending on > chargeTime configuration if the loan is not closed. However, in following > scenarios, we should be able to configure if late penalty should be applied > or not: > 1. Outstanding amount for Loan is within arrears limit > 2. Loan is in NPA > As a workaround, these charges can be waived, but it reflect in accounting > journals which is not desired. > Also, there are regulatory requirements stating sum of all charges levied on > loan cant be greater than x%loan principal value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-754) Linked between savings transfer transaction broken when account goes into overdraft
[
https://issues.apache.org/jira/browse/FINERACT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-754:
--
Fix Version/s: (was: 1.9.0)
> Linked between savings transfer transaction broken when account goes into
> overdraft
> ---
>
> Key: FINERACT-754
> URL: https://issues.apache.org/jira/browse/FINERACT-754
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.8.0
>Reporter: andrewDzakpasu
>Priority: Major
> Labels: GCI-2019, p2
> Fix For: 3.0.0
>
>
> {code:java}
> // code code where bug is found
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse(); /// why reverse the transaction here if you could just
> update the details
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
> I have replicated it on https://demo.openmf.org/#/viewsavingaccount/2589
> steps to replicate
> 1.create a savings account using the same product with opening balance as
> 45,754 , activation date 31-01-2019
> 2.manually posted interest on savings with transaction date as 31-01-2019
> 3. make an account transfer to another client with amount 45,854 transaction
> date 28-02-2019.
> 5. if you view the details you will see the transfer was made to another
> person will all details
> 6. now make a deposit of 5 on 27-02-2018
> 5. you will see the code above reverses the initial transfers and books it
> again (just a withdrawal )there by breaking the link of the transfer to
> another client.
> you can also view this from the journals
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-631) Allow to specify transfer date when transferring client from one branch to another
[ https://issues.apache.org/jira/browse/FINERACT-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-631: -- Fix Version/s: (was: 1.9.0) > Allow to specify transfer date when transferring client from one branch to > another > -- > > Key: FINERACT-631 > URL: https://issues.apache.org/jira/browse/FINERACT-631 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Affects Versions: 1.8.0 >Reporter: Mexina Daniel >Priority: Major > Labels: 2019-mifos-gsoc, gsoc, p2 > Fix For: 3.0.0 > > > Then transferring the client from one branch to another, the system take the > current data and assume its a transfer date, the system should allow a user > to specify, sometimes it might be a back date. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-892) Include Logback Appender for Google Cloud Logging in Fineract container
[ https://issues.apache.org/jira/browse/FINERACT-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-892: -- Fix Version/s: (was: 1.9.0) > Include Logback Appender for Google Cloud Logging in Fineract container > --- > > Key: FINERACT-892 > URL: https://issues.apache.org/jira/browse/FINERACT-892 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Michael Vorburger >Assignee: Michael Vorburger >Priority: Major > Fix For: 3.0.0 > > > https://cloud.google.com/error-reporting/ > https://cloud.google.com/error-reporting/docs/setup/java > [https://github.com/googleapis/java-logging-logback/blob/master/README.md] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-673) Address issue with creating rejected data table at center level
[ https://issues.apache.org/jira/browse/FINERACT-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-673: -- Fix Version/s: (was: 1.9.0) > Address issue with creating rejected data table at center level > > > Key: FINERACT-673 > URL: https://issues.apache.org/jira/browse/FINERACT-673 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-694) API for Withdrawing Savings Account not available
[ https://issues.apache.org/jira/browse/FINERACT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-694: -- Fix Version/s: (was: 1.9.0) > API for Withdrawing Savings Account not available > - > > Key: FINERACT-694 > URL: https://issues.apache.org/jira/browse/FINERACT-694 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.8.0 >Reporter: Saksham Handu >Priority: Major > Fix For: 3.0.0 > > > Currently, there is no API for withdrawing Saving Account -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-638) Creation of API's for Web App and Self Service Admin Portal
[ https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-638: -- Fix Version/s: (was: 1.9.0) > Creation of API's for Web App and Self Service Admin Portal > --- > > Key: FINERACT-638 > URL: https://issues.apache.org/jira/browse/FINERACT-638 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System, User Management >Affects Versions: 1.8.0 >Reporter: Abhay Chawla >Priority: Major > Labels: gsoc, large, p1 > Fix For: 3.0.0 > > Attachments: AcceptTransferClient.png > > Original Estimate: 80h > Remaining Estimate: 80h > > List of API's that will be required are as follows- > App Configuration for the new web app, based on the Tenant so that they can > be accessed on the login page itself before authentication: > 1) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format > 2) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name > 3) Support for saving and retrieving Default theme and font to be used within > the application > 4) Support for saving and retrieving contact information including website, > email, contact no (multiple if required) > App Configuration for the self-service mobile app and online banking app, > based on Tenant so that they can be accessed on the login page itself before > authentication: > 5) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format (common) > 6) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name (common and will be used as > required by whichever application) > 7) Support for saving and retrieving Default theme and font to be used within > the application (separate for mobile and online banking app) > 8) Support for saving and retrieving contact information including website, > email, contact no (common, multiple if required) > Self Service User Management and Creation > 1) Support for viewing current and potential self-service users. > 2) Support for activating and deactivating self-service users (single and > bulk). > 3) Support for creating new self-service users. > 4) Support for viewing, editing and changing the password of a self-service > user. > Refer to Issues: > https://github.com/openMF/web-app/issues/33 > https://github.com/openMF/web-app/issues/34 > https://github.com/openMF/web-app/issues/35 > https://github.com/openMF/web-app/issues/36 > Self Service JIRA Link: > https://mifosforge.jira.com/wiki/spaces/MIFOSX/pages/102629583/Customer+Self+Service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-626) MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01
[ https://issues.apache.org/jira/browse/FINERACT-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-626: -- Fix Version/s: (was: 1.9.0) > MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01 > -- > > Key: FINERACT-626 > URL: https://issues.apache.org/jira/browse/FINERACT-626 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System >Affects Versions: 1.8.0 >Reporter: Jimmy Jubha Mayala >Priority: Major > Labels: gsoc, p2 > Fix For: 3.0.0 > > > We need a feature in Fineract to enhance cash distribution from head office > to branches, for examplE, in our office we have taken a loan from bank and we > want it be distributed into our branches, we are able to inject this loan > into Head office accounts, but how is it going to be sent to branches > accounts? this is where we got stuck since mifos x 17.07.01 we are using does > not have this feature. > We do request any developer to pick this task. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-633) New Penalty Charge not appearing in Product dropdown list
[ https://issues.apache.org/jira/browse/FINERACT-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-633: -- Fix Version/s: (was: 1.9.0) > New Penalty Charge not appearing in Product dropdown list > - > > Key: FINERACT-633 > URL: https://issues.apache.org/jira/browse/FINERACT-633 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Affects Versions: 1.8.0 > Environment: v18.03.01 >Reporter: Sifiso Mtetwa >Priority: Minor > Labels: GSOC, Volunteer, easyfix, p1 > Fix For: 3.0.0 > > > We have been developing a new feature for penalties overdue on maturity > [https://mifosforge.jira.com/browse/MIFOSX-2848?filter=-2] We have an issue > where after you create the penalty in the charges area with a new charge time > type of overdue on maturity and submit it, it does not appear in loan > products penalties dropdown box for selection. Wanted to find out which class > fetches the penalties that are fetched to appear in this list yet in table > m_charges it appears fine. We have added some code in the UI to fetch the > required variables but it still does not appear. We can’t proceed beyond this > point. Please advise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-790) Double journal entry on reversal then post of disburse to savings.
[ https://issues.apache.org/jira/browse/FINERACT-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-790: -- Fix Version/s: (was: 1.9.0) > Double journal entry on reversal then post of disburse to savings. > -- > > Key: FINERACT-790 > URL: https://issues.apache.org/jira/browse/FINERACT-790 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Loan >Affects Versions: 1.3.1, 1.8.0 > Environment: All >Reporter: Nyota Macharia >Priority: Critical > Labels: p1 > Fix For: 3.0.0 > > > First apply for loan and link savings account. Then disburse the loan to > savings. Reverse the disbursal then disburse again. The implication during > the second disbursal is that journal entries for the first (reversed) > disbursal will be recreated hence making it a double entry. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-841) Data table lookup only camel case if you are importing db
[ https://issues.apache.org/jira/browse/FINERACT-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-841: -- Fix Version/s: (was: 1.9.0) > Data table lookup only camel case if you are importing db > - > > Key: FINERACT-841 > URL: https://issues.apache.org/jira/browse/FINERACT-841 > Project: Apache Fineract > Issue Type: Improvement > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Saransh Sharma >Priority: Minor > Fix For: 3.0.0 > > > When you create data table its all fine, API retrieves data , When you do > like this > # Import your db from one server to another > # You need the created db tables to work , they lookup camel case names > # I had to create the db tables name in camel case manually > We should have a lookup which does return based on the value provided does > not look for camel case and non . > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-737) Ability to fetch details of charges paid by a loan transaction
[ https://issues.apache.org/jira/browse/FINERACT-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-737: -- Fix Version/s: (was: 1.9.0) > Ability to fetch details of charges paid by a loan transaction > -- > > Key: FINERACT-737 > URL: https://issues.apache.org/jira/browse/FINERACT-737 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Affects Versions: 1.8.0 >Reporter: Vishwas Babu A J >Priority: Major > Labels: gsoc2019 > Fix For: 3.0.0 > > > As a side effect of > [https://github.com/apache/fineract/commit/aaa61695cf27419a2bc9e018fc6e2715512a1094] > , along with the functionality for "Predefined nominal interest rates" > associated with loan products, the ability to fetch the details of charges > paid by a loan transaction have also been added in > [https://github.com/apache/fineract/tree/Fineract-614.] > Details of the relevant code changes and the functionality are present in > comments on github at > [https://github.com/apache/fineract/pull/465#pullrequestreview-212401382.] > To merge the same into our develop branch, the API docs and Integration tests > needs to updated to reflect these changes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-756) Scheduler job fails If we enter date manually without using date-picker
[ https://issues.apache.org/jira/browse/FINERACT-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-756: -- Fix Version/s: (was: 1.9.0) > Scheduler job fails If we enter date manually without using date-picker > --- > > Key: FINERACT-756 > URL: https://issues.apache.org/jira/browse/FINERACT-756 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: p1 > Fix For: 3.0.0 > > > 1) Go to any savings account and click on 'More' > 2) Select 'Add Charge' , give the inputs (select the weekly fee) and enter > the date 'Due for Collection on' manually , ie.. by typing it. Don't use > date-picker. > > If you run the scheduler job 'Pay Due for Savings' , it's failing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-675) Address issue with creating rejected data table at office level
[ https://issues.apache.org/jira/browse/FINERACT-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-675: -- Fix Version/s: (was: 1.9.0) > Address issue with creating rejected data table at office level > > > Key: FINERACT-675 > URL: https://issues.apache.org/jira/browse/FINERACT-675 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-739) Loan (Installment in multiples of) Rounding not working
[ https://issues.apache.org/jira/browse/FINERACT-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-739: -- Fix Version/s: (was: 1.9.0) > Loan (Installment in multiples of) Rounding not working > --- > > Key: FINERACT-739 > URL: https://issues.apache.org/jira/browse/FINERACT-739 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: Okeleke Mike >Priority: Major > Fix For: 3.0.0 > > Attachments: SS1.png, SS2.png, SS3.png > > > Loan repay schedule is not affected by *Installment in multiples of (IIM)* > setting in Loan Product screen > when you set the IIM to say: 1000, you are expected to have your total > repayments calculated to the nearest 1000 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-756) Scheduler job fails If we enter date manually without using date-picker
[ https://issues.apache.org/jira/browse/FINERACT-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-756: -- Fix Version/s: 3.0.0 > Scheduler job fails If we enter date manually without using date-picker > --- > > Key: FINERACT-756 > URL: https://issues.apache.org/jira/browse/FINERACT-756 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: p1 > Fix For: 1.9.0, 3.0.0 > > > 1) Go to any savings account and click on 'More' > 2) Select 'Add Charge' , give the inputs (select the weekly fee) and enter > the date 'Due for Collection on' manually , ie.. by typing it. Don't use > date-picker. > > If you run the scheduler job 'Pay Due for Savings' , it's failing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-657) Enhancement of Standing Instruction dealing with insufficient fund in Savings Account
[ https://issues.apache.org/jira/browse/FINERACT-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-657: -- Fix Version/s: 3.0.0 > Enhancement of Standing Instruction dealing with insufficient fund in > Savings Account > -- > > Key: FINERACT-657 > URL: https://issues.apache.org/jira/browse/FINERACT-657 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.7.3, 1.8.2, 1.8.1, 1.8.0 >Reporter: Santosh Math >Assignee: Francis Guchie >Priority: Major > Labels: p2 > Fix For: 1.9.0, 3.0.0 > > > (Original Description By Zayyad in mailing list) > Current Behaviour: > If there isn't sufficient funds in the linked savings account, Scheduler jobs > for "Execute Standing Instruction" gets failed. And the repayment doesn't > happen. > Expected Behaviour: > We have had an enquiry before that if the linked savings doesn’t have enough, > then the system should recover the whole amount available in the account and > once the account is credited with any other amount the same is deducted until > the amount due is fully collected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-694) API for Withdrawing Savings Account not available
[ https://issues.apache.org/jira/browse/FINERACT-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-694: -- Fix Version/s: 3.0.0 > API for Withdrawing Savings Account not available > - > > Key: FINERACT-694 > URL: https://issues.apache.org/jira/browse/FINERACT-694 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.8.0 >Reporter: Saksham Handu >Priority: Major > Fix For: 1.9.0, 3.0.0 > > > Currently, there is no API for withdrawing Saving Account -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-701) In Individual Collection sheet and Collection Sheet, Not able to select previous year dates(2018) through date picker.
[ https://issues.apache.org/jira/browse/FINERACT-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-701: -- Fix Version/s: 3.0.0 > In Individual Collection sheet and Collection Sheet, Not able to select > previous year dates(2018) through date picker. > -- > > Key: FINERACT-701 > URL: https://issues.apache.org/jira/browse/FINERACT-701 > Project: Apache Fineract > Issue Type: Bug > Components: System >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Critical > Labels: GCI-2019, gsoc > Fix For: 1.9.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-737) Ability to fetch details of charges paid by a loan transaction
[ https://issues.apache.org/jira/browse/FINERACT-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-737: -- Fix Version/s: 3.0.0 > Ability to fetch details of charges paid by a loan transaction > -- > > Key: FINERACT-737 > URL: https://issues.apache.org/jira/browse/FINERACT-737 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Affects Versions: 1.8.0 >Reporter: Vishwas Babu A J >Priority: Major > Labels: gsoc2019 > Fix For: 1.9.0, 3.0.0 > > > As a side effect of > [https://github.com/apache/fineract/commit/aaa61695cf27419a2bc9e018fc6e2715512a1094] > , along with the functionality for "Predefined nominal interest rates" > associated with loan products, the ability to fetch the details of charges > paid by a loan transaction have also been added in > [https://github.com/apache/fineract/tree/Fineract-614.] > Details of the relevant code changes and the functionality are present in > comments on github at > [https://github.com/apache/fineract/pull/465#pullrequestreview-212401382.] > To merge the same into our develop branch, the API docs and Integration tests > needs to updated to reflect these changes -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-633) New Penalty Charge not appearing in Product dropdown list
[ https://issues.apache.org/jira/browse/FINERACT-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-633: -- Fix Version/s: 3.0.0 > New Penalty Charge not appearing in Product dropdown list > - > > Key: FINERACT-633 > URL: https://issues.apache.org/jira/browse/FINERACT-633 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Affects Versions: 1.8.0 > Environment: v18.03.01 >Reporter: Sifiso Mtetwa >Priority: Minor > Labels: GSOC, Volunteer, easyfix, p1 > Fix For: 1.9.0, 3.0.0 > > > We have been developing a new feature for penalties overdue on maturity > [https://mifosforge.jira.com/browse/MIFOSX-2848?filter=-2] We have an issue > where after you create the penalty in the charges area with a new charge time > type of overdue on maturity and submit it, it does not appear in loan > products penalties dropdown box for selection. Wanted to find out which class > fetches the penalties that are fetched to appear in this list yet in table > m_charges it appears fine. We have added some code in the UI to fetch the > required variables but it still does not appear. We can’t proceed beyond this > point. Please advise -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-652) Deliver status is not getting updated to 'Delivered' (status:300) even message is delivered to the mobile
[ https://issues.apache.org/jira/browse/FINERACT-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-652: -- Fix Version/s: 3.0.0 > Deliver status is not getting updated to 'Delivered' (status:300) even > message is delivered to the mobile > -- > > Key: FINERACT-652 > URL: https://issues.apache.org/jira/browse/FINERACT-652 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.8.0 >Reporter: Santosh Math >Assignee: Benura Lasan Abeywardena >Priority: Critical > Labels: 2019-mifos-gsoc, GCI-2019, GSOC, Volunteer, p1 > Fix For: 1.9.0, 3.0.0 > > > The following are the sms status: > Pending: 100 > Waiting for Delivery Report: 150 > Sent sms: 200 > Delivered sms: 300 > Failed sms: 400 > Even sms is delivered to given mobile number the status in the database is > not getting updating from 150 to 300. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-791) Transfer of fund from saving balance to shares
[ https://issues.apache.org/jira/browse/FINERACT-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-791: -- Fix Version/s: 3.0.0 > Transfer of fund from saving balance to shares > -- > > Key: FINERACT-791 > URL: https://issues.apache.org/jira/browse/FINERACT-791 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings, Shares >Affects Versions: 1.0.0 >Reporter: Mexina Daniel >Assignee: Benura Abeywardena >Priority: Major > Labels: gsoc, p1 > Fix For: 1.9.0, 3.0.0 > > > This improvement will enable to use saving balance to purchase a share > through the feature of transfer fund. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-790) Double journal entry on reversal then post of disburse to savings.
[ https://issues.apache.org/jira/browse/FINERACT-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-790: -- Fix Version/s: 3.0.0 > Double journal entry on reversal then post of disburse to savings. > -- > > Key: FINERACT-790 > URL: https://issues.apache.org/jira/browse/FINERACT-790 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Loan >Affects Versions: 1.3.1, 1.8.0 > Environment: All >Reporter: Nyota Macharia >Priority: Critical > Labels: p1 > Fix For: 1.9.0, 3.0.0 > > > First apply for loan and link savings account. Then disburse the loan to > savings. Reverse the disbursal then disburse again. The implication during > the second disbursal is that journal entries for the first (reversed) > disbursal will be recreated hence making it a double entry. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-687) Automatic application of Late Penalty should not happen in certain scenarios
[ https://issues.apache.org/jira/browse/FINERACT-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-687: -- Fix Version/s: 3.0.0 > Automatic application of Late Penalty should not happen in certain scenarios > > > Key: FINERACT-687 > URL: https://issues.apache.org/jira/browse/FINERACT-687 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Affects Versions: 1.8.0 >Reporter: sapana >Priority: Major > Labels: gsoc2019, p1 > Fix For: 1.9.0, 3.0.0 > > > Currently, late penalty charges are applied automatically depending on > chargeTime configuration if the loan is not closed. However, in following > scenarios, we should be able to configure if late penalty should be applied > or not: > 1. Outstanding amount for Loan is within arrears limit > 2. Loan is in NPA > As a workaround, these charges can be waived, but it reflect in accounting > journals which is not desired. > Also, there are regulatory requirements stating sum of all charges levied on > loan cant be greater than x%loan principal value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-608) Share Dividends wrongly calculated
[ https://issues.apache.org/jira/browse/FINERACT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-608: -- Fix Version/s: 3.0.0 > Share Dividends wrongly calculated > -- > > Key: FINERACT-608 > URL: https://issues.apache.org/jira/browse/FINERACT-608 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.8.0 >Reporter: Ippez Roberts >Priority: Critical > Fix For: 1.9.0, 3.0.0 > > > I have seen some behavior with Share Account and Dividend. > I initiated a dividend payout of 100,000 to 4 clients with shares as below > > *Product>>Share Product>>Share Account (product name)>>Dividends* > ||Name||Dividend Period Start Date||Dividend Period End Date||Dividend > Amount||Status|| > |Share Account|01 January 2017|31 December 2017|100,000|Dividend Approved| > > |*Client Name*|*No. of Shares*| > |Asienzo|38 (approved) 1 pending approval| > |Mureo|40 (approved)| > |Drani|6 (approved)| > |Amatura|0| > |*TOTAL SHARES*|*84 (approved) 1 pending approval*| > > The distribution of dividend is as follow which to me is wrong. > > ||Client Name||Share Account||Dividend Amount||Status|| > |Asienzo Clara|21-1-0|29,260.01|Dividend Initiated| > |Mureo Stella|21-2-3|61,078.95|Dividend Initiated| > |Drani Joseph|21-3-1|8,192.8|Dividend Initiated| > |Amatura Women's Group|21-4-0|1,468.24|Dividend Initiated| > *Justification* > # Dividend per share = 100,000/84 = 1,190.48 ==> This is because there are > 84 approved shares, the 1 pending approval doesn't get dividend. > # Amatura Women's Group doesn't qualify for dividend because there is no > share purchased though they have opened a share account. > # To me the share distribution table should be as below:- > ||Client Name||Share Account||Dividend Amount||Status|| > |Asienzo Clara|21-1-0|45,238.24|Dividend Initiated| > |Mureo Stella|21-2-3|47,619.2|Dividend Initiated| > |Drani Joseph|21-3-1|7,142.88|Dividend Initiated| > |Amatura Women's Group|21-4-0|0|Dividend Initiated| > > Example, If we are calculating dividend for 2017, we get the total shares at > the organisation since inception of the organisation e.g if the organisation > started in 2003, we shall get total shares from 2003 upto 31st Dec 2017. Say > its 360 shares. > > Then if the approved dividend to be given to members is 720,000, we then get > how much each share will get i.e 720,000/360 = *2,000* > Now that we know each share gets 2,000, this will be the multiplying factor > for each members total share. > > Eg. > *Client Name Total Shares Dividend* > Client 1 1 > 2,000 > Client 2 5 > 10,000 > Client 3 10 > 20,000 > Client 4 0 0 > ... etc > > *TOTAL 360 > 720,000* > > Total amount given to clients should be equal to approved dividend. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-739) Loan (Installment in multiples of) Rounding not working
[ https://issues.apache.org/jira/browse/FINERACT-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-739: -- Fix Version/s: 3.0.0 > Loan (Installment in multiples of) Rounding not working > --- > > Key: FINERACT-739 > URL: https://issues.apache.org/jira/browse/FINERACT-739 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: Okeleke Mike >Priority: Major > Fix For: 1.9.0, 3.0.0 > > Attachments: SS1.png, SS2.png, SS3.png > > > Loan repay schedule is not affected by *Installment in multiples of (IIM)* > setting in Loan Product screen > when you set the IIM to say: 1000, you are expected to have your total > repayments calculated to the nearest 1000 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-843) Mifos Calculation of reinstallment day
[ https://issues.apache.org/jira/browse/FINERACT-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-843: -- Fix Version/s: 3.0.0 > Mifos Calculation of reinstallment day > -- > > Key: FINERACT-843 > URL: https://issues.apache.org/jira/browse/FINERACT-843 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Affects Versions: 1.8.0 >Reporter: Jose Alberto Hernandez Maldonado >Priority: Minor > Labels: easyfix, features > Fix For: 1.9.0, 3.0.0 > > Attachments: 01__Terms_Settings.png, 02__Schedule.png > > > Problem > How to configure a Loan with 2 specific installments in a Month. > # The first one occurs every 15th oh the Month. > # The Second must occurs the last day of the Month. > Solution > We detect two cases: > If the date is before 15th day, then the next is (fixed) to the 15th day of > the current month, > Else If the date is after 15th day, then the next date will be end of month > (calculated) with the java LocalDate method class. > * In both cases, as Mifos X applies the Business rule for no working days. > > Finally we defined a new EnumType called SemiWeeks for that case -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-641) Withdrawal fee support for overdrawing account
[ https://issues.apache.org/jira/browse/FINERACT-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-641: -- Fix Version/s: 3.0.0 > Withdrawal fee support for overdrawing account > --- > > Key: FINERACT-641 > URL: https://issues.apache.org/jira/browse/FINERACT-641 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, p1 > Fix For: 1.9.0, 3.0.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > Currently, Savings Withdrawal fee only applicable if withdrawal is done when > balance is greater than zero. > If try to overdraw from savings account, withdrawal fee won't support and > it's throwing the error. > Expected: Withdrawal fee should support overdrawn account . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-691) GCM to FCM upgrade in Fineract Back-end for notification
[ https://issues.apache.org/jira/browse/FINERACT-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-691: -- Fix Version/s: 3.0.0 > GCM to FCM upgrade in Fineract Back-end for notification > > > Key: FINERACT-691 > URL: https://issues.apache.org/jira/browse/FINERACT-691 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.3.0 >Reporter: Ankur Sharma >Assignee: Nayan Ambali >Priority: Major > Labels: p1 > Fix For: 1.9.0, 3.0.0 > > > Currently, Fineract codebase supports GCM which a deprecated version. We need > to switch to FCM for our mobile apps to support notification feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-670) Transaction 'Notes' should be displayed in summary of transaction
[ https://issues.apache.org/jira/browse/FINERACT-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-670: -- Fix Version/s: 3.0.0 > Transaction 'Notes' should be displayed in summary of transaction > - > > Key: FINERACT-670 > URL: https://issues.apache.org/jira/browse/FINERACT-670 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: GSOC, Volunteer, gci, p1 > Fix For: 1.9.0, 3.0.0 > > > Whenever we make Transactions like Loan Repayments, we can capture Notes. But > currently, after transaction is done ,these notes can be seen in Loan > Account tab rather than in Transaction Details. This makes it difficult to > determine which transaction the note applied to. > Expected: Notes should be shown in Transaction details page. Likewise, this > notes field should be part of the fields that would get displayed in a > transaction details report. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-638) Creation of API's for Web App and Self Service Admin Portal
[ https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-638: -- Fix Version/s: 3.0.0 > Creation of API's for Web App and Self Service Admin Portal > --- > > Key: FINERACT-638 > URL: https://issues.apache.org/jira/browse/FINERACT-638 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System, User Management >Affects Versions: 1.8.0 >Reporter: Abhay Chawla >Priority: Major > Labels: gsoc, large, p1 > Fix For: 1.9.0, 3.0.0 > > Attachments: AcceptTransferClient.png > > Original Estimate: 80h > Remaining Estimate: 80h > > List of API's that will be required are as follows- > App Configuration for the new web app, based on the Tenant so that they can > be accessed on the login page itself before authentication: > 1) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format > 2) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name > 3) Support for saving and retrieving Default theme and font to be used within > the application > 4) Support for saving and retrieving contact information including website, > email, contact no (multiple if required) > App Configuration for the self-service mobile app and online banking app, > based on Tenant so that they can be accessed on the login page itself before > authentication: > 5) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format (common) > 6) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name (common and will be used as > required by whichever application) > 7) Support for saving and retrieving Default theme and font to be used within > the application (separate for mobile and online banking app) > 8) Support for saving and retrieving contact information including website, > email, contact no (common, multiple if required) > Self Service User Management and Creation > 1) Support for viewing current and potential self-service users. > 2) Support for activating and deactivating self-service users (single and > bulk). > 3) Support for creating new self-service users. > 4) Support for viewing, editing and changing the password of a self-service > user. > Refer to Issues: > https://github.com/openMF/web-app/issues/33 > https://github.com/openMF/web-app/issues/34 > https://github.com/openMF/web-app/issues/35 > https://github.com/openMF/web-app/issues/36 > Self Service JIRA Link: > https://mifosforge.jira.com/wiki/spaces/MIFOSX/pages/102629583/Customer+Self+Service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-673) Address issue with creating rejected data table at center level
[ https://issues.apache.org/jira/browse/FINERACT-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-673: -- Fix Version/s: 3.0.0 > Address issue with creating rejected data table at center level > > > Key: FINERACT-673 > URL: https://issues.apache.org/jira/browse/FINERACT-673 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 1.9.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-690) Global configuration to disallow the change of overdue charges on a loan product to affect the already created loans.
[ https://issues.apache.org/jira/browse/FINERACT-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-690: -- Fix Version/s: 3.0.0 > Global configuration to disallow the change of overdue charges on a loan > product to affect the already created loans. > - > > Key: FINERACT-690 > URL: https://issues.apache.org/jira/browse/FINERACT-690 > Project: Apache Fineract > Issue Type: New Feature > Components: Charges, Loan >Affects Versions: 1.8.0 >Reporter: Mexina Daniel >Priority: Major > Labels: GSoC, p1 > Fix For: 1.9.0, 3.0.0 > > > For now when you attach an overdue charge to a loan product which did not > have previously, it affect the active loans that were created without a > penalty. > Am suggesting for the system to have a configuration to allow are disallow > this feature. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-478) Savings overdraft fee with charge time type 'overdraft fee' and charge calculation '%amount' is not working
[ https://issues.apache.org/jira/browse/FINERACT-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-478: -- Fix Version/s: 3.0.0 > Savings overdraft fee with charge time type 'overdraft fee' and charge > calculation '%amount' is not working > --- > > Key: FINERACT-478 > URL: https://issues.apache.org/jira/browse/FINERACT-478 > Project: Apache Fineract > Issue Type: Bug > Components: Charges, Savings >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, gsoc, p1 > Fix For: 1.9.0, 3.0.0 > > > 1. Go to charges and select charge applied to 'Savings and deposits' > 2. Fill other required inputs with > Charge Time type: overdraft fee > Charge calculation : % amount. > Amount : 1 > > After submission , it is throwing error: > > "validation.msg.charges.charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivity" > Expected: > 1.This feature of overdraft fee with charge calculation as % amount need to > be implemented. > 2. Until the feature is implemented, the following proper error message > should be thrown in stead of above mentioned: > ""validation.msg: > charge.calculation.type.percentage.allowed.only.for.withdrawal.or.noactivityand > yet to be implemented for overdraft fee" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-276: -- Fix Version/s: 3.0.0 > Job scheduler timezones not handled correctly > - > > Key: FINERACT-276 > URL: https://issues.apache.org/jira/browse/FINERACT-276 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > Fix For: 1.9.0, 3.0.0 > > > Reported by Sander at https://mifosforge.jira.com/browse/MIFOSX-1269 > Original Description: > When investigating some issues with the overdue loan portfolio we found out > that the current way the jobs are handled can cause differences in the > figures for tenants by not picking up the correct date. > The server has the timezone set to UTC/GMT. When a cronjob is added with a > cron entry to run at 0:01 every day, the java scheduler converts this into > the timezone of the tenant (UTC+3 in this example). In this case this results > in the actual schedule to be kicked off at 21:01 the day before. > When the job then triggers it on 21:01 on 01-06-2014 it uses the mysql > CURDATE() feature to decide on the current date, but this returns in UTC, > therefore reporting everything against 01-06-2014, instead of 02-06-2014 > which was the expected (based on timezone UTC+3). > In this case the arrears are updated incorrectly, but same applies to > prepayments and all other jobs that happen in the gap between UTC and the > tenant timezone. > Workaround: Update the cronjob entry to run at 03:01 (UTC+3) by default, this > then gets converted into 0:01 (UTC) and therefore it uses 02-06-2014 as the > date. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-643) Journal Entries are not filterable by type of entry: system
[ https://issues.apache.org/jira/browse/FINERACT-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-643: -- Fix Version/s: 3.0.0 > Journal Entries are not filterable by type of entry: system > --- > > Key: FINERACT-643 > URL: https://issues.apache.org/jira/browse/FINERACT-643 > Project: Apache Fineract > Issue Type: Improvement > Components: Accounting >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, gci, p2 > Fix For: 1.9.0, 3.0.0 > > > Related Front -End Issue: > https://github.com/openMF/web-app/issues/236 > As a developer, I am unable to implement the filter for Journal Entries by > type of entry: system, as the only parameter available to filter entries by > type is manualEntriesOnly which filters manual entries (as clear from its > name). There is no way to filter system entries from server-side. > (similar issue in community-app) > Due to a large number of entries in database (over 8), its essential to > implement it from server-side because the default implementation of sending a > HTTP request to get all the entries at once and implementing the logic on > client-side will be too costly for people with slow internet connections. > > Refer: [https://demo.openmf.org/api-docs/apiLive.htm#journalentries_list] > Expected Behaviour: > Journal Entries should be filterable by type of entry: system apart from the > manual as well from the server-side so that it can be implemented on the > client side. > h2. Actual Behaviour > Journal Entries are not filterable by type of entry: system from the > server-side due to which filter by type of entry cannot be implemented > properly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-597) mifos -- splitting savings into member and donor(sponsor) for a single saving stream
[ https://issues.apache.org/jira/browse/FINERACT-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-597: -- Fix Version/s: 3.0.0 > mifos -- splitting savings into member and donor(sponsor) for a single saving > stream > > > Key: FINERACT-597 > URL: https://issues.apache.org/jira/browse/FINERACT-597 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.8.0 > Environment: software(cloud) >Reporter: Simon Peter Mulima >Priority: Major > Labels: gsoc, p2 > Fix For: 1.9.0, 3.0.0 > > > Hello it would be good to split accounts(saving stream) within an > individual's saving account such that u can separate saving money streams > from for example ( if parents were contributing for their child) a father , > mother and the child *OR* if an individual is receiving topup contributions > from an association which are dependent on themselves making a saving( the > association will give you a saving only if u also contribute and it is > necessary to show what each party has contributed) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-784) Description Field while creating share product should not be mandatory
[ https://issues.apache.org/jira/browse/FINERACT-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-784: -- Fix Version/s: 3.0.0 > Description Field while creating share product should not be mandatory > -- > > Key: FINERACT-784 > URL: https://issues.apache.org/jira/browse/FINERACT-784 > Project: Apache Fineract > Issue Type: Improvement > Components: Shares >Affects Versions: 1.3.1, 1.8.0 >Reporter: Santosh Math >Priority: Minor > Labels: GCI-2019, p1 > Fix For: 1.9.0, 3.0.0 > > > Go to Admin>Products>Share Products and click on 'Create Share Product'. > In create page, Description field is mandatory. It shouldn't be. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-676) Address issue with creating rejected data table at savings account level
[ https://issues.apache.org/jira/browse/FINERACT-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-676: -- Fix Version/s: 3.0.0 > Address issue with creating rejected data table at savings account level > - > > Key: FINERACT-676 > URL: https://issues.apache.org/jira/browse/FINERACT-676 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 1.9.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-672) Address issue with creating rejected data table at group level
[ https://issues.apache.org/jira/browse/FINERACT-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-672: -- Fix Version/s: 3.0.0 > Address issue with creating rejected data table at group level > --- > > Key: FINERACT-672 > URL: https://issues.apache.org/jira/browse/FINERACT-672 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 1.9.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-471) Preview feature for uploaded document
[ https://issues.apache.org/jira/browse/FINERACT-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-471: -- Fix Version/s: 3.0.0 > Preview feature for uploaded document > - > > Key: FINERACT-471 > URL: https://issues.apache.org/jira/browse/FINERACT-471 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization, System >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, gsoc, p2 > Fix For: 1.9.0, 3.0.0 > > > Enhance Request by Boniphace Fredrick > Original Description: > Currently the system allows to upload a document and once you want to view it > again there is only one option ie, to download it. > This act can probably violate client's privacy( ie, client information > vulnerability) for example if a user(eg. Loan officer) uses somebody computer > to access system, so there is possibility he/she can download a document and > forget to delete if from that local machine > Therefore I suggest there should first an option to preview the document fist > maybe as a pdf and then a user can choose either to download, print or just > view it only. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-752) savings interest, posting wrong interest amount when savings-interest-posting-current-period-end is enable
[ https://issues.apache.org/jira/browse/FINERACT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-752: -- Fix Version/s: 3.0.0 > savings interest, posting wrong interest amount when > savings-interest-posting-current-period-end is enable > > > Key: FINERACT-752 > URL: https://issues.apache.org/jira/browse/FINERACT-752 > Project: Apache Fineract > Issue Type: Bug > Components: Savings >Affects Versions: 1.3.1, 1.8.0 >Reporter: andrewDzakpasu >Priority: Critical > Labels: p1 > Fix For: 1.9.0, 3.0.0 > > Attachments: fineract79.png, fineract80.png > > Time Spent: 40m > Remaining Estimate: 0h > > When savings-interest-posting-current-period-end is enable the amount of > interest posted is twice the amount when > savings-interest-posting-current-period-end is disabled. > > i was able to replicate this on these two accounts > 1.[https://staging.openmf.org/#/viewsavingaccount/79] when > savings-interest-posting-current-period-end is disable > 2.[https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > savings-interest-posting-current-period-end is enable. > > > To replicate. > # create a savings account with voluntary product with withdrawal fee of 300 > # opening balance 20013 activation date 1-03-2019 > # approve and activate 1-03-2019 > # post interest on 25-03-2019 > # make a withdrawal of 19500 on 26-03-2019 > # you will notice the interest posting total amounts to 296 on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]80 > which is wrong > # whilst on > [https://staging.openmf.org/#/viewsavingaccount/|https://staging.openmf.org/#/viewsavingaccount/79]79 > the amount is 187 which is correct . -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-789) Wrong Journal Entry Posting on Disburse to savings.
[ https://issues.apache.org/jira/browse/FINERACT-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-789: -- Fix Version/s: 3.0.0 > Wrong Journal Entry Posting on Disburse to savings. > --- > > Key: FINERACT-789 > URL: https://issues.apache.org/jira/browse/FINERACT-789 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.3.1, 1.8.0 > Environment: All >Reporter: Nyota Macharia >Priority: Critical > Labels: p1 > Fix For: 1.9.0, 3.0.0 > > > When a loan with a fee charged at disbursement is disbursed to savings the > the journal entries happen as follows: Eg. Loan of 50,000 with 1% processing > fees charged at disbursement. > # Loan Portfolio is debited by by 50,000. This is okay. > # Liability Transfer is credited by 50,000. This is okay. > # Fee income is credited with 500. This is okay. > # Loan fund source is debit with 500. This is the error, Liability Transfer > should be debited. > # Savings Portfolio is credited with 49,500. This is okay. > # Liability transfer is debited with 49,500. this is okay. > As you can see the end result is that liability transfer is left with a > balance with in fact it is a control account. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-754) Linked between savings transfer transaction broken when account goes into overdraft
[
https://issues.apache.org/jira/browse/FINERACT-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-754:
--
Fix Version/s: 3.0.0
> Linked between savings transfer transaction broken when account goes into
> overdraft
> ---
>
> Key: FINERACT-754
> URL: https://issues.apache.org/jira/browse/FINERACT-754
> Project: Apache Fineract
> Issue Type: Bug
> Components: Savings
>Affects Versions: 1.8.0
>Reporter: andrewDzakpasu
>Priority: Major
> Labels: GCI-2019, p2
> Fix For: 1.9.0, 3.0.0
>
>
> {code:java}
> // code code where bug is found
> else if
> (overdraftAmount.isNotEqualTo(transaction.getOverdraftAmount(getCurrency(
> {
> SavingsAccountTransaction accountTransaction =
> SavingsAccountTransaction.copyTransaction(transaction);
> transaction.reverse(); /// why reverse the transaction here if you could just
> update the details
> if (overdraftAmount.isGreaterThanZero()) {
> accountTransaction.updateOverdraftAmount(overdraftAmount.getAmount());
> }
> accountTransaction.updateRunningBalance(runningBalance);
> addTransaction(accountTransaction);
> isTransactionsModified = true;
> }
> {code}
> I have replicated it on https://demo.openmf.org/#/viewsavingaccount/2589
> steps to replicate
> 1.create a savings account using the same product with opening balance as
> 45,754 , activation date 31-01-2019
> 2.manually posted interest on savings with transaction date as 31-01-2019
> 3. make an account transfer to another client with amount 45,854 transaction
> date 28-02-2019.
> 5. if you view the details you will see the transfer was made to another
> person will all details
> 6. now make a deposit of 5 on 27-02-2018
> 5. you will see the code above reverses the initial transfers and books it
> again (just a withdrawal )there by breaking the link of the transfer to
> another client.
> you can also view this from the journals
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-463) Dashboard showing no data for 'Amount Collected for Today' even though there are transactions today
[ https://issues.apache.org/jira/browse/FINERACT-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-463: -- Fix Version/s: 3.0.0 > Dashboard showing no data for 'Amount Collected for Today' even though there > are transactions today > - > > Key: FINERACT-463 > URL: https://issues.apache.org/jira/browse/FINERACT-463 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, GSOC, Volunteer, community-app, p1, > verify > Fix For: 1.9.0, 3.0.0 > > Attachments: dashboard.png > > > Reported by Onyedikachi Nwosu > 1. Create a new office and create a client under the new office. > 2. perform a deposit of 10,000 to a savings account and issued a loan to the > value of 10,000 for the same client. > As can be seen from the attached screenshot, On the dashboard, Amount > Disbursed for Today reflects the 10,000 loan, but the Amount Collected for > Today does not reflect 10,000 savings made. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-647) Allow rescheduling of loan with recalculation of interest enabled
[ https://issues.apache.org/jira/browse/FINERACT-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-647: -- Fix Version/s: 3.0.0 > Allow rescheduling of loan with recalculation of interest enabled > - > > Key: FINERACT-647 > URL: https://issues.apache.org/jira/browse/FINERACT-647 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.8.0 >Reporter: Mexina Daniel >Priority: Major > Labels: large, p2 > Fix For: 1.9.0, 3.0.0 > > > There is a need of allowing the loan which has enabled interest recalculation > to be rescheduled once needed. > for now the system does not allow that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-854) Use prepared statements instead of string concatenated SQL everywhere
[
https://issues.apache.org/jira/browse/FINERACT-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-854:
--
Fix Version/s: 3.0.0
> Use prepared statements instead of string concatenated SQL everywhere
> -
>
> Key: FINERACT-854
> URL: https://issues.apache.org/jira/browse/FINERACT-854
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Security
>Reporter: Michael Vorburger
>Assignee: Joseph Makara
>Priority: Major
> Labels: beginner, scalability, security, technical
> Fix For: 1.9.0, 3.0.0
>
>
> The Fineract code base in many places creates SQL statements through String
> concatenation. This is prone to SQL injection. This is mitigated by the use
> of helpers utilities such as
> {{org.apache.fineract.infrastructure.core.api.ApiParameterHelper.sqlEncodeString(String)}}
> and
> {{org.apache.fineract.infrastructure.security.utils.SQLInjectionValidator.validateSQLInput(String)}}
> but I opine that those are workarounds... the better solution, both for
> security and likely also helping with performance (at least a little bit,
> knowing how much would require measuring it...), would be to use JDBC
> prepared statements with '?' placeholders and passing all raw arguments,
> instead of embedding them in the query String.
> FINERACT-808 root cause analysis brought this up, and I'm about to raise a PR
> for FINERACT-808 which makes a start; the goal of this issue is to use the
> new {{org.apache.fineract.infrastructure.security.utils.SQLBuilder}}
> everywhere, and eventually be able to get completely rid of
> {{ApiParameterHelper}} and {{SQLInjectionValidator}}.
> This issue should also include work to scan the code base for places where
> SQL Strings are concatenated without even using the existing helpers.
> FINERACT-853 could potentially help with that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-675) Address issue with creating rejected data table at office level
[ https://issues.apache.org/jira/browse/FINERACT-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-675: -- Fix Version/s: 3.0.0 > Address issue with creating rejected data table at office level > > > Key: FINERACT-675 > URL: https://issues.apache.org/jira/browse/FINERACT-675 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 1.9.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-841) Data table lookup only camel case if you are importing db
[ https://issues.apache.org/jira/browse/FINERACT-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-841: -- Fix Version/s: 3.0.0 > Data table lookup only camel case if you are importing db > - > > Key: FINERACT-841 > URL: https://issues.apache.org/jira/browse/FINERACT-841 > Project: Apache Fineract > Issue Type: Improvement > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Saransh Sharma >Priority: Minor > Fix For: 1.9.0, 3.0.0 > > > When you create data table its all fine, API retrieves data , When you do > like this > # Import your db from one server to another > # You need the created db tables to work , they lookup camel case names > # I had to create the db tables name in camel case manually > We should have a lookup which does return based on the value provided does > not look for camel case and non . > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-892) Include Logback Appender for Google Cloud Logging in Fineract container
[ https://issues.apache.org/jira/browse/FINERACT-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-892: -- Fix Version/s: 3.0.0 > Include Logback Appender for Google Cloud Logging in Fineract container > --- > > Key: FINERACT-892 > URL: https://issues.apache.org/jira/browse/FINERACT-892 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Michael Vorburger >Assignee: Michael Vorburger >Priority: Major > Fix For: 1.9.0, 3.0.0 > > > https://cloud.google.com/error-reporting/ > https://cloud.google.com/error-reporting/docs/setup/java > [https://github.com/googleapis/java-logging-logback/blob/master/README.md] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-674) Address issue with creating rejected data table at loan account level
[ https://issues.apache.org/jira/browse/FINERACT-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-674: -- Fix Version/s: 3.0.0 > Address issue with creating rejected data table at loan account level > -- > > Key: FINERACT-674 > URL: https://issues.apache.org/jira/browse/FINERACT-674 > Project: Apache Fineract > Issue Type: Sub-task > Components: Data Tables >Affects Versions: 1.8.0 >Reporter: Ed Cable >Priority: Major > Fix For: 1.9.0, 3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-631) Allow to specify transfer date when transferring client from one branch to another
[ https://issues.apache.org/jira/browse/FINERACT-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-631: -- Fix Version/s: 3.0.0 > Allow to specify transfer date when transferring client from one branch to > another > -- > > Key: FINERACT-631 > URL: https://issues.apache.org/jira/browse/FINERACT-631 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Affects Versions: 1.8.0 >Reporter: Mexina Daniel >Priority: Major > Labels: 2019-mifos-gsoc, gsoc, p2 > Fix For: 1.9.0, 3.0.0 > > > Then transferring the client from one branch to another, the system take the > current data and assume its a transfer date, the system should allow a user > to specify, sometimes it might be a back date. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-736) Update API docs for associating pre-defined nominal interest rates to loan products
[ https://issues.apache.org/jira/browse/FINERACT-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-736: -- Fix Version/s: 3.0.0 > Update API docs for associating pre-defined nominal interest rates to loan > products > --- > > Key: FINERACT-736 > URL: https://issues.apache.org/jira/browse/FINERACT-736 > Project: Apache Fineract > Issue Type: Sub-task >Affects Versions: 1.8.0 >Reporter: Vishwas Babu A J >Priority: Major > Labels: gsoc2019 > Fix For: 1.9.0, 3.0.0 > > > With > [https://github.com/apache/fineract/commit/aaa61695cf27419a2bc9e018fc6e2715512a1094] > , the functionality for "Associating pre-defined nominal interest rates to > loan products" has been added in > [https://github.com/apache/fineract/tree/Fineract-614.] > The API documentation for the same needs to be updated at > [https://github.com/apache/fineract/blob/Fineract-614/api-docs/apiLive.htm] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-769) Adding Loan Collaterals to an existing Loan account
[ https://issues.apache.org/jira/browse/FINERACT-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-769: -- Fix Version/s: 3.0.0 > Adding Loan Collaterals to an existing Loan account > > > Key: FINERACT-769 > URL: https://issues.apache.org/jira/browse/FINERACT-769 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.8.0 >Reporter: Santosh Math >Assignee: Rahul Pawar >Priority: Minor > Labels: gci, gsoc, gsoc2019, p2 > Fix For: 1.9.0, 3.0.0 > > > Currently, we can add collateral in loan account application level. We can't > add it to existing loan account. Same need to implemented. > Current behavior is given here: > [https://mifosforge.jira.com/wiki/spaces/docs/pages/72909199/How+to+Add+Collateral+to+a+Loan+Account] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-595) Should allow user to specify an account nickname
[ https://issues.apache.org/jira/browse/FINERACT-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-595: -- Fix Version/s: 3.0.0 > Should allow user to specify an account nickname > > > Key: FINERACT-595 > URL: https://issues.apache.org/jira/browse/FINERACT-595 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan, Savings >Affects Versions: 1.8.0 >Reporter: Rajan Maurya >Priority: Minor > Labels: 2019-mifos-gsoc, Volunteer, confirm, gsoc, p2, patch > Fix For: 1.9.0, 3.0.0 > > > *Summary:* > For users to be able to quickly identify their accounts when doing transfers > or payments, we should allow them to specify an account nickname. > We would have to decide if the account nickname is just stored locally in the > app on the device or if the account nickname would be stored at the platform > level for Apache Fineract. > Storing it the Apache Fineract level, would allow the user to have account > nickname persist across the mobile and online banking apps. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-626) MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01
[ https://issues.apache.org/jira/browse/FINERACT-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-626: -- Fix Version/s: 3.0.0 > MOVING CASH FROM HEAD OFFICE ACCOUNTS TO BRANCHES ACCOUNTS IN MIFOS X 17.07.01 > -- > > Key: FINERACT-626 > URL: https://issues.apache.org/jira/browse/FINERACT-626 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System >Affects Versions: 1.8.0 >Reporter: Jimmy Jubha Mayala >Priority: Major > Labels: gsoc, p2 > Fix For: 1.9.0, 3.0.0 > > > We need a feature in Fineract to enhance cash distribution from head office > to branches, for examplE, in our office we have taken a loan from bank and we > want it be distributed into our branches, we are able to inject this loan > into Head office accounts, but how is it going to be sent to branches > accounts? this is where we got stuck since mifos x 17.07.01 we are using does > not have this feature. > We do request any developer to pick this task. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1718) Introduce Lombok to interoperation module
[ https://issues.apache.org/jira/browse/FINERACT-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1718. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to interoperation module > - > > Key: FINERACT-1718 > URL: https://issues.apache.org/jira/browse/FINERACT-1718 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in interoperation module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1740) Introduce Lombok to core module
[ https://issues.apache.org/jira/browse/FINERACT-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1740. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to core module > --- > > Key: FINERACT-1740 > URL: https://issues.apache.org/jira/browse/FINERACT-1740 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in core module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1727) Introduce Lombok to accountnumberformat module
[ https://issues.apache.org/jira/browse/FINERACT-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1727. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to accountnumberformat module > -- > > Key: FINERACT-1727 > URL: https://issues.apache.org/jira/browse/FINERACT-1727 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in accountnumberformat module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1779) Introduce Lombok to teller module
[ https://issues.apache.org/jira/browse/FINERACT-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1779. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to teller module > - > > Key: FINERACT-1779 > URL: https://issues.apache.org/jira/browse/FINERACT-1779 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in teller module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1715) Introduce Lombok to cob module
[ https://issues.apache.org/jira/browse/FINERACT-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1715. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to cob module > -- > > Key: FINERACT-1715 > URL: https://issues.apache.org/jira/browse/FINERACT-1715 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in cob module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1780) Introduce Lombok to workingdays module
[ https://issues.apache.org/jira/browse/FINERACT-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1780. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to workingdays module > -- > > Key: FINERACT-1780 > URL: https://issues.apache.org/jira/browse/FINERACT-1780 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in workingdays module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1776) Introduce Lombok to office module
[ https://issues.apache.org/jira/browse/FINERACT-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1776. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to office module > - > > Key: FINERACT-1776 > URL: https://issues.apache.org/jira/browse/FINERACT-1776 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in office module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1732) Introduce Lombok to bulkimport module
[ https://issues.apache.org/jira/browse/FINERACT-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1732. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to bulkimport module > - > > Key: FINERACT-1732 > URL: https://issues.apache.org/jira/browse/FINERACT-1732 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in bulkimport module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1742) Introduce Lombok to dataqueries module
[ https://issues.apache.org/jira/browse/FINERACT-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1742. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to dataqueries module > -- > > Key: FINERACT-1742 > URL: https://issues.apache.org/jira/browse/FINERACT-1742 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in dataqueries module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1743) Introduce Lombok to documentmanagement module
[ https://issues.apache.org/jira/browse/FINERACT-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1743. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to documentmanagement module > - > > Key: FINERACT-1743 > URL: https://issues.apache.org/jira/browse/FINERACT-1743 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in documentmanagement module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1775) Introduce Lombok to monetary module
[ https://issues.apache.org/jira/browse/FINERACT-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1775. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to monetary module > --- > > Key: FINERACT-1775 > URL: https://issues.apache.org/jira/browse/FINERACT-1775 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in monetary module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1778) Introduce Lombok to staff module
[ https://issues.apache.org/jira/browse/FINERACT-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1778. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to staff module > > > Key: FINERACT-1778 > URL: https://issues.apache.org/jira/browse/FINERACT-1778 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in staff module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1716) Introduce Lombok to commands module
[ https://issues.apache.org/jira/browse/FINERACT-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1716. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to commands module > --- > > Key: FINERACT-1716 > URL: https://issues.apache.org/jira/browse/FINERACT-1716 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in commands module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1737) Introduce Lombok to smscampaigns module
[ https://issues.apache.org/jira/browse/FINERACT-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1737. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to smscampaigns module > --- > > Key: FINERACT-1737 > URL: https://issues.apache.org/jira/browse/FINERACT-1737 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in smscampaigns module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1725) Introduce Lombok to JournalEntry module
[ https://issues.apache.org/jira/browse/FINERACT-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic resolved FINERACT-1725. Resolution: Fixed Done by Abhinav as part of GSoC project. > Introduce Lombok to JournalEntry module > --- > > Key: FINERACT-1725 > URL: https://issues.apache.org/jira/browse/FINERACT-1725 > Project: Apache Fineract > Issue Type: Sub-task >Reporter: Hemant Gupta >Priority: Major > Fix For: 1.9.0 > > > This sub-task introduces Lombok annotations in JournalEntry module. > Following changes are introduced : > # Annotating the sub-packages with multiple appropriate annotations. > # Removing 'final' keyword from attributes. > # Remove all constructors and, find their usage & correct them with fluent > setters. > # Remove all Getters & Setters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1875) Operation requires a scrollable ResultSet, but this ResultSet is FORWARD_ONLY. Postgres
[
https://issues.apache.org/jira/browse/FINERACT-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandar Vidakovic updated FINERACT-1875:
---
Fix Version/s: 1.10.0
(was: 1.9.0)
> Operation requires a scrollable ResultSet, but this ResultSet is
> FORWARD_ONLY. Postgres
> ---
>
> Key: FINERACT-1875
> URL: https://issues.apache.org/jira/browse/FINERACT-1875
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Affects Versions: 1.8.3
> Environment: Local:
> - Ubuntu 22.04
> - Postgresql 14.6
> Server:
> - Ubuntu 20.04
> - Postgresql 14.6
> - Tomcat 9.0.71
>Reporter: Richard Matovu
>Priority: Critical
> Labels: postgresql, resultset, scrollable_resultset
> Fix For: 1.10.0
>
>
> Under tax components and tax groups, when you have created more than one
> record of either, and you do a fetch, it throws an error the following error:
> {code:java}
> 2023-01-27 17:41:16.378 -ERROR 22641 --- [nio-443-exec-26]
> o.s.b.w.servlet.support.ErrorPageFilter : Forwarding to error page from
> request [/api/v1/taxes/group] due to exception
> [org.springframework.jdbc.UncategorizedSQLException: StatementCallback;
> uncategorized SQLException for SQL [select tg.id as id, tg.name as
> name,tgm.id as mappingId,tc.id as taxComponentId, tc.name as
> taxComponentName,tgm.start_date as startDate, tgm.end_date as endDate from
> m_tax_group tg inner join m_tax_group_mappings tgm on tgm.tax_group_id =
> tg.id inner join m_tax_component tc on tc.id = tgm.tax_component_id ]; SQL
> state [24000]; error code [0]; Operation requires a scrollable ResultSet, but
> this ResultSet is FORWARD_ONLY.; nested exception is
> org.postgresql.util.PSQLException: Operation requires a scrollable ResultSet,
> but this ResultSet is FORWARD_ONLY.]
> javax.servlet.ServletException:
> org.springframework.jdbc.UncategorizedSQLException: StatementCallback;
> uncategorized SQLException for SQL [select tg.id as id, tg.name as
> name,tgm.id as mappingId,tc.id as taxComponentId, tc.name as
> taxComponentName,tgm.start_date as startDate, tgm.end_date as endDate from
> m_tax_group tg inner join m_tax_group_mappings tgm on tgm.tax_group_id =
> tg.id inner join m_tax_component tc on tc.id = tgm.tax_component_id ]; SQL
> state [24000]; error code [0]; Operation requires a scrollable ResultSet, but
> this ResultSet is FORWARD_ONLY.; nested exception is
> org.postgresql.util.PSQLException: Operation requires a scrollable ResultSet,
> but this ResultSet is FORWARD_ONLY.at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:410)
> at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
>...Caused by: org.springframework.jdbc.UncategorizedSQLException:
> StatementCallback; uncategorized SQLException for SQL [select tg.id as id,
> tg.name as name,tgm.id as mappingId,tc.id as taxComponentId, tc.name as
> taxComponentName,tgm.start_date as startDate, tgm.end_date as endDate from
> m_tax_group tg inner join m_tax_group_mappings tgm on tgm.tax_group_id =
> tg.id inner join m_tax_component tc on tc.id = tgm.tax_component_id ]; SQL
> state [24000]; error code [0]; Operation requires a scrollable ResultSet, but
> this ResultSet is FORWARD_ONLY.; nested exception is
> org.postgresql.util.PSQLException: Operation requires a scrollable ResultSet,
> but this ResultSet is FORWARD_ONLY.at
> org.springframework.jdbc.core.JdbcTemplate.translateException(JdbcTemplate.java:1542)
> at
> org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:393)
> at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:465)
> at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:475)
> at
> org.apache.fineract.portfolio.tax.service.TaxReadPlatformServiceImpl.retrieveAllTaxGroups(TaxReadPlatformServiceImpl.java:80)
> at
> org.apache.fineract.portfolio.tax.api.TaxGroupApiResource.retrieveAllTaxGroups(TaxGroupApiResource.java:91)
> at jdk.internal.reflect.GeneratedMethodAccessor317.invoke(Unknown Source)
>at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ...Caused by: org.postgresql.util.PSQLException: Operation requires a
> scrollable ResultSet, but this ResultSet is FORWARD_ONLY.at
> org.postgresql.jdbc.PgResultSet.checkScrollable(PgResultSet.java:316)at
> org.postgresql.jdbc.PgResultSet.previous(PgResultSet.java:993)at
> com.zaxxer.hikari.pool.HikariProxyResultSet.previous(HikariProxyResultSet.java)
> at
>
