[jira] [Comment Edited] (FINERACT-2063) Enable repayment of overdue installments
[ https://issues.apache.org/jira/browse/FINERACT-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825670#comment-17825670 ] Francis Guchie edited comment on FINERACT-2063 at 3/12/24 1:08 PM: --- [~kigred.developer] [~ikimbrah] This is what I have observed for a long time, and a PR will go a long to solve the issue Ideally the cron job should * consider total amounts not yet paid, * apply the payment using the repayment strategy set in the product setting of the loan in question * In the order provided by the repayment strategy was (Author: francisguchie): [~kigred.developer] [~ikimbrah] This is what I have observed for a long time, the cron job should * consider total amounts not yet paid, * apply the payment using the repayment strategy set in the product setting of the loan in question * In the order provided by the repayment strategy > Enable repayment of overdue installments > > > Key: FINERACT-2063 > URL: https://issues.apache.org/jira/browse/FINERACT-2063 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.9.0 >Reporter: Kigenyi Wilfred >Priority: Minor > Fix For: 1.10.0 > > > Currently the standing instruction task will only execute a transfer if the > loan installment in question is for the exact date as the date on which the > task is running. This means that if for example a client had an installment > due for the day before (or several days before), that installment will not be > settled if the client deposits funds on his savings account today or the next > day. > The thinking is that installments should be settled as longs as they are not > in the future, that is if the are today or they are overdue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-2063) Enable repayment of overdue installments
[ https://issues.apache.org/jira/browse/FINERACT-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825670#comment-17825670 ] Francis Guchie commented on FINERACT-2063: -- [~kigred.developer] [~ikimbrah] This is what I have observed for a long time, the cron job should * consider total amounts not yet paid, * apply the payment using the repayment strategy set in the product setting of the loan in question * In the order provided by the repayment strategy > Enable repayment of overdue installments > > > Key: FINERACT-2063 > URL: https://issues.apache.org/jira/browse/FINERACT-2063 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.9.0 >Reporter: Kigenyi Wilfred >Priority: Minor > Fix For: 1.10.0 > > > Currently the standing instruction task will only execute a transfer if the > loan installment in question is for the exact date as the date on which the > task is running. This means that if for example a client had an installment > due for the day before (or several days before), that installment will not be > settled if the client deposits funds on his savings account today or the next > day. > The thinking is that installments should be settled as longs as they are not > in the future, that is if the are today or they are overdue. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-2062) Use 48 weeks in a year when interest rate is per month
[
https://issues.apache.org/jira/browse/FINERACT-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17825667#comment-17825667
]
Francis Guchie commented on FINERACT-2062:
--
[~kigred.developer] [~adamsaghy] [~bgowda] & [~eroemma] , [~ikimbrah]
Mathematically everything is correct, but the practice is not correct in my
view. I have experienced this from a number of clients who like to assume a
month has 4 weeks. So they want to give out loans and use the weeks as a yard
stick ( to their customers) yet the want to annualize the interest calculation
(they want to use this as a {*}"LUNAR MONTH"{*})
a month measured between
[successive|https://www.google.com/search?sa=X_esv=1114ab6409594670=1777=830=ACQVn08chJpugHbWy1NIK7JNEteQgx_azw:1710248186155=successive=AKbGX_pt4UlL1m2gNC94R_NJDj6SF39e9PuGLPKk1qjEgJkeoeSrsMOJx8LzLMIDC-cz1UsXq9wOtXMrthQQYx1FDHcIdK3TtpDWLY_YbFTA8ae9B5I7MXQ%3D=1]
new
[moons|https://www.google.com/search?sa=X_esv=1114ab6409594670=1777=830=ACQVn08chJpugHbWy1NIK7JNEteQgx_azw:1710248186155=moons=AKbGX_oRjcCPa5QPMQwD2ABTMArQUfLzInjyVbGwBh1zPlK-Ip0wPQzNdEc3XAJYBfRb40bIrCk2e-NZZRckVYXvsV5SqiMh8A%3D%3D=1]
(roughly 29 1/2 days).
*
(in general use) a period of four weeks
In my personal view,
A daily loan should be calculated using daily interest calculations 1/365 (or
360) if one chooses a year of 360 days
A weekly loan should be calculated using weekly interest calculations 1/52
weeks in a year
A Monthly loan should be calculated using monthly interest calculations 1/12
weeks in a year
A mixture of weeks and months in a loan interest calculation method is likely
to confuse the flock unless we can come up with a package that does not violate
rules of engagement in the Financial Industry
[~ikimbrah] please comment
> Use 48 weeks in a year when interest rate is per month
> --
>
> Key: FINERACT-2062
> URL: https://issues.apache.org/jira/browse/FINERACT-2062
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Loan
>Affects Versions: 1.9.0
>Reporter: Kigenyi Wilfred
>Priority: Minor
> Fix For: 1.10.0
>
>
> Given that the interest rate period on a loan is monthly and client has
> chosen to make weekly repayments, it makes more sense to assume that there
> are 4 weeks in the month and 12 months in the year which comes to 48 weeks
> rather than assuming the traditional 52 weeks in the year.
> For example if a loan has a flat interest rate of 2% Per month and the
> principal is 1000 and the repayments are weekly, weekly interest is currently
> computed as follows:
> interest per week = (0.02*12*1000)/52 = 4.61538
> it would make more sense if interest per month is computed as follows:
> interest per week = (0.02*12*1000)/48 = 5
>
> In other words there is no need for computing weeks in a year when we are
> dealing with a month. There are 4 weeks in a month and this assumption
> calculates a more reasonable figure as compared to when we compute weeks in
> year.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FINERACT-1990) Loan repayment schedule shows incorrect numbers of instalments for daily repayment frequency loans.
[ https://issues.apache.org/jira/browse/FINERACT-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1990: Assignee: Francis Guchie > Loan repayment schedule shows incorrect numbers of instalments for daily > repayment frequency loans. > --- > > Key: FINERACT-1990 > URL: https://issues.apache.org/jira/browse/FINERACT-1990 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.4 >Reporter: Samarth Singh Thakur >Assignee: Francis Guchie >Priority: Critical > Attachments: image-2023-10-06-16-23-47-158.png > > > !image-2023-10-06-16-23-47-158.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
[ https://issues.apache.org/jira/browse/FINERACT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772519#comment-17772519 ] Francis Guchie commented on FINERACT-1945: -- [~opensrcsam] Please make a comment on this if you have observed the same > UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing > -- > > Key: FINERACT-1945 > URL: https://issues.apache.org/jira/browse/FINERACT-1945 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.7.3 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2023-06-20-19-40-27-163.png, > image-2023-06-20-19-45-07-790.png > > > Jobs are failing to run and I think it is the Jobs that are duplicated on the > UI. > Something to consider trouble shooting > !image-2023-06-20-19-40-27-163.png! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-109) Bank Reconciliation Module
[ https://issues.apache.org/jira/browse/FINERACT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-109: Priority: Major (was: Minor) > Bank Reconciliation Module > -- > > Key: FINERACT-109 > URL: https://issues.apache.org/jira/browse/FINERACT-109 > Project: Apache Fineract > Issue Type: New Feature > Components: Accounting >Reporter: Emmanuel Nnaa >Assignee: Francis Guchie >Priority: Major > Labels: Cleanup2022, functional > > A number of MFIs have requested the addition of a bank reconciliation module, > making it easier for them to reconcile any journal entries made against their > Bank Account GL(s) in Fineract, with the actual transactions in their bank > account. First thoughts on how this would work below: > * User will need the ability to select a specific GL Account to reconcile. > Perhaps a checkbox should be added when creating / editing a GL to specify if > it should be made available in the reconciliation module > * Reconciliation module should show all GL accounts that were previously made > available, along with the reconciled balance and unreconciled balance > * User should then be able to select the GL account, and pull out either all > journal entries between a start and end date, or all unreconciled entries, or > all reconciled entries > * User should have the ability to tick a checkbox for any entry that they > wish to reconcile and then to save at the end once they have ticked multiple > checkboxes they can save > * The act of reconciliation should be tracked and shown in the audit module > The more complex, but key, addition, will be the option to group (or if > possible to sum) all transactions with the same reference together. This will > be useful when reconciling group postings which appear as multiple GLs in > Fineract, but only one transaction in the bank account. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (FINERACT-109) Bank Reconciliation Module
[ https://issues.apache.org/jira/browse/FINERACT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reopened FINERACT-109: - Assignee: Francis Guchie I am re-opening this issue coz am interested in it > Bank Reconciliation Module > -- > > Key: FINERACT-109 > URL: https://issues.apache.org/jira/browse/FINERACT-109 > Project: Apache Fineract > Issue Type: New Feature > Components: Accounting >Reporter: Emmanuel Nnaa >Assignee: Francis Guchie >Priority: Minor > Labels: Cleanup2022, functional > > A number of MFIs have requested the addition of a bank reconciliation module, > making it easier for them to reconcile any journal entries made against their > Bank Account GL(s) in Fineract, with the actual transactions in their bank > account. First thoughts on how this would work below: > * User will need the ability to select a specific GL Account to reconcile. > Perhaps a checkbox should be added when creating / editing a GL to specify if > it should be made available in the reconciliation module > * Reconciliation module should show all GL accounts that were previously made > available, along with the reconciled balance and unreconciled balance > * User should then be able to select the GL account, and pull out either all > journal entries between a start and end date, or all unreconciled entries, or > all reconciled entries > * User should have the ability to tick a checkbox for any entry that they > wish to reconcile and then to save at the end once they have ticked multiple > checkboxes they can save > * The act of reconciliation should be tracked and shown in the audit module > The more complex, but key, addition, will be the option to group (or if > possible to sum) all transactions with the same reference together. This will > be useful when reconciling group postings which appear as multiple GLs in > Fineract, but only one transaction in the bank account. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1967) Pay Charge, Pay Due Savings Charges, Apply Annual Fee For Savings is violating Overdraft conditions
[ https://issues.apache.org/jira/browse/FINERACT-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1967: Assignee: Francis Guchie > Pay Charge, Pay Due Savings Charges, Apply Annual Fee For Savings is > violating Overdraft conditions > --- > > Key: FINERACT-1967 > URL: https://issues.apache.org/jira/browse/FINERACT-1967 > Project: Apache Fineract > Issue Type: Bug >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > > If a user disallows overdraft on a savings account but yet adds a savings > charge. > then later clicks pay charge on the same account the charge will be paid thus > sending the account into over-drawn state > Also the jobs below > *Cron Jobs below will send account into overdrawn state* > Pay Due Savings Charges > Apply Annual Fee For Savings -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1967) Pay Charge, Pay Due Savings Charges, Apply Annual Fee For Savings is violating Overdraft conditions
Francis Guchie created FINERACT-1967: Summary: Pay Charge, Pay Due Savings Charges, Apply Annual Fee For Savings is violating Overdraft conditions Key: FINERACT-1967 URL: https://issues.apache.org/jira/browse/FINERACT-1967 Project: Apache Fineract Issue Type: Bug Reporter: Francis Guchie If a user disallows overdraft on a savings account but yet adds a savings charge. then later clicks pay charge on the same account the charge will be paid thus sending the account into over-drawn state Also the jobs below *Cron Jobs below will send account into overdrawn state* Pay Due Savings Charges Apply Annual Fee For Savings -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1957) Fix Interchanged Balances On Savings Withdrawal Transaction and Savings Withdrawal Charge Transaction
[ https://issues.apache.org/jira/browse/FINERACT-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1957: - Affects Version/s: 1.8.3 > Fix Interchanged Balances On Savings Withdrawal Transaction and Savings > Withdrawal Charge Transaction > - > > Key: FINERACT-1957 > URL: https://issues.apache.org/jira/browse/FINERACT-1957 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.7.2, 1.8.2, 1.8.3, 1.7.3 >Reporter: Kigenyi Wilfred >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > > When using automatic withdrawal charges on a savings account, it sometimes > happens that the withdrawal transaction and the corresponding withdrawal > charge transaction happen at "The same time". Sometimes the withdrawal > transaction happens before the charge transaction and sometimes it is the > other way round, so one cannot predict if the transaction id for the charge > transaction will be greater or less that of the actual withdrawal > transaction. Since the SavingsAccountTransactionComparator compares > created_date (these can be the same) and id (there is no assurance as to > which one will come first), the comparison become unpredictable for this > particular case and the logic sometimes ends up interchanging running > balances on the transactions. So when a list of transactions is pulled it may > show the interchanged running balances for withdrawal charge transaction and > the withdrawal transaction. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1957) Fix Interchanged Balances On Savings Withdrawal Transaction and Savings Withdrawal Charge Transaction
[ https://issues.apache.org/jira/browse/FINERACT-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1957: Assignee: Francis Guchie > Fix Interchanged Balances On Savings Withdrawal Transaction and Savings > Withdrawal Charge Transaction > - > > Key: FINERACT-1957 > URL: https://issues.apache.org/jira/browse/FINERACT-1957 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.7.2, 1.8.2, 1.7.3 >Reporter: Kigenyi Wilfred >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > > When using automatic withdrawal charges on a savings account, it sometimes > happens that the withdrawal transaction and the corresponding withdrawal > charge transaction happen at "The same time". Sometimes the withdrawal > transaction happens before the charge transaction and sometimes it is the > other way round, so one cannot predict if the transaction id for the charge > transaction will be greater or less that of the actual withdrawal > transaction. Since the SavingsAccountTransactionComparator compares > created_date (these can be the same) and id (there is no assurance as to > which one will come first), the comparison become unpredictable for this > particular case and the logic sometimes ends up interchanging running > balances on the transactions. So when a list of transactions is pulled it may > show the interchanged running balances for withdrawal charge transaction and > the withdrawal transaction. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1957) Fix Interchanged Balances On Savings Withdrawal Transaction and Savings Withdrawal Charge Transaction
[ https://issues.apache.org/jira/browse/FINERACT-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751120#comment-17751120 ] Francis Guchie commented on FINERACT-1957: -- [~ikimbrah] Please look into this. But I think we need to add micro seconds to transactions in the system for all modules. to uniquely identify transactions and be able to sort / order then accurately > Fix Interchanged Balances On Savings Withdrawal Transaction and Savings > Withdrawal Charge Transaction > - > > Key: FINERACT-1957 > URL: https://issues.apache.org/jira/browse/FINERACT-1957 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.7.2, 1.8.2, 1.7.3 >Reporter: Kigenyi Wilfred >Priority: Major > Fix For: 1.9.0 > > > When using automatic withdrawal charges on a savings account, it sometimes > happens that the withdrawal transaction and the corresponding withdrawal > charge transaction happen at "The same time". Sometimes the withdrawal > transaction happens before the charge transaction and sometimes it is the > other way round, so one cannot predict if the transaction id for the charge > transaction will be greater or less that of the actual withdrawal > transaction. Since the SavingsAccountTransactionComparator compares > created_date (these can be the same) and id (there is no assurance as to > which one will come first), the comparison become unpredictable for this > particular case and the logic sometimes ends up interchanging running > balances on the transactions. So when a list of transactions is pulled it may > show the interchanged running balances for withdrawal charge transaction and > the withdrawal transaction. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1957) Fix Interchanged Balances On Savings Withdrawal Transaction and Savings Withdrawal Charge Transaction
[ https://issues.apache.org/jira/browse/FINERACT-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1957: - Affects Version/s: 1.7.2 1.7.3 > Fix Interchanged Balances On Savings Withdrawal Transaction and Savings > Withdrawal Charge Transaction > - > > Key: FINERACT-1957 > URL: https://issues.apache.org/jira/browse/FINERACT-1957 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.7.2, 1.8.2, 1.7.3 >Reporter: Kigenyi Wilfred >Priority: Major > Fix For: 1.9.0 > > > When using automatic withdrawal charges on a savings account, it sometimes > happens that the withdrawal transaction and the corresponding withdrawal > charge transaction happen at "The same time". Sometimes the withdrawal > transaction happens before the charge transaction and sometimes it is the > other way round, so one cannot predict if the transaction id for the charge > transaction will be greater or less that of the actual withdrawal > transaction. Since the SavingsAccountTransactionComparator compares > created_date (these can be the same) and id (there is no assurance as to > which one will come first), the comparison become unpredictable for this > particular case and the logic sometimes ends up interchanging running > balances on the transactions. So when a list of transactions is pulled it may > show the interchanged running balances for withdrawal charge transaction and > the withdrawal transaction. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1950) Disallow backdated transactions - A Global Configuration
[ https://issues.apache.org/jira/browse/FINERACT-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1950: - Summary: Disallow backdated transactions - A Global Configuration (was: Disallow backdated transactions after COB) > Disallow backdated transactions - A Global Configuration > - > > Key: FINERACT-1950 > URL: https://issues.apache.org/jira/browse/FINERACT-1950 > Project: Apache Fineract > Issue Type: Improvement >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > > We need to have a global configuration to disallow backdated transactions for > a given period without necessarily closing an accounting period in the > closing entries. > A use case of a teller not being allowed to post a backdated transaction on a > customer after the till was balanced or after COB. The accountant can however > have the right to post GL transactions on a back date. > > This should however be set as a global configuration that can be turned on > and off. > > [~francisguchie] and [~bgowda] and [~eroemma] what do you think of this > improvement? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (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 ] Francis Guchie reassigned FINERACT-657: --- Assignee: Francis Guchie (was: Rahul Pawar) > 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.8.0, 1.8.1, 1.8.2, 1.7.3 >Reporter: Santosh Math >Assignee: Francis Guchie >Priority: Major > Labels: p2 > Fix For: 1.9.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] [Commented] (FINERACT-1950) Disallow backdated transactions after COB
[ https://issues.apache.org/jira/browse/FINERACT-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17749997#comment-17749997 ] Francis Guchie commented on FINERACT-1950: -- Doing final testing before I push the PR. [~ikimbrah] thank you for the functional tests so far done > Disallow backdated transactions after COB > - > > Key: FINERACT-1950 > URL: https://issues.apache.org/jira/browse/FINERACT-1950 > Project: Apache Fineract > Issue Type: Improvement >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > > We need to have a global configuration to disallow backdated transactions for > a given period without necessarily closing an accounting period in the > closing entries. > A use case of a teller not being allowed to post a backdated transaction on a > customer after the till was balanced or after COB. The accountant can however > have the right to post GL transactions on a back date. > > This should however be set as a global configuration that can be turned on > and off. > > [~francisguchie] and [~bgowda] and [~eroemma] what do you think of this > improvement? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1948) Loan repayment by account transfer transaction type should not be withdrawal
[ https://issues.apache.org/jira/browse/FINERACT-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17749794#comment-17749794 ] Francis Guchie commented on FINERACT-1948: -- Thanks [~bgowda] , [~ikimbrah] may you please throw more light on this payment type so we can have a stronger use case > Loan repayment by account transfer transaction type should not be withdrawal > > > Key: FINERACT-1948 > URL: https://issues.apache.org/jira/browse/FINERACT-1948 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.7.0, 1.8.1, 1.7.2, 1.8.2, 1.8.3 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0, 1.8.4 > > Attachments: image-2023-07-31-23-11-05-824.png > > > When a user transfers money from a savings account to pay off a loan, the > transaction type is tagged as a withdrawal yet this is a loan repayment. The > transaction type should be adjusted to suit the transaction as it gets handy > for repayments with standing instructions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1948) Loan repayment by account transfer transaction type should not be withdrawal
[ https://issues.apache.org/jira/browse/FINERACT-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17749643#comment-17749643 ] Francis Guchie commented on FINERACT-1948: -- [~bgowda], [~BLasan] what do you think of this suggestion? This payment is from a savings account but not a basic withdrawal. And when a client signs up for standing instructions, this would be confusing for users and the client seeing withdrawal on their account, instead of loan repayment > Loan repayment by account transfer transaction type should not be withdrawal > > > Key: FINERACT-1948 > URL: https://issues.apache.org/jira/browse/FINERACT-1948 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.7.0, 1.8.1, 1.7.2, 1.8.2, 1.8.3 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0, 1.8.4 > > Attachments: image-2023-07-31-23-11-05-824.png > > > When a user transfers money from a savings account to pay off a loan, the > transaction type is tagged as a withdrawal yet this is a loan repayment. The > transaction type should be adjusted to suit the transaction as it gets handy > for repayments with standing instructions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1948) Loan repayment by account transfer transaction type should not be withdrawal
[ https://issues.apache.org/jira/browse/FINERACT-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1948: Assignee: Francis Guchie > Loan repayment by account transfer transaction type should not be withdrawal > > > Key: FINERACT-1948 > URL: https://issues.apache.org/jira/browse/FINERACT-1948 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.7.0, 1.8.1, 1.7.2, 1.8.2, 1.8.3 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0, 1.8.4 > > Attachments: image-2023-07-31-23-11-05-824.png > > > When a user transfers money from a savings account to pay off a loan, the > transaction type is tagged as a withdrawal yet this is a loan repayment. The > transaction type should be adjusted to suit the transaction as it gets handy > for repayments with standing instructions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
[ https://issues.apache.org/jira/browse/FINERACT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17748856#comment-17748856 ] Francis Guchie commented on FINERACT-1945: -- [~mkaitesi] [~ikimbrah] have you tested > UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing > -- > > Key: FINERACT-1945 > URL: https://issues.apache.org/jira/browse/FINERACT-1945 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.7.3 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2023-06-20-19-40-27-163.png, > image-2023-06-20-19-45-07-790.png > > > Jobs are failing to run and I think it is the Jobs that are duplicated on the > UI. > Something to consider trouble shooting > !image-2023-06-20-19-40-27-163.png! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1700) Bulk JLG loan Application not displaying loan terms
[ https://issues.apache.org/jira/browse/FINERACT-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1700: Assignee: Francis Guchie (was: Rahul Pawar) > Bulk JLG loan Application not displaying loan terms > --- > > Key: FINERACT-1700 > URL: https://issues.apache.org/jira/browse/FINERACT-1700 > Project: Apache Fineract > Issue Type: Bug > Components: Groups >Affects Versions: 1.7.0 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > Attachments: image-2022-08-21-15-31-25-813.png > > > During the bulk JLG loan application, procedures should follow as per the > documentation here, > [https://docs.mifos.org/mifosx/user-manual/for-operational-users-mifos-x-web-app/accounts-and-transactions/loan-accounts/how-to-process-bulk-jlg-loan-application] > However, after adding client loan amounts and submitting the application, the > system allows the application to go through without returning to the loan > terms page for the individual clients. This means that Incase of a charge > that requires a savings account, the validation will fail since the API does > not return the loan terms window for all the applied loans. > !image-2022-08-21-15-31-25-813.png|width=547,height=376! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1949) Access customer information accross a multiple branch institution
[ https://issues.apache.org/jira/browse/FINERACT-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1949: Assignee: Francis Guchie > Access customer information accross a multiple branch institution > - > > Key: FINERACT-1949 > URL: https://issues.apache.org/jira/browse/FINERACT-1949 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.7.0, 1.8.3 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > > Currently, the fineract allows a scope of branch teams to access branch > information unless they're added at head office. This feature should however > be extended to make sure that customers of a particular branch can be served > at another branch. Cases include doing deposits and withdrawals. > [~francisguchie] and [~bgowda] whats your take on this? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
[ https://issues.apache.org/jira/browse/FINERACT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17748713#comment-17748713 ] Francis Guchie commented on FINERACT-1945: -- [~bgowda] I have more than 2 live environments showing these duplicates. I have already made a [PR-3337|https://github.com/apache/fineract/pull/3337] that addresses this issue. Look out for the Job called *"Execute all Dirty Jobs"* this job once it runs it re-creates entries inside the table called JobRunHistory. Once this happens you will start having duplicate jobs displayed. > UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing > -- > > Key: FINERACT-1945 > URL: https://issues.apache.org/jira/browse/FINERACT-1945 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.7.3 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2023-06-20-19-40-27-163.png, > image-2023-06-20-19-45-07-790.png > > > Jobs are failing to run and I think it is the Jobs that are duplicated on the > UI. > Something to consider trouble shooting > !image-2023-06-20-19-40-27-163.png! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1897) Creating a Share Account - Internal server error
[ https://issues.apache.org/jira/browse/FINERACT-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1897: Assignee: Francis Guchie (was: Rahul Pawar) > Creating a Share Account - Internal server error > > > Key: FINERACT-1897 > URL: https://issues.apache.org/jira/browse/FINERACT-1897 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.7.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > > When a user creates a new share account they get an internal server error at > submission of the share creation > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1950) Disallow backdated transactions after COB
[ https://issues.apache.org/jira/browse/FINERACT-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1950: Assignee: Francis Guchie > Disallow backdated transactions after COB > - > > Key: FINERACT-1950 > URL: https://issues.apache.org/jira/browse/FINERACT-1950 > Project: Apache Fineract > Issue Type: Improvement >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > > We need to have a global configuration to disallow backdated transactions for > a given period without necessarily closing an accounting period in the > closing entries. > A use case of a teller not being allowed to post a backdated transaction on a > customer after the till was balanced or after COB. The accountant can however > have the right to post GL transactions on a back date. > > This should however be set as a global configuration that can be turned on > and off. > > [~francisguchie] and [~bgowda] and [~eroemma] what do you think of this > improvement? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1944) interest recalculation only when client pays early - do not recalculate if payment is on time or late (so that interest remains the same)
[ https://issues.apache.org/jira/browse/FINERACT-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1944: Assignee: Francis Guchie (was: Rahul Pawar) > interest recalculation only when client pays early - do not recalculate if > payment is on time or late (so that interest remains the same) > - > > Key: FINERACT-1944 > URL: https://issues.apache.org/jira/browse/FINERACT-1944 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > > As a client of a financial institution i would like to see the following > among others for my loan > * *Interest Method: Declining Balance* > * *Interest recalculation: Enabled* - When I pay my installments before due > date, the system should follow the standard of recalculating my interest > downwards. When I pay late the system does not recalculate (or lets say it > does but ignores updating my interest upwards. > [~ikimbrah] [~bgowda] is this a viable new feature? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1951) Add filter on cashier teller management for transactions
[ https://issues.apache.org/jira/browse/FINERACT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741405#comment-17741405 ] Francis Guchie commented on FINERACT-1951: -- [~ikimbrah] I strongly agree but this is what we need to note: This section works best for a real-time scenario this section is a challenge for MFIs that always run late and cannot afford to do work in realtime So we need to factor these considerations when making adjustments > Add filter on cashier teller management for transactions > > > Key: FINERACT-1951 > URL: https://issues.apache.org/jira/browse/FINERACT-1951 > Project: Apache Fineract > Issue Type: Improvement > Environment: Mifos community App 21.07.3 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > Attachments: image-2023-07-09-18-24-49-473.png, > image-2023-07-09-18-26-53-403.png > > > In the cashier teller management module, the cashier may need to filter and > reconcile balances on a daily basis side the cashier teller module. For this > to be achieved, there need to be filters that allow the user to d so as per > the screenshot below > !image-2023-07-09-18-26-53-403.png|width=587,height=405! > > Filter for; > * Transaction type either cash in or cashout > * Transaction date > * Transaction ID > We also need to change the layout to have the last transaction on the first > page. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1951) Add filter on cashier teller management for transactions
[ https://issues.apache.org/jira/browse/FINERACT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1951: Assignee: Francis Guchie > Add filter on cashier teller management for transactions > > > Key: FINERACT-1951 > URL: https://issues.apache.org/jira/browse/FINERACT-1951 > Project: Apache Fineract > Issue Type: Improvement > Environment: Mifos community App 21.07.3 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > Attachments: image-2023-07-09-18-24-49-473.png, > image-2023-07-09-18-26-53-403.png > > > In the cashier teller management module, the cashier may need to filter and > reconcile balances on a daily basis side the cashier teller module. For this > to be achieved, there need to be filters that allow the user to d so as per > the screenshot below > !image-2023-07-09-18-26-53-403.png|width=587,height=405! > > Filter for; > * Transaction type either cash in or cashout > * Transaction date > * Transaction ID > We also need to change the layout to have the last transaction on the first > page. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
[ https://issues.apache.org/jira/browse/FINERACT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741217#comment-17741217 ] Francis Guchie commented on FINERACT-1945: -- [~bgowda] this is the API that creates the challenge [https://servername_or_IP/fineract-provider/api/v1/jobs|https://livedemo.lcf-ltd.net/fineract-provider/api/v1/jobs] when called you will see that 2 job with id 2 and id 7 are duplicated in the list. And yet it is this list that the scheduler uses to run the jobs > UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing > -- > > Key: FINERACT-1945 > URL: https://issues.apache.org/jira/browse/FINERACT-1945 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.7.3 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2023-06-20-19-40-27-163.png, > image-2023-06-20-19-45-07-790.png > > > Jobs are failing to run and I think it is the Jobs that are duplicated on the > UI. > Something to consider trouble shooting > !image-2023-06-20-19-40-27-163.png! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
[ https://issues.apache.org/jira/browse/FINERACT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1945: Assignee: Francis Guchie > UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing > -- > > Key: FINERACT-1945 > URL: https://issues.apache.org/jira/browse/FINERACT-1945 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.7.3 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2023-06-20-19-40-27-163.png, > image-2023-06-20-19-45-07-790.png > > > Jobs are failing to run and I think it is the Jobs that are duplicated on the > UI. > Something to consider trouble shooting > !image-2023-06-20-19-40-27-163.png! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
[ https://issues.apache.org/jira/browse/FINERACT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735656#comment-17735656 ] Francis Guchie commented on FINERACT-1945: -- [~bgowda] Incidentally the jobs in table job are not duplicated. Nevertheless, I think it is the api that lists them up for job scheduling that duplicates the calls > UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing > -- > > Key: FINERACT-1945 > URL: https://issues.apache.org/jira/browse/FINERACT-1945 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.7.3 >Reporter: Francis Guchie >Priority: Major > Attachments: image-2023-06-20-19-40-27-163.png, > image-2023-06-20-19-45-07-790.png > > > Jobs are failing to run and I think it is the Jobs that are duplicated on the > UI. > Something to consider trouble shooting > !image-2023-06-20-19-40-27-163.png! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
[ https://issues.apache.org/jira/browse/FINERACT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735431#comment-17735431 ] Francis Guchie edited comment on FINERACT-1945 at 6/20/23 7:45 PM: --- [~bgowda] [~ikimbrah] We have to look into this I have noticed one job failing for the last one month and I cannot explain why it is failing. When i trigger it on its own it runs just fine. when i leave it to run as per the scheduler. This error tells us that another job is locking the access I get the error below *org.springframework.dao.CannotAcquireLockException:* *StatementCallback; SQL [UPDATE m_loan as ml , (select loan.id FROM m_loan_arrears_aging laa INNER JOIN m_loan loan on laa.loan_id = loan.id INNER JOIN m_product_loan mpl on mpl.id = loan.product_id AND mpl.overdue_days_for_npa is not null WHERE loan.loan_status_id = 300 and laa.overdue_since_date_derived < DATE_SUB(CURDATE(), INTERVAL COALESCE(mpl.overdue_days_for_npa, 0) day) group by loan.id) as sl SET ml.is_npa = true where ml.id=sl.id ];* *(conn=49120) Lock wait timeout exceeded;* *try restarting transaction;* *nested exception is java.sql.SQLTransientConnectionException: (conn=49120) Lock wait timeout exceeded; try restarting transaction* *at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(267)* *at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(70)* *at org.springframework.jdbc.core.JdbcTemplate.translateException(1541)* *at org.springframework.jdbc.core.JdbcTemplate.execute(393)* *at org.springframework.jdbc.core.JdbcTemplate.update(558)* *at org.apache.fineract.scheduledjobs.service.ScheduledJobRunnerServiceImpl.updateNPA(207)* *at org.apache.fineract.scheduledjobs.service.ScheduledJobRunnerServiceImpl$$FastClassBySpringCGLIB$$80bbf4b3.invoke(-1)* *at org.springframework.cglib.proxy.MethodProxy.invoke(218)* *at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(793)* *at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(163)* *at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(763)* *at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(123)* *at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(388)* *at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(119)* *at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(186)* *at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(763)* *at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(708)* *at* A deeper search shows that this job has been running in duplicates for a while see image below !image-2023-06-20-19-45-07-790.png! was (Author: francisguchie): [~bgowda] [~ikimbrah] We have to look into this I have noticed one job failing for the last one month and I cannot explain why it is failing. When i trigger it on its own it runs just fine. when i leave it to run as per the schedular, I get the error below *org.springframework.dao.CannotAcquireLockException:* *StatementCallback; SQL [UPDATE m_loan as ml , (select loan.id FROM m_loan_arrears_aging laa INNER JOIN m_loan loan on laa.loan_id = loan.id INNER JOIN m_product_loan mpl on mpl.id = loan.product_id AND mpl.overdue_days_for_npa is not null WHERE loan.loan_status_id = 300 and laa.overdue_since_date_derived < DATE_SUB(CURDATE(), INTERVAL COALESCE(mpl.overdue_days_for_npa, 0) day) group by loan.id) as sl SET ml.is_npa = true where ml.id=sl.id ];* *(conn=49120) Lock wait timeout exceeded;* *try restarting transaction;* *nested exception is java.sql.SQLTransientConnectionException: (conn=49120) Lock wait timeout exceeded; try restarting transaction* *at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(267)* *at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(70)* *at org.springframework.jdbc.core.JdbcTemplate.translateException(1541)* *at org.springframework.jdbc.core.JdbcTemplate.execute(393)* *at org.springframework.jdbc.core.JdbcTemplate.update(558)* *at org.apache.fineract.scheduledjobs.service.ScheduledJobRunnerServiceImpl.updateNPA(207)* *at org.apache.fineract.scheduledjobs.service.ScheduledJobRunnerServiceImpl$$FastClassBySpringCGLIB$$80bbf4b3.invoke(-1)* *at org.springframework.cglib.proxy.MethodProxy.invoke(218)* *at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(793)* *at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(163)* *at
[jira] [Commented] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
[ https://issues.apache.org/jira/browse/FINERACT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17735431#comment-17735431 ] Francis Guchie commented on FINERACT-1945: -- [~bgowda] [~ikimbrah] We have to look into this I have noticed one job failing for the last one month and I cannot explain why it is failing. When i trigger it on its own it runs just fine. when i leave it to run as per the schedular, I get the error below *org.springframework.dao.CannotAcquireLockException:* *StatementCallback; SQL [UPDATE m_loan as ml , (select loan.id FROM m_loan_arrears_aging laa INNER JOIN m_loan loan on laa.loan_id = loan.id INNER JOIN m_product_loan mpl on mpl.id = loan.product_id AND mpl.overdue_days_for_npa is not null WHERE loan.loan_status_id = 300 and laa.overdue_since_date_derived < DATE_SUB(CURDATE(), INTERVAL COALESCE(mpl.overdue_days_for_npa, 0) day) group by loan.id) as sl SET ml.is_npa = true where ml.id=sl.id ];* *(conn=49120) Lock wait timeout exceeded;* *try restarting transaction;* *nested exception is java.sql.SQLTransientConnectionException: (conn=49120) Lock wait timeout exceeded; try restarting transaction* *at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(267)* *at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(70)* *at org.springframework.jdbc.core.JdbcTemplate.translateException(1541)* *at org.springframework.jdbc.core.JdbcTemplate.execute(393)* *at org.springframework.jdbc.core.JdbcTemplate.update(558)* *at org.apache.fineract.scheduledjobs.service.ScheduledJobRunnerServiceImpl.updateNPA(207)* *at org.apache.fineract.scheduledjobs.service.ScheduledJobRunnerServiceImpl$$FastClassBySpringCGLIB$$80bbf4b3.invoke(-1)* *at org.springframework.cglib.proxy.MethodProxy.invoke(218)* *at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(793)* *at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(163)* *at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(763)* *at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(123)* *at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(388)* *at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(119)* *at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(186)* *at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(763)* *at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(708)* *at* > UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing > -- > > Key: FINERACT-1945 > URL: https://issues.apache.org/jira/browse/FINERACT-1945 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.7.3 >Reporter: Francis Guchie >Priority: Major > Attachments: image-2023-06-20-19-40-27-163.png > > > Jobs are failing to run and I think it is the Jobs that are duplicated on the > UI. > Something to consider trouble shooting > !image-2023-06-20-19-40-27-163.png! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
[ https://issues.apache.org/jira/browse/FINERACT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1945: - Affects Version/s: 1.7.3 > UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing > -- > > Key: FINERACT-1945 > URL: https://issues.apache.org/jira/browse/FINERACT-1945 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.7.3 >Reporter: Francis Guchie >Priority: Major > Attachments: image-2023-06-20-19-40-27-163.png > > > Jobs are failing to run and I think it is the Jobs that are duplicated on the > UI. > Something to consider trouble shooting > !image-2023-06-20-19-40-27-163.png! > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1945) UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing
Francis Guchie created FINERACT-1945: Summary: UI Shows Duplicate Scheduler Jobs - a reason some jobs are failing Key: FINERACT-1945 URL: https://issues.apache.org/jira/browse/FINERACT-1945 Project: Apache Fineract Issue Type: Bug Reporter: Francis Guchie Attachments: image-2023-06-20-19-40-27-163.png Jobs are failing to run and I think it is the Jobs that are duplicated on the UI. Something to consider trouble shooting !image-2023-06-20-19-40-27-163.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1944) interest recalculation only when client pays early - do not recalculate if payment is on time or late (so that interest remains the same)
[ https://issues.apache.org/jira/browse/FINERACT-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1944: Assignee: Rahul Pawar > interest recalculation only when client pays early - do not recalculate if > payment is on time or late (so that interest remains the same) > - > > Key: FINERACT-1944 > URL: https://issues.apache.org/jira/browse/FINERACT-1944 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > > As a client of a financial institution i would like to see the following > among others for my loan > * *Interest Method: Declining Balance* > * *Interest recalculation: Enabled* - When I pay my installments before due > date, the system should follow the standard of recalculating my interest > downwards. When I pay late the system does not recalculate (or lets say it > does but ignores updating my interest upwards. > [~ikimbrah] [~bgowda] is this a viable new feature? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1944) interest recalculation only when client pays early - do not recalculate if payment is on time or late (so that interest remains the same)
Francis Guchie created FINERACT-1944: Summary: interest recalculation only when client pays early - do not recalculate if payment is on time or late (so that interest remains the same) Key: FINERACT-1944 URL: https://issues.apache.org/jira/browse/FINERACT-1944 Project: Apache Fineract Issue Type: New Feature Reporter: Francis Guchie As a client of a financial institution i would like to see the following among others for my loan * *Interest Method: Declining Balance* * *Interest recalculation: Enabled* - When I pay my installments before due date, the system should follow the standard of recalculating my interest downwards. When I pay late the system does not recalculate (or lets say it does but ignores updating my interest upwards. [~ikimbrah] [~bgowda] is this a viable new feature? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1752) Undo Transfer transactions
[ https://issues.apache.org/jira/browse/FINERACT-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17731196#comment-17731196 ] Francis Guchie commented on FINERACT-1752: -- [~ikimbrah] This is the issue we discussed in the morning > Undo Transfer transactions > -- > > Key: FINERACT-1752 > URL: https://issues.apache.org/jira/browse/FINERACT-1752 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan, Savings >Affects Versions: 1.4.0, 1.5.0, 1.7.0, 1.8.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-09-21-13-54-23-648.png, > image-2022-09-21-13-56-33-027.png, image-2022-09-21-14-01-57-321.png, > image-2022-09-21-14-15-07-083.png > > > A user can make a loan repayment from a savings account, using the transfer > transaction API. But this cannot be undone. > on the savings account transactions side the undo button is not seen > !image-2022-09-21-13-54-23-648.png|width=564,height=177! > on the loan transactions side the undo and edit are visible > !image-2022-09-21-13-56-33-027.png|width=522,height=171! > However, this does not depict the real details of this loan transaction > I would expect the following > 1- on the savings account transactions i expect the transaction to show the > transfer details and the Undo button - the Undo button should only allow the > undo if the this is a savings to savings transfer > !image-2022-09-21-14-01-57-321.png|width=559,height=244! > 2- on the loan account transactions i expect the transaction to show the > transfer details and the Undo button > !image-2022-09-21-14-15-07-083.png|width=562,height=114! > 3- the Undo button should all user to undo the transaction so that the loan > and the savings balances are restored to initial values before the transfer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel=17729734#comment-17729734 ] Francis Guchie commented on FINERACT-657: - Yes [~bgowda] I want to concentrate on this part you have mentioned *We can use the method of completing the job for all loans (where the positive cases loans can get processed and let the system show the failed loans list at the end of the job* I will see if a PR can be raised sooner so it can be merged in the next release > 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.8.0, 1.8.1, 1.8.2, 1.7.3 >Reporter: Santosh Math >Assignee: Rahul Pawar >Priority: Major > Labels: p2 > Fix For: 1.9.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-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 ] Francis Guchie updated FINERACT-657: Affects Version/s: 1.8.2 1.8.1 1.7.3 > 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.8.0, 1.8.1, 1.8.2, 1.7.3 >Reporter: Santosh Math >Assignee: Rahul Pawar >Priority: Major > Labels: p2 > Fix For: 1.9.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] [Comment Edited] (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:comment-tabpanel=17729692#comment-17729692 ] Francis Guchie edited comment on FINERACT-657 at 6/6/23 11:23 AM: -- [~rrpawar] [~ikimbrah] [~mkaitesi] [~eroemma] I think we just saw this yesterday, and there is a new twist to this to that is connected to FINERACT-894, So besides taking out what is left on the account, we need to also consider the other problem. If or during the cron job, if one of the accounts has insufficient funds, all the other accounts are ignored and the system will just provide the error log. For a successful cron job of standing instructions, all the accounts in the batch should have enough balances. I think the approach used is *"ALL OR NOTHING"* [~bgowda] have you experienced this before?? was (Author: francisguchie): [~rrpawar] [~ikimbrah] [~mkaitesi] [~eroemma] I think we just saw this yesterday, and there is a new twist to this to that is connected to FINERACT-894, So besides taking out what is left on the account, we need to also consider the other problem. If or during the cron job, if one of the accounts has insufficient funds, all the other accounts are ignored and the system will just provide the error log. For a successful cron job of standing instructions, all the accounts in the batch should have enough balances. I think the approach used is *"ALL OR NOTHING"* > 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.8.0 >Reporter: Santosh Math >Assignee: Rahul Pawar >Priority: Major > Labels: p2 > Fix For: 1.9.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] [Commented] (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:comment-tabpanel=17729692#comment-17729692 ] Francis Guchie commented on FINERACT-657: - [~rrpawar] [~ikimbrah] [~mkaitesi] [~eroemma] I think we just saw this yesterday, and there is a new twist to this to that is connected to FINERACT-894, So besides taking out what is left on the account, we need to also consider the other problem. If or during the cron job, if one of the accounts has insufficient funds, all the other accounts are ignored and the system will just provide the error log. For a successful cron job of standing instructions, all the accounts in the batch should have enough balances. I think the approach used is *"ALL OR NOTHING"* > 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.8.0 >Reporter: Santosh Math >Assignee: Rahul Pawar >Priority: Major > Labels: p2 > Fix For: 1.9.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] [Comment Edited] (FINERACT-894) Scheduler Jobs Issue
[ https://issues.apache.org/jira/browse/FINERACT-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729687#comment-17729687 ] Francis Guchie edited comment on FINERACT-894 at 6/6/23 11:16 AM: -- [~vorburger] & [~bgowda] I have resurrected this issue as it is an issue that cron jobs for charges follow the *"ALL or Nothing"* approach. during a cron job execution, if one of the accounts being updated fails, the whole cron job is cancelled and an error message provide. We should find a solution to skip that one account and continue and keep a log of all failed accounts [~ikimbrah] [~rrpawar] I know we have discussed this for a long time even in apache-fineract 1.7.3 it still exists. this relates to FINERACT-657 was (Author: francisguchie): [~vorburger] I have resurrected this issue as it is an issue that cron jobs for charges follow the *"ALL or Nothing"* approach. during a cron job execution, if one of the accounts being updated fails, the whole cron job is cancelled and an error message provide. We should find a solution to skip that one account and continue and keep a log of all failed accounts [~ikimbrah] [~rrpawar] I know we have discussed this for a long time even in apache-fineract 1.7.3 it still exists. this relates to [FINERACT-657|https://issues.apache.org/jira/browse/FINERACT-657] > Scheduler Jobs Issue > > > Key: FINERACT-894 > URL: https://issues.apache.org/jira/browse/FINERACT-894 > Project: Apache Fineract > Issue Type: Bug > Components: Job Scheduler >Affects Versions: 1.8.0, 1.8.1, 1.7.2, 1.8.2, 1.8.3, 1.8.4, 1.7.3 >Reporter: Bharath Gowda >Assignee: Rahul Pawar >Priority: Critical > Attachments: Local Build Succes.png, Traivs Failure.png > > > Following Scheduler Jobs are failing for the below mentioned scenario > 1.Execute standing instruction Job > 2.Pay Due Saving charge > > Scenario: > if there is a single savings account with insufficient balance, then Job is > failing and not processing its tasks for rest of the loans as well in the > system. > > Expected behavior :Jobs should successfully execute it's task for all the > accounts and show the error message of accounts for which there was > insufficient amount. > > Steps to Reproduce > :For "Pay Due Saving charge" Job > 1.Create a Basic Savings account with deposit amount 1000 and add a monthly > charge of 5000. > 2.Create second savings account with deposit amount 1000 and add a monthly > charge of 500. > > then execute the "Pay Due Saving charge" Job, system should actually post the > charge for second saving account and through the error message for first > savings account. but system is not posting the charge for any of the loans. > > :For "Execute standing instruction Job" Job > 1.For client A - create a savings account with 100 balance, create a loan > with EMI of 1000 and add a standing instruction for the client to transfer > money from savings account to loan account on duedate. > > 2.For client B - create a savings account with 1000 balance, create a loan > with EMI of 1000 and add a standing instruction for the client to transfer > money from savings account to loan account on duedate. > then execute the "Execute standing instruction Job" Job, system should > actually post the transactions from savings to loan for client B and fail for > client A(due to insufficient fund) but as of the job is failing for both > clients. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-894) Scheduler Jobs Issue
[ https://issues.apache.org/jira/browse/FINERACT-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-894: --- Affects Version/s: 1.8.3 1.8.2 1.7.2 1.8.1 1.8.0 1.8.4 1.7.3 Assignee: Rahul Pawar (was: Nazeer Shaik) > Scheduler Jobs Issue > > > Key: FINERACT-894 > URL: https://issues.apache.org/jira/browse/FINERACT-894 > Project: Apache Fineract > Issue Type: Bug > Components: Job Scheduler >Affects Versions: 1.8.0, 1.8.1, 1.7.2, 1.8.2, 1.8.3, 1.8.4, 1.7.3 >Reporter: Bharath Gowda >Assignee: Rahul Pawar >Priority: Critical > Attachments: Local Build Succes.png, Traivs Failure.png > > > Following Scheduler Jobs are failing for the below mentioned scenario > 1.Execute standing instruction Job > 2.Pay Due Saving charge > > Scenario: > if there is a single savings account with insufficient balance, then Job is > failing and not processing its tasks for rest of the loans as well in the > system. > > Expected behavior :Jobs should successfully execute it's task for all the > accounts and show the error message of accounts for which there was > insufficient amount. > > Steps to Reproduce > :For "Pay Due Saving charge" Job > 1.Create a Basic Savings account with deposit amount 1000 and add a monthly > charge of 5000. > 2.Create second savings account with deposit amount 1000 and add a monthly > charge of 500. > > then execute the "Pay Due Saving charge" Job, system should actually post the > charge for second saving account and through the error message for first > savings account. but system is not posting the charge for any of the loans. > > :For "Execute standing instruction Job" Job > 1.For client A - create a savings account with 100 balance, create a loan > with EMI of 1000 and add a standing instruction for the client to transfer > money from savings account to loan account on duedate. > > 2.For client B - create a savings account with 1000 balance, create a loan > with EMI of 1000 and add a standing instruction for the client to transfer > money from savings account to loan account on duedate. > then execute the "Execute standing instruction Job" Job, system should > actually post the transactions from savings to loan for client B and fail for > client A(due to insufficient fund) but as of the job is failing for both > clients. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-894) Scheduler Jobs Issue
[ https://issues.apache.org/jira/browse/FINERACT-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729687#comment-17729687 ] Francis Guchie commented on FINERACT-894: - [~vorburger] I have resurrected this issue as it is an issue that cron jobs for charges follow the *"ALL or Nothing"* approach. during a cron job execution, if one of the accounts being updated fails, the whole cron job is cancelled and an error message provide. We should find a solution to skip that one account and continue and keep a log of all failed accounts [~ikimbrah] [~rrpawar] I know we have discussed this for a long time even in apache-fineract 1.7.3 it still exists. this relates to [FINERACT-657|https://issues.apache.org/jira/browse/FINERACT-657] > Scheduler Jobs Issue > > > Key: FINERACT-894 > URL: https://issues.apache.org/jira/browse/FINERACT-894 > Project: Apache Fineract > Issue Type: Bug > Components: Job Scheduler >Reporter: Bharath Gowda >Assignee: Nazeer Shaik >Priority: Critical > Attachments: Local Build Succes.png, Traivs Failure.png > > > Following Scheduler Jobs are failing for the below mentioned scenario > 1.Execute standing instruction Job > 2.Pay Due Saving charge > > Scenario: > if there is a single savings account with insufficient balance, then Job is > failing and not processing its tasks for rest of the loans as well in the > system. > > Expected behavior :Jobs should successfully execute it's task for all the > accounts and show the error message of accounts for which there was > insufficient amount. > > Steps to Reproduce > :For "Pay Due Saving charge" Job > 1.Create a Basic Savings account with deposit amount 1000 and add a monthly > charge of 5000. > 2.Create second savings account with deposit amount 1000 and add a monthly > charge of 500. > > then execute the "Pay Due Saving charge" Job, system should actually post the > charge for second saving account and through the error message for first > savings account. but system is not posting the charge for any of the loans. > > :For "Execute standing instruction Job" Job > 1.For client A - create a savings account with 100 balance, create a loan > with EMI of 1000 and add a standing instruction for the client to transfer > money from savings account to loan account on duedate. > > 2.For client B - create a savings account with 1000 balance, create a loan > with EMI of 1000 and add a standing instruction for the client to transfer > money from savings account to loan account on duedate. > then execute the "Execute standing instruction Job" Job, system should > actually post the transactions from savings to loan for client B and fail for > client A(due to insufficient fund) but as of the job is failing for both > clients. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FINERACT-1851) Modify ReadMe.md to address default character set issue with windows
[ https://issues.apache.org/jira/browse/FINERACT-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie closed FINERACT-1851. Fix Version/s: 1.8.4 1.7.3 1.8.3 1.8.2 (was: 1.9.0) Resolution: Fixed Fixed > Modify ReadMe.md to address default character set issue with windows > > > Key: FINERACT-1851 > URL: https://issues.apache.org/jira/browse/FINERACT-1851 > Project: Apache Fineract > Issue Type: Improvement > Components: Docs >Affects Versions: 1.8.2 > Environment: Windows >Reporter: Kigenyi Wilfred >Priority: Blocker > Labels: documentation > Fix For: 1.8.4, 1.7.3, 1.8.3, 1.8.2 > > > When creating databases and tables with mysql/mariadb on Windows servers, the > default character set is UTF8MB3. The character set UTF8MB3 allows for > columns to store up to 3 bytes. > The display_symbol column in the fineract_default.m_currency table requires > 4bytes, so if the default character set is used when creating the database > fineract_default with the following command: > _CREATE DATABASE fineract_default_ > then the migration script to insert the currencies will fail with an error > similar to: > _Incorrect string value: `\xE2\x82\xA1` for column display_symbol ..._ > To rectify this, the default character set has to be overridden when creating > the fineract_default database with the following command > _CREATE DATABASE fineract_default_ CHARACTER SET utf8mb4 > This allows for the 4bytes needed to store the data in the > m_currency.display_symbol and the migration script will run just fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1851) Modify ReadMe.md to address default character set issue with windows
[ https://issues.apache.org/jira/browse/FINERACT-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726784#comment-17726784 ] Francis Guchie commented on FINERACT-1851: -- Thank you [~kigred.developer] , I have been deploying on windows alike with no more issues for the currency is mentioned by you. Its a +1 from me that this has been resolved. Kindly advise if I should close this as resolved > Modify ReadMe.md to address default character set issue with windows > > > Key: FINERACT-1851 > URL: https://issues.apache.org/jira/browse/FINERACT-1851 > Project: Apache Fineract > Issue Type: Improvement > Components: Docs >Affects Versions: 1.8.2 > Environment: Windows >Reporter: Kigenyi Wilfred >Priority: Blocker > Labels: documentation > Fix For: 1.9.0 > > > When creating databases and tables with mysql/mariadb on Windows servers, the > default character set is UTF8MB3. The character set UTF8MB3 allows for > columns to store up to 3 bytes. > The display_symbol column in the fineract_default.m_currency table requires > 4bytes, so if the default character set is used when creating the database > fineract_default with the following command: > _CREATE DATABASE fineract_default_ > then the migration script to insert the currencies will fail with an error > similar to: > _Incorrect string value: `\xE2\x82\xA1` for column display_symbol ..._ > To rectify this, the default character set has to be overridden when creating > the fineract_default database with the following command > _CREATE DATABASE fineract_default_ CHARACTER SET utf8mb4 > This allows for the 4bytes needed to store the data in the > m_currency.display_symbol and the migration script will run just fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1392) JOINT ACCOUNTS
[ https://issues.apache.org/jira/browse/FINERACT-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1392: - Affects Version/s: 16 1.8 1.7.0 1.6.0 > JOINT ACCOUNTS > -- > > Key: FINERACT-1392 > URL: https://issues.apache.org/jira/browse/FINERACT-1392 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0, > 16, 1.8 >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Critical > Attachments: image-2021-08-26-20-32-59-026.png, > image-2022-06-29-20-58-44-963.png > > > How does Fineract handle joint accounts (which are not a group account)? > As a user i would like to have a savings account in which we have more than > one signatory -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1924) Denominations on the Transactions Screen
Francis Guchie created FINERACT-1924: Summary: Denominations on the Transactions Screen Key: FINERACT-1924 URL: https://issues.apache.org/jira/browse/FINERACT-1924 Project: Apache Fineract Issue Type: Improvement Components: Organization Affects Versions: 1.9.0 Reporter: Francis Guchie Intended output # Globaly configured disabled or not ( if configured it becomes mandatory) # Cash movement between Cashiers # Cash Allocation or settlement to a Cashier -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1924) Denominations on the Transactions Screen
[ https://issues.apache.org/jira/browse/FINERACT-1924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1924: Assignee: Francis Guchie > Denominations on the Transactions Screen > > > Key: FINERACT-1924 > URL: https://issues.apache.org/jira/browse/FINERACT-1924 > Project: Apache Fineract > Issue Type: Improvement > Components: Organization >Affects Versions: 1.9.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > > Intended output > # Globaly configured disabled or not ( if configured it becomes mandatory) > # Cash movement between Cashiers > # Cash Allocation or settlement to a Cashier -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1171) Multi-module configuration for Gradle
[ https://issues.apache.org/jira/browse/FINERACT-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17710281#comment-17710281 ] Francis Guchie commented on FINERACT-1171: -- [~aleks] [~vorburger] [~ptuomola] I just read through this resolved issue and I am amazed. Thank you all for this great work. I see all issues resolved but i cant not go without saying thank you ..:D > Multi-module configuration for Gradle > - > > Key: FINERACT-1171 > URL: https://issues.apache.org/jira/browse/FINERACT-1171 > Project: Apache Fineract > Issue Type: Improvement > Components: Build >Affects Versions: 1.5.0 >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.5.0 > > Attachments: image-2020-10-08-21-19-43-775.png, > image-2020-10-08-21-43-03-567.png, image-2020-10-08-21-48-56-177.png, > image-2020-10-08-21-52-46-940.png > > > Use the build.gradle file in the root folder rather than in fineract-provider > to import the project in IDEs. > Note: this will force everyone to re-import the project in their IDEs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1451) Beneficiary: unable to add a second beneficiary (same name as first, but different accountNo/currency)
[
https://issues.apache.org/jira/browse/FINERACT-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francis Guchie reassigned FINERACT-1451:
Assignee: Francis Guchie
> Beneficiary: unable to add a second beneficiary (same name as first, but
> different accountNo/currency)
> --
>
> Key: FINERACT-1451
> URL: https://issues.apache.org/jira/browse/FINERACT-1451
> Project: Apache Fineract
> Issue Type: Bug
> Components: Database
>Affects Versions: 1.5.0
>Reporter: Thomas Kerin
>Assignee: Francis Guchie
>Priority: Major
>
> The 'name' index on the m_selfservice_beneficiaries_tpt table prevents a
> client from adding two
>
> {{Server error:}}
> {{{}Duplicate entry 'Clint Westwood-4-\x01' for key 'name' {prepstmnt
> 128161655 INSERT INTO m_selfservice_beneficiaries_tpt (account_id,
> account_type, ap{}}}{{{}p_user_id, client_id, is_active, name, office_id,
> transfer_limit) VALUES (?, ?, ?, ?, ?, ?, ?, ?)} [code=1062, state=23000]{}}}
>
> {{mysql> show index from m_selfservice_beneficiaries_tpt;}}
> {{{+}{-}{-}{+}--{-}++{-}{-}{-}{-}++{-}---{-}{-}-{-}++{-}---{-}{-}{-}++{-}--{-}{-}{-}++{-}--{-}{-}---{-}++{-}--}}
> {{| Table | Non_unique | Key_name | Seq_in_index |
> Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type
> | Comment | Index_comment |}}
> {{{+}{-}{-}{+}--{-}++{-}{-}{-}{-}++{-}---{-}{-}-{-}++{-}---{-}{-}{-}++{-}--{-}{-}{-}++{-}--{-}{-}---{-}++{-}--}}
> {{| m_selfservice_beneficiaries_tpt | 0 | PRIMARY | 1 |
> id | A | 1 | NULL | NULL | | BTREE
> | | |}}
> {{| m_selfservice_beneficiaries_tpt | 0 | name | 1 |
> name | A | 1 | NULL | NULL | | BTREE
> | | |}}
> {{| m_selfservice_beneficiaries_tpt | 0 | name | 2 |
> app_user_id | A | 1 | NULL | NULL | | BTREE
> | | |}}
> {{| m_selfservice_beneficiaries_tpt | 0 | name | 3 |
> is_active | A | 1 | NULL | NULL | | BTREE
> | | |}}
> {{{+}{-}{-}{+}--{-}++{-}{-}{-}{-}++{-}---{-}{-}-{-}++{-}---{-}{-}{-}++{-}--{-}{-}{-}++{-}--{-}{-}---{-}++{-}--}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FINERACT-578) Year end -Accounting
[ https://issues.apache.org/jira/browse/FINERACT-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-578: --- Assignee: Francis Guchie > Year end -Accounting > -- > > Key: FINERACT-578 > URL: https://issues.apache.org/jira/browse/FINERACT-578 > Project: Apache Fineract > Issue Type: Bug >Reporter: sangamesh >Assignee: Francis Guchie >Priority: Major > Labels: Roadmap2022 > > Year end -Accounting process- Should provide year ending wherein after year > ending all the profits and expense booked will be for that year only. But as > now it's been carried out for next year too. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1831) Tenant passwd encryption
[
https://issues.apache.org/jira/browse/FINERACT-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699797#comment-17699797
]
Francis Guchie commented on FINERACT-1831:
--
[~mdallos]
this is a nice improvement
> Tenant passwd encryption
>
>
> Key: FINERACT-1831
> URL: https://issues.apache.org/jira/browse/FINERACT-1831
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Mihaly Dallos
>Priority: Major
>
> {panel}
> *As a* _Fineract operator_
> *I want to* store tenant passwords encrypted
> *in order to* _reduce security risk_
> {panel}
> h4. *Background and details:*
> Tenant passwords are stored in plain text in the database. It should be
> encrypted to disable accidental share/access.…
> {panel}
> *Acceptance criteria*
> # Tenant passwords are encrypted in the {{fineract_tenants}} schema
> # Tenant passwords are encrypted with AES encryption using Java (not the DB
> level encryption)
> # The AES mode is CBC ({{{}AES/CBC/PKCS5Padding){}}}
> # Existing tenants are migrated over to encrypted passwords seamlessly
> # The master password and initialization vector (IV) for encrypting the data
> can be configured via environment variables
> # The encryption for tenant passwords cannot be turned off{panel}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FINERACT-1897) Creating a Share Account - Internal server error
[ https://issues.apache.org/jira/browse/FINERACT-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1897: Assignee: Rahul Pawar > Creating a Share Account - Internal server error > > > Key: FINERACT-1897 > URL: https://issues.apache.org/jira/browse/FINERACT-1897 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.7.0 >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > > When a user creates a new share account they get an internal server error at > submission of the share creation > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1897) Creating a Share Account - Internal server error
[ https://issues.apache.org/jira/browse/FINERACT-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690949#comment-17690949 ] Francis Guchie commented on FINERACT-1897: -- [~ikimbrah] [~mkaitesi] have you tested shares before?? > Creating a Share Account - Internal server error > > > Key: FINERACT-1897 > URL: https://issues.apache.org/jira/browse/FINERACT-1897 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.7.0 >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > > When a user creates a new share account they get an internal server error at > submission of the share creation > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1897) Creating a Share Account - Internal server error
Francis Guchie created FINERACT-1897: Summary: Creating a Share Account - Internal server error Key: FINERACT-1897 URL: https://issues.apache.org/jira/browse/FINERACT-1897 Project: Apache Fineract Issue Type: Bug Components: Shares Affects Versions: 1.7.0 Reporter: Francis Guchie When a user creates a new share account they get an internal server error at submission of the share creation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1879) Loan Credit Committee Aproval Steps
[ https://issues.apache.org/jira/browse/FINERACT-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683910#comment-17683910 ] Francis Guchie commented on FINERACT-1879: -- [~bgowda] , Thank you for the response I or [~ikimbrah] will provide a functional spec > Loan Credit Committee Aproval Steps > --- > > Key: FINERACT-1879 > URL: https://issues.apache.org/jira/browse/FINERACT-1879 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > > Loan processing cycle is categorized into 4 steps as opposed to 3 provided > currently > details > # application > # Approval at Branch Level > # Credit Committee Approval > # Disbursement > All these steps need have to be controlled by the Maker-Checker module. This > means we have to add another layer in between the current steps -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1879) Loan Credit Committee Aproval Steps
[ https://issues.apache.org/jira/browse/FINERACT-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1879: - Summary: Loan Credit Committee Aproval Steps (was: Loan Credit Committee Aproval) > Loan Credit Committee Aproval Steps > --- > > Key: FINERACT-1879 > URL: https://issues.apache.org/jira/browse/FINERACT-1879 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > > Loan processing cycle is categorized into 4 steps as opposed to 3 provided > currently > details > # application > # Approval at Branch Level > # Credit Committee Approval > # Disbursement > All these steps need have to be controlled by the Maker-Checker module. This > means we have to add another layer in between the current steps -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1879) Loan Credit Committee Aproval
[ https://issues.apache.org/jira/browse/FINERACT-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1879: Assignee: Rahul Pawar > Loan Credit Committee Aproval > - > > Key: FINERACT-1879 > URL: https://issues.apache.org/jira/browse/FINERACT-1879 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > > Loan processing cycle is categorized into 4 steps as opposed to 3 provided > currently > details > # application > # Approval at Branch Level > # Credit Committee Approval > # Disbursement > All these steps need have to be controlled by the Maker-Checker module. This > means we have to add another layer in between the current steps -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1879) Loan Credit Committee Aproval
[ https://issues.apache.org/jira/browse/FINERACT-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683537#comment-17683537 ] Francis Guchie commented on FINERACT-1879: -- [~eroemma] [~mkaitesi] [~ikimbrah] Please provide details > Loan Credit Committee Aproval > - > > Key: FINERACT-1879 > URL: https://issues.apache.org/jira/browse/FINERACT-1879 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > > Loan processing cycle is categorized into 4 steps as opposed to 3 provided > currently > details > # application > # Approval at Branch Level > # Credit Committee Approval > # Disbursement > All these steps need have to be controlled by the Maker-Checker module. This > means we have to add another layer in between the current steps -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1879) Loan Credit Committee Aproval
Francis Guchie created FINERACT-1879: Summary: Loan Credit Committee Aproval Key: FINERACT-1879 URL: https://issues.apache.org/jira/browse/FINERACT-1879 Project: Apache Fineract Issue Type: Improvement Reporter: Francis Guchie Loan processing cycle is categorized into 4 steps as opposed to 3 provided currently details # application # Approval at Branch Level # Credit Committee Approval # Disbursement All these steps need have to be controlled by the Maker-Checker module. This means we have to add another layer in between the current steps -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel=17681997#comment-17681997 ] Francis Guchie commented on FINERACT-769: - [~ikimbrah] let me request [~rrpawar] to work with me on this if that is ok with [~avidakovic] > 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 > > > 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] [Assigned] (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 ] Francis Guchie reassigned FINERACT-769: --- Assignee: Rahul Pawar > 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 > > > 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] [Assigned] (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 ] Francis Guchie reassigned FINERACT-657: --- Assignee: Rahul Pawar > 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.8.0 >Reporter: Santosh Math >Assignee: Rahul Pawar >Priority: Major > Labels: p2 > Fix For: 1.9.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] [Commented] (FINERACT-1749) Not able to add loan collateral
[ https://issues.apache.org/jira/browse/FINERACT-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17616372#comment-17616372 ] Francis Guchie commented on FINERACT-1749: -- [~ikimbrah] [~rrpawar] this issue has been solved already in this [FINERACT-1357|https://issues.apache.org/jira/browse/FINERACT-1357] & [PR 3398 |https://github.com/openMF/community-app/pull/3398] > Not able to add loan collateral > --- > > Key: FINERACT-1749 > URL: https://issues.apache.org/jira/browse/FINERACT-1749 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > Attachments: image-2022-09-18-17-42-52-963.png, > image-2022-09-18-17-43-51-893.png > > > At loan application, the user can add a loan collateral as per the screenshot > below, > !image-2022-09-18-17-43-51-893.png|width=557,height=111! > however, upon adding the collateral details, the system throws the error > below. > !image-2022-09-18-17-42-52-963.png|width=572,height=114! > > If the loan collateral is not added, the application is submitted > successfully. Our use case here is that except for group loans, all > individual loans must be secured. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (FINERACT-1749) Not able to add loan collateral
[ https://issues.apache.org/jira/browse/FINERACT-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie closed FINERACT-1749. Fix Version/s: 1.8 1.7 Resolution: Duplicate > Not able to add loan collateral > --- > > Key: FINERACT-1749 > URL: https://issues.apache.org/jira/browse/FINERACT-1749 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0, 1.8, 1.7 > > Attachments: image-2022-09-18-17-42-52-963.png, > image-2022-09-18-17-43-51-893.png > > > At loan application, the user can add a loan collateral as per the screenshot > below, > !image-2022-09-18-17-43-51-893.png|width=557,height=111! > however, upon adding the collateral details, the system throws the error > below. > !image-2022-09-18-17-42-52-963.png|width=572,height=114! > > If the loan collateral is not added, the application is submitted > successfully. Our use case here is that except for group loans, all > individual loans must be secured. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1750) User permissions not available
[ https://issues.apache.org/jira/browse/FINERACT-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1750: - Affects Version/s: 1.7 (was: 1.8.0) > User permissions not available > --- > > Key: FINERACT-1750 > URL: https://issues.apache.org/jira/browse/FINERACT-1750 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.7 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > Attachments: client summary-1.png, permissoin error-1.png > > > We setup users with different permissions. It has come to our attention that > some permissions are not available like the client summary. Others are > available but even when granted, the system does not allow users to access > that information. An example is the client summary and the credit bureau. > !client summary-1.png|width=831,height=378! > !permissoin error-1.png|width=838,height=341! > There is no permission for read credit bureau and client summary. The same > applies to the reports, even when a user is given the rights to view a > report, the system does not show any report unless you give the person the > report super user rights which should not be the case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1204) When creating Reports, one will notice a number of missing parameters
[ https://issues.apache.org/jira/browse/FINERACT-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1204: Assignee: Francis Guchie (was: Rahul Pawar) > When creating Reports, one will notice a number of missing parameters > - > > Key: FINERACT-1204 > URL: https://issues.apache.org/jira/browse/FINERACT-1204 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Critical > Labels: pull-request-available > Attachments: Extra Stretchy Parameters Explained.xlsx > > > During creation of reports (pentaho and table alike) I have noticed a number > of parameters that are needed. I have managed to identify 25 parameters that > users will find very useful. Please see the attached document, I have tried > to explain the use of these parameters to the best of my ability. Additions > and / corrections are welcome > If this can be back ported for older builds it will be nice as it only > affects the table stretchy_parameter and nothing else -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1627) Error message; Unknown data integrity issue on client page after data importation
[ https://issues.apache.org/jira/browse/FINERACT-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1627: Assignee: Francis Guchie > Error message; Unknown data integrity issue on client page after data > importation > - > > Key: FINERACT-1627 > URL: https://issues.apache.org/jira/browse/FINERACT-1627 > Project: Apache Fineract > Issue Type: Bug > Components: Client, Database >Affects Versions: 1.5.0, 1.6.0, 1.7.0 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Critical > Labels: error-handling, error_response > Attachments: image-2022-05-29-22-01-12-969.png, > image-2022-05-29-22-03-45-669.png > > > After a successful data importation using postman, there is an error message > that shows on the client profile screen. as shown in the screenshot below > !image-2022-05-29-22-01-12-969.png|width=544,height=232! > > This however does not stop any operations on the client screen. However, the > same message appears on the loan application and it does not allow loan > creation when I was testing with fineract 1.7. > At the closer look into the console, the message below is seen. > !image-2022-05-29-22-03-45-669.png|width=537,height=220! > [~francisguchie] [~rrpawar] and [~eroemma] have you seen this as well for all > databases that have been imported? even when the initial database was for > mifos itself. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1752) Undo Transfer transactions
[ https://issues.apache.org/jira/browse/FINERACT-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607830#comment-17607830 ] Francis Guchie commented on FINERACT-1752: -- [~bgowda] [~ikimbrah] [~eroemma] we forgot this all this while when looking at the items > Undo Transfer transactions > -- > > Key: FINERACT-1752 > URL: https://issues.apache.org/jira/browse/FINERACT-1752 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan, Savings >Affects Versions: 1.4.0, 1.5.0, 1.7.0, 1.8, 1.6, 1.2, 1.3 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-09-21-13-54-23-648.png, > image-2022-09-21-13-56-33-027.png, image-2022-09-21-14-01-57-321.png, > image-2022-09-21-14-15-07-083.png > > > A user can make a loan repayment from a savings account, using the transfer > transaction API. But this cannot be undone. > on the savings account transactions side the undo button is not seen > !image-2022-09-21-13-54-23-648.png|width=564,height=177! > on the loan transactions side the undo and edit are visible > !image-2022-09-21-13-56-33-027.png|width=522,height=171! > However, this does not depict the real details of this loan transaction > I would expect the following > 1- on the savings account transactions i expect the transaction to show the > transfer details and the Undo button - the Undo button should only allow the > undo if the this is a savings to savings transfer > !image-2022-09-21-14-01-57-321.png|width=559,height=244! > 2- on the loan account transactions i expect the transaction to show the > transfer details and the Undo button > !image-2022-09-21-14-15-07-083.png|width=562,height=114! > 3- the Undo button should all user to undo the transaction so that the loan > and the savings balances are restored to initial values before the transfer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1752) Undo Transfer transactions
[ https://issues.apache.org/jira/browse/FINERACT-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1752: - Affects Version/s: 1.8 1.6 1.2 1.3 1.7.0 1.5.0 1.4.0 > Undo Transfer transactions > -- > > Key: FINERACT-1752 > URL: https://issues.apache.org/jira/browse/FINERACT-1752 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan, Savings >Affects Versions: 1.4.0, 1.5.0, 1.7.0, 1.8, 1.6, 1.2, 1.3 >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-09-21-13-54-23-648.png, > image-2022-09-21-13-56-33-027.png, image-2022-09-21-14-01-57-321.png, > image-2022-09-21-14-15-07-083.png > > > A user can make a loan repayment from a savings account, using the transfer > transaction API. But this cannot be undone. > on the savings account transactions side the undo button is not seen > !image-2022-09-21-13-54-23-648.png|width=564,height=177! > on the loan transactions side the undo and edit are visible > !image-2022-09-21-13-56-33-027.png|width=522,height=171! > However, this does not depict the real details of this loan transaction > I would expect the following > 1- on the savings account transactions i expect the transaction to show the > transfer details and the Undo button - the Undo button should only allow the > undo if the this is a savings to savings transfer > !image-2022-09-21-14-01-57-321.png|width=559,height=244! > 2- on the loan account transactions i expect the transaction to show the > transfer details and the Undo button > !image-2022-09-21-14-15-07-083.png|width=562,height=114! > 3- the Undo button should all user to undo the transaction so that the loan > and the savings balances are restored to initial values before the transfer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1752) Undo Transfer transactions
[ https://issues.apache.org/jira/browse/FINERACT-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1752: Assignee: Francis Guchie > Undo Transfer transactions > -- > > Key: FINERACT-1752 > URL: https://issues.apache.org/jira/browse/FINERACT-1752 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan, Savings >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-09-21-13-54-23-648.png, > image-2022-09-21-13-56-33-027.png, image-2022-09-21-14-01-57-321.png, > image-2022-09-21-14-15-07-083.png > > > A user can make a loan repayment from a savings account, using the transfer > transaction API. But this cannot be undone. > on the savings account transactions side the undo button is not seen > !image-2022-09-21-13-54-23-648.png|width=564,height=177! > on the loan transactions side the undo and edit are visible > !image-2022-09-21-13-56-33-027.png|width=522,height=171! > However, this does not depict the real details of this loan transaction > I would expect the following > 1- on the savings account transactions i expect the transaction to show the > transfer details and the Undo button - the Undo button should only allow the > undo if the this is a savings to savings transfer > !image-2022-09-21-14-01-57-321.png|width=559,height=244! > 2- on the loan account transactions i expect the transaction to show the > transfer details and the Undo button > !image-2022-09-21-14-15-07-083.png|width=562,height=114! > 3- the Undo button should all user to undo the transaction so that the loan > and the savings balances are restored to initial values before the transfer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (FINERACT-1752) Undo Transfer transactions
Francis Guchie created FINERACT-1752: Summary: Undo Transfer transactions Key: FINERACT-1752 URL: https://issues.apache.org/jira/browse/FINERACT-1752 Project: Apache Fineract Issue Type: New Feature Components: Loan, Savings Reporter: Francis Guchie Attachments: image-2022-09-21-13-54-23-648.png, image-2022-09-21-13-56-33-027.png, image-2022-09-21-14-01-57-321.png, image-2022-09-21-14-15-07-083.png A user can make a loan repayment from a savings account, using the transfer transaction API. But this cannot be undone. on the savings account transactions side the undo button is not seen !image-2022-09-21-13-54-23-648.png|width=564,height=177! on the loan transactions side the undo and edit are visible !image-2022-09-21-13-56-33-027.png|width=522,height=171! However, this does not depict the real details of this loan transaction I would expect the following 1- on the savings account transactions i expect the transaction to show the transfer details and the Undo button - the Undo button should only allow the undo if the this is a savings to savings transfer !image-2022-09-21-14-01-57-321.png|width=559,height=244! 2- on the loan account transactions i expect the transaction to show the transfer details and the Undo button !image-2022-09-21-14-15-07-083.png|width=562,height=114! 3- the Undo button should all user to undo the transaction so that the loan and the savings balances are restored to initial values before the transfer -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606716#comment-17606716
]
Francis Guchie commented on FINERACT-1653:
--
For Ubuntu users
please create the file or make sure you give it the correct users rights
otherwise Apache-fineract will not boot
[~ikimbrah] this was the issue to day
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FINERACT-1750) User permissions not available
[ https://issues.apache.org/jira/browse/FINERACT-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1750: Assignee: Francis Guchie > User permissions not available > --- > > Key: FINERACT-1750 > URL: https://issues.apache.org/jira/browse/FINERACT-1750 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.8.0 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > Attachments: client summary-1.png, permissoin error-1.png > > > We setup users with different permissions. It has come to our attention that > some permissions are not available like the client summary. Others are > available but even when granted, the system does not allow users to access > that information. An example is the client summary and the credit bureau. > !client summary-1.png|width=831,height=378! > !permissoin error-1.png|width=838,height=341! > There is no permission for read credit bureau and client summary. The same > applies to the reports, even when a user is given the rights to view a > report, the system does not show any report unless you give the person the > report super user rights which should not be the case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1749) Not able to add loan collateral
[ https://issues.apache.org/jira/browse/FINERACT-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1749: Assignee: Francis Guchie > Not able to add loan collateral > --- > > Key: FINERACT-1749 > URL: https://issues.apache.org/jira/browse/FINERACT-1749 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: ibrahim kimbugwe >Assignee: Francis Guchie >Priority: Major > Fix For: 1.9.0 > > Attachments: image-2022-09-18-17-42-52-963.png, > image-2022-09-18-17-43-51-893.png > > > At loan application, the user can add a loan collateral as per the screenshot > below, > !image-2022-09-18-17-43-51-893.png|width=557,height=111! > however, upon adding the collateral details, the system throws the error > below. > !image-2022-09-18-17-42-52-963.png|width=572,height=114! > > If the loan collateral is not added, the application is submitted > successfully. Our use case here is that except for group loans, all > individual loans must be secured. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1749) Not able to add loan collateral
[ https://issues.apache.org/jira/browse/FINERACT-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606487#comment-17606487 ] Francis Guchie commented on FINERACT-1749: -- [~ikimbrah] I think you are using version 1.7.0 are you sure this is the same in version 1.8.0 too? > Not able to add loan collateral > --- > > Key: FINERACT-1749 > URL: https://issues.apache.org/jira/browse/FINERACT-1749 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.8.0 >Reporter: ibrahim kimbugwe >Priority: Major > Fix For: 1.9.0 > > Attachments: image-2022-09-18-17-42-52-963.png, > image-2022-09-18-17-43-51-893.png > > > At loan application, the user can add a loan collateral as per the screenshot > below, > !image-2022-09-18-17-43-51-893.png|width=557,height=111! > however, upon adding the collateral details, the system throws the error > below. > !image-2022-09-18-17-42-52-963.png|width=572,height=114! > > If the loan collateral is not added, the application is submitted > successfully. Our use case here is that except for group loans, all > individual loans must be secured. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1750) User permissions not available
[ https://issues.apache.org/jira/browse/FINERACT-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606486#comment-17606486 ] Francis Guchie commented on FINERACT-1750: -- [~ikimbrah] i think you are using version 1.7 and not 1.8 kindly edit this > User permissions not available > --- > > Key: FINERACT-1750 > URL: https://issues.apache.org/jira/browse/FINERACT-1750 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.8.0 >Reporter: ibrahim kimbugwe >Priority: Major > Fix For: 1.9.0 > > Attachments: client summary-1.png, permissoin error-1.png > > > We setup users with different permissions. It has come to our attention that > some permissions are not available like the client summary. Others are > available but even when granted, the system does not allow users to access > that information. An example is the client summary and the credit bureau. > !client summary-1.png|width=831,height=378! > !permissoin error-1.png|width=838,height=341! > There is no permission for read credit bureau and client summary. The same > applies to the reports, even when a user is given the rights to view a > report, the system does not show any report unless you give the person the > report super user rights which should not be the case. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602016#comment-17602016
]
Francis Guchie commented on FINERACT-1653:
--
[~aleks]
I do confirm that this is working perfectly - in a setup i have used none
default credentials and a database server separated from UI server
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FINERACT-1639) Apply penal interest For Pre-mature Closure (as a Charge)
[ https://issues.apache.org/jira/browse/FINERACT-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1639: Assignee: Francis Guchie (was: Rahul Pawar) > Apply penal interest For Pre-mature Closure (as a Charge) > - > > Key: FINERACT-1639 > URL: https://issues.apache.org/jira/browse/FINERACT-1639 > Project: Apache Fineract > Issue Type: Bug >Reporter: Francis Guchie >Assignee: Francis Guchie >Priority: Major > Attachments: image-2022-06-13-10-04-34-964.png, > image-2022-08-24-17-55-57-998.png, image-2022-08-24-17-57-38-718.png, > image-2022-08-24-18-12-49-604.png, image-2022-08-29-18-42-20-723.png > > > [~ikimbrah] [~mkaitesi] [~eroemma] [~kigred.developer] > After considerations of FINERACT-1567 , we me and [~rrpawar] have concluded > that we shall add this in as a charge under system ==> Products ==> Charges > see imitation below > !image-2022-06-13-10-04-34-964.png|width=436,height=217! > > The charge-time-type will be tagged "premature closure of FD or RD" > shortly i will update this issue with better images -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francis Guchie resolved FINERACT-1653.
--
Resolution: Not A Problem
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.6.0, 1.5.0, 1.4.0, 1.3.0, 1.2.0, 1.1.0, 1.0.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598558#comment-17598558
]
Francis Guchie edited comment on FINERACT-1653 at 8/31/22 6:39 PM:
---
[~aleks] Yes i agree now i agree with you. I will close this issue as
resolved. Then will implement according to documentation
was (Author: francisguchie):
[~aleks] Yes i agree with you it is not a security threat for other versions
1.5 and below
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598558#comment-17598558
]
Francis Guchie commented on FINERACT-1653:
--
[~aleks] Yes i agree with you it is not a security threat for other versions
1.5 and below
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598322#comment-17598322
]
Francis Guchie commented on FINERACT-1653:
--
[~arnold]
I am doing deployments using tomcat - (war and ROOT folders )
where would someone put the env file ?? Kindly point me to it and i will write
out something for all tomcat users to use during deployment.
I am a bit hesitant to use docker in live production may be you can give me
your professional advise on Docker usage for a databases that group up to about
5gb in size
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598303#comment-17598303
]
Francis Guchie edited comment on FINERACT-1653 at 8/31/22 10:17 AM:
[~arnold]
I have not used any env Variables - kindly advise on how to go about this - I
think i missed something, env rings a bell but i have not used any in 1.7.0
and am yet to test 1.8.0 (was thinking of going straight for 1.8.0)
please note that these are 2 issues in one
1- I want to have the db in a different place (RDBMS)
2- I want to have the default credentials changed to my liking
was (Author: francisguchie):
[~arnold]
I have not used any env Variables - kindly advise on how to go about this - I
think i missed something, env rings a bell but i have not used any in 1.7.0
and am yet to test 1.8.0 (was thinking of going straight for 1.8.0)
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598303#comment-17598303
]
Francis Guchie commented on FINERACT-1653:
--
[~arnold]
I have not used any env Variables - kindly advise on how to go about this - I
think i missed something, env rings a bell but i have not used any in 1.7.0
and am yet to test 1.8.0 (was thinking of going straight for 1.8.0)
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francis Guchie updated FINERACT-1653:
-
Issue Type: Bug (was: Improvement)
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1653) Security Threat Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francis Guchie updated FINERACT-1653:
-
Summary: Security Threat Cannot boot Apache Fineract if database is not on
local host and password is not the default (was: Cannot boot Apache Fineract
if database is not on local host and password is not the default)
> Security Threat Cannot boot Apache Fineract if database is not on local host
> and password is not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Improvement
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FINERACT-1653) Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17598280#comment-17598280
]
Francis Guchie commented on FINERACT-1653:
--
[~avidakovic] [~ikimbrah] [~eroemma] [~mkaitesi]
This issue is causing a serious problem, because globally mysql / mariadb
databases can easily be hacked if passwords are set so simple
> Cannot boot Apache Fineract if database is not on local host and password is
> not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Improvement
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (FINERACT-1653) Cannot boot Apache Fineract if database is not on local host and password is not the default
[
https://issues.apache.org/jira/browse/FINERACT-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francis Guchie reassigned FINERACT-1653:
Assignee: Francis Guchie
> Cannot boot Apache Fineract if database is not on local host and password is
> not the default
>
>
> Key: FINERACT-1653
> URL: https://issues.apache.org/jira/browse/FINERACT-1653
> Project: Apache Fineract
> Issue Type: Improvement
>Affects Versions: 1.7.0
>Reporter: Francis Guchie
>Assignee: Francis Guchie
>Priority: Major
> Fix For: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0
>
>
> As a user, i would like to setup apache fineract in a live production where
> the database server is separate from the ui server with a different root
> password from usual.
> In the latest release, 1.7.0, there is a pre-compiled jar by the names of
> fineract-provider-1.5.1-0d5bace3-plain.jar which is used during boot up of
> Apache-Fineract.
> As such, the user gets an error shown below ( amongst others )
> Error creating bean with name '(inner bean)#10ee8a73':
> Cannot resolve reference to bean 'entityManagerFactory' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'tenantDatabaseUpgradeService' defined in URL
> [jar:file:{*}/usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar{*}!
> /org/apache/fineract/infrastructure/core/service/migration/TenantDatabaseUpgradeService.class]:
> Unsatisfied dependency expressed through constructor parameter 0;
> nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'jdbcTenantDetailsService'
> defined in URL
> [jar:file:/{*}usr/share/tomcat9/webapps/fineract-provider/WEB-INF/lib/fineract-provider-1.5.1-0d5bace3-plain.jar!{*}
> this means users will not be able to deploy Mifos without using the default
> root password and if they have the database and ui on different servers.
> IN release 1.6.0, tomcat deployment users had the opportunity to edit the
> following files after a first boot up when the war file is deployed (
> *..webapps/fineract-provider/WEB-INF/classes/META-INF/spring/jdbc.properties*
> *.webapps/fineract-provider/WEB-INF/classes/META-INF/spring/hikariDataSource.xml*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FINERACT-1639) Apply penal interest For Pre-mature Closure (as a Charge)
[ https://issues.apache.org/jira/browse/FINERACT-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1639: - Attachment: image-2022-08-29-18-42-20-723.png > Apply penal interest For Pre-mature Closure (as a Charge) > - > > Key: FINERACT-1639 > URL: https://issues.apache.org/jira/browse/FINERACT-1639 > Project: Apache Fineract > Issue Type: Bug >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > Attachments: image-2022-06-13-10-04-34-964.png, > image-2022-08-24-17-55-57-998.png, image-2022-08-24-17-57-38-718.png, > image-2022-08-24-18-12-49-604.png, image-2022-08-29-18-42-20-723.png > > > [~ikimbrah] [~mkaitesi] [~eroemma] [~kigred.developer] > After considerations of FINERACT-1567 , we me and [~rrpawar] have concluded > that we shall add this in as a charge under system ==> Products ==> Charges > see imitation below > !image-2022-06-13-10-04-34-964.png|width=436,height=217! > > The charge-time-type will be tagged "premature closure of FD or RD" > shortly i will update this issue with better images -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1639) Apply penal interest For Pre-mature Closure (as a Charge)
[ https://issues.apache.org/jira/browse/FINERACT-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1639: - Attachment: image-2022-08-24-18-12-49-604.png > Apply penal interest For Pre-mature Closure (as a Charge) > - > > Key: FINERACT-1639 > URL: https://issues.apache.org/jira/browse/FINERACT-1639 > Project: Apache Fineract > Issue Type: Bug >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > Attachments: image-2022-06-13-10-04-34-964.png, > image-2022-08-24-17-55-57-998.png, image-2022-08-24-17-57-38-718.png, > image-2022-08-24-18-12-49-604.png > > > [~ikimbrah] [~mkaitesi] [~eroemma] [~kigred.developer] > After considerations of FINERACT-1567 , we me and [~rrpawar] have concluded > that we shall add this in as a charge under system ==> Products ==> Charges > see imitation below > !image-2022-06-13-10-04-34-964.png|width=436,height=217! > > The charge-time-type will be tagged "premature closure of FD or RD" > shortly i will update this issue with better images -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1639) Apply penal interest For Pre-mature Closure (as a Charge)
[ https://issues.apache.org/jira/browse/FINERACT-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584413#comment-17584413 ] Francis Guchie commented on FINERACT-1639: -- [~rrpawar] [~mkaitesi] [~ikimbrah] *Take note of the following issues about premature closure of the re-current account* Once a user selects transfer to savings, (NOT Direct Withdrawal) the the payment Type and Show Payment details are not needed. See image below !image-2022-08-24-18-12-49-604.png! > Apply penal interest For Pre-mature Closure (as a Charge) > - > > Key: FINERACT-1639 > URL: https://issues.apache.org/jira/browse/FINERACT-1639 > Project: Apache Fineract > Issue Type: Bug >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > Attachments: image-2022-06-13-10-04-34-964.png, > image-2022-08-24-17-55-57-998.png, image-2022-08-24-17-57-38-718.png, > image-2022-08-24-18-12-49-604.png > > > [~ikimbrah] [~mkaitesi] [~eroemma] [~kigred.developer] > After considerations of FINERACT-1567 , we me and [~rrpawar] have concluded > that we shall add this in as a charge under system ==> Products ==> Charges > see imitation below > !image-2022-06-13-10-04-34-964.png|width=436,height=217! > > The charge-time-type will be tagged "premature closure of FD or RD" > shortly i will update this issue with better images -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1639) Apply penal interest For Pre-mature Closure (as a Charge)
[ https://issues.apache.org/jira/browse/FINERACT-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584405#comment-17584405 ] Francis Guchie commented on FINERACT-1639: -- [~rrpawar] [~mkaitesi] [~ikimbrah] *Take note of the following issues about premature closure of the account* 1- User should NOT be allowed to put a date higher than the maturity date of the Recurring deposit. On the UI, I see that the user has options to date-pick any date *(in cases where users have a back log)* and some days have passed before they did the postings. See image below !image-2022-08-24-17-55-57-998.png|width=603,height=614! See below - fineract has updated the maturity date and accepted the transaction on 24 Aug 2022 !image-2022-08-24-17-57-38-718.png|width=633,height=603! > Apply penal interest For Pre-mature Closure (as a Charge) > - > > Key: FINERACT-1639 > URL: https://issues.apache.org/jira/browse/FINERACT-1639 > Project: Apache Fineract > Issue Type: Bug >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > Attachments: image-2022-06-13-10-04-34-964.png, > image-2022-08-24-17-55-57-998.png, image-2022-08-24-17-57-38-718.png > > > [~ikimbrah] [~mkaitesi] [~eroemma] [~kigred.developer] > After considerations of FINERACT-1567 , we me and [~rrpawar] have concluded > that we shall add this in as a charge under system ==> Products ==> Charges > see imitation below > !image-2022-06-13-10-04-34-964.png|width=436,height=217! > > The charge-time-type will be tagged "premature closure of FD or RD" > shortly i will update this issue with better images -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1639) Apply penal interest For Pre-mature Closure (as a Charge)
[ https://issues.apache.org/jira/browse/FINERACT-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1639: - Attachment: image-2022-08-24-17-57-38-718.png > Apply penal interest For Pre-mature Closure (as a Charge) > - > > Key: FINERACT-1639 > URL: https://issues.apache.org/jira/browse/FINERACT-1639 > Project: Apache Fineract > Issue Type: Bug >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > Attachments: image-2022-06-13-10-04-34-964.png, > image-2022-08-24-17-55-57-998.png, image-2022-08-24-17-57-38-718.png > > > [~ikimbrah] [~mkaitesi] [~eroemma] [~kigred.developer] > After considerations of FINERACT-1567 , we me and [~rrpawar] have concluded > that we shall add this in as a charge under system ==> Products ==> Charges > see imitation below > !image-2022-06-13-10-04-34-964.png|width=436,height=217! > > The charge-time-type will be tagged "premature closure of FD or RD" > shortly i will update this issue with better images -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FINERACT-1639) Apply penal interest For Pre-mature Closure (as a Charge)
[ https://issues.apache.org/jira/browse/FINERACT-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie updated FINERACT-1639: - Attachment: image-2022-08-24-17-55-57-998.png > Apply penal interest For Pre-mature Closure (as a Charge) > - > > Key: FINERACT-1639 > URL: https://issues.apache.org/jira/browse/FINERACT-1639 > Project: Apache Fineract > Issue Type: Bug >Reporter: Francis Guchie >Assignee: Rahul Pawar >Priority: Major > Attachments: image-2022-06-13-10-04-34-964.png, > image-2022-08-24-17-55-57-998.png > > > [~ikimbrah] [~mkaitesi] [~eroemma] [~kigred.developer] > After considerations of FINERACT-1567 , we me and [~rrpawar] have concluded > that we shall add this in as a charge under system ==> Products ==> Charges > see imitation below > !image-2022-06-13-10-04-34-964.png|width=436,height=217! > > The charge-time-type will be tagged "premature closure of FD or RD" > shortly i will update this issue with better images -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1485) New Loan Charge type "upfront disbursement fees"
[ https://issues.apache.org/jira/browse/FINERACT-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583749#comment-17583749 ] Francis Guchie commented on FINERACT-1485: -- [~bgowda] Now i get you clearly on this part *"Currently, loan is getting disbursed at $1000 only + the fee of $10 is getting collected"* Is it ok if [~rrpawar] does the PR with support from me & [~ikimbrah] > New Loan Charge type "upfront disbursement fees" > > > Key: FINERACT-1485 > URL: https://issues.apache.org/jira/browse/FINERACT-1485 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Affects Versions: 1.8.0 >Reporter: bharath gowda >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.9.0 > > Attachments: Upfront fee requirement.xlsx, screenshot-1.png > > > Refer Attachment for full details of the requirement. > |Requirement|Changes | > |New loan entity - fee type to be introduced |Upfront Disbursement Fee| > | > Upfront fee can be on |1. % approved amount > 2. Flat| > |Actual Disbursement Amount =|Disbursement amount entered - upfront fees > amount| > |Repayment schedule|Repayment schedule should be calculated based on the > actual disbursement amount(Disbursement amount entered - upfront fees)| > |Transaction|Upfront fees should be collected at the time of disbursement(as > shown in the transaction sample)| > |Accounting entry|no changes in accounting entries. it remains standard OOB > for disbursement, fees, and transactions| > |Repayment schedule calculation |once disbursed with the actual > disbursement amount- all calculation remains the same as OOB as per > product configuration| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FINERACT-1485) New Loan Charge type "upfront disbursement fees"
[ https://issues.apache.org/jira/browse/FINERACT-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583744#comment-17583744 ] Francis Guchie commented on FINERACT-1485: -- [~bgowda] Have you added the documentation? [~ikimbrah] do you have a comment > New Loan Charge type "upfront disbursement fees" > > > Key: FINERACT-1485 > URL: https://issues.apache.org/jira/browse/FINERACT-1485 > Project: Apache Fineract > Issue Type: Improvement > Components: Charges, Loan >Affects Versions: 1.8.0 >Reporter: bharath gowda >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.9.0 > > Attachments: Upfront fee requirement.xlsx, screenshot-1.png > > > Refer Attachment for full details of the requirement. > |Requirement|Changes | > |New loan entity - fee type to be introduced |Upfront Disbursement Fee| > | > Upfront fee can be on |1. % approved amount > 2. Flat| > |Actual Disbursement Amount =|Disbursement amount entered - upfront fees > amount| > |Repayment schedule|Repayment schedule should be calculated based on the > actual disbursement amount(Disbursement amount entered - upfront fees)| > |Transaction|Upfront fees should be collected at the time of disbursement(as > shown in the transaction sample)| > |Accounting entry|no changes in accounting entries. it remains standard OOB > for disbursement, fees, and transactions| > |Repayment schedule calculation |once disbursed with the actual > disbursement amount- all calculation remains the same as OOB as per > product configuration| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (FINERACT-1560) Enhance Retrieve loan information by Client ID API for new required response parameters
[ https://issues.apache.org/jira/browse/FINERACT-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Guchie reassigned FINERACT-1560: Assignee: Rahul Pawar > Enhance Retrieve loan information by Client ID API for new required response > parameters > --- > > Key: FINERACT-1560 > URL: https://issues.apache.org/jira/browse/FINERACT-1560 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.6.0 >Reporter: Ed Cable >Assignee: Rahul Pawar >Priority: Major > Fix For: 1.9.0 > > > For retrieving the loan information for a client, we need to enhance the > following API with additonal parameters outlined below. > +GET:+ > _https://DomainName/api/v1/loans/template?templateType=individual=1=1_ > > |New Parameter|Value/Amount| > |available_disbursement_amount|It is the difference of approved amount and > disbursed amount| > |past_due_days|No of days the loan is overdue,current date - duedate| > |next_payment_due_date|Based on the current date, need to populate the next > payment due date| > |delinquent_days|No of days the loan is in arrears, current date - > duedate-grace period| > |delinquent_date|Date the loan is in arrears, current date - duedate-grace > period| > |delinquent_amount|amount overdue after the grace period| > |last_payment_date|last repayment made date on the loan| > |last_payment_amount|last repayment amount made date on the loan| > -- This message was sent by Atlassian Jira (v8.20.10#820010)
