[jira] [Commented] (FINERACT-1424) Make collateral feature optional for multi disbursement
[ https://issues.apache.org/jira/browse/FINERACT-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17436614#comment-17436614 ] Benura Abeywardena commented on FINERACT-1424: -- [~bharathc27] Please add details if missing > Make collateral feature optional for multi disbursement > --- > > Key: FINERACT-1424 > URL: https://issues.apache.org/jira/browse/FINERACT-1424 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.6.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.5.0 > > > Loan collateral should be optional when creating a loan. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1424) Make collateral feature optional for multi disbursement
Benura Abeywardena created FINERACT-1424: Summary: Make collateral feature optional for multi disbursement Key: FINERACT-1424 URL: https://issues.apache.org/jira/browse/FINERACT-1424 Project: Apache Fineract Issue Type: Bug Components: Loan Affects Versions: 1.6.0 Reporter: Benura Abeywardena Assignee: Benura Abeywardena Fix For: 1.5.0 Loan collateral should be optional when creating a loan. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1417) Introduce a new pivot date to filter the savings transactions.
[ https://issues.apache.org/jira/browse/FINERACT-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434321#comment-17434321 ] Benura Abeywardena commented on FINERACT-1417: -- [~avikganguly010] Please add changes if there's any > Introduce a new pivot date to filter the savings transactions. > -- > > Key: FINERACT-1417 > URL: https://issues.apache.org/jira/browse/FINERACT-1417 > Project: Apache Fineract > Issue Type: New Feature > Components: Savings >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.6.0 > > > Current fineract code base use multiple for loops to calculate the > transaction related data on a savings transaction. This adds an unnecessary > latency to a transaction request. By introducing a pivot date, this number of > iterations can be reduced with the help of savings account summary available. > However, in this scenario back dated transactions will not be allowed. Since, > there can be scenarios where back dated transactions are needed, a global > configuration is introduced to prevent breaking the existing use cases > completely. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1417) Introduce a new pivot date to filter the savings transactions.
Benura Abeywardena created FINERACT-1417: Summary: Introduce a new pivot date to filter the savings transactions. Key: FINERACT-1417 URL: https://issues.apache.org/jira/browse/FINERACT-1417 Project: Apache Fineract Issue Type: New Feature Components: Savings Reporter: Benura Abeywardena Assignee: Benura Abeywardena Fix For: 1.6.0 Current fineract code base use multiple for loops to calculate the transaction related data on a savings transaction. This adds an unnecessary latency to a transaction request. By introducing a pivot date, this number of iterations can be reduced with the help of savings account summary available. However, in this scenario back dated transactions will not be allowed. Since, there can be scenarios where back dated transactions are needed, a global configuration is introduced to prevent breaking the existing use cases completely. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-429) Node aware Scheduler
[
https://issues.apache.org/jira/browse/FINERACT-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benura Abeywardena reassigned FINERACT-429:
---
Assignee: Benura Abeywardena
> Node aware Scheduler
>
>
> Key: FINERACT-429
> URL: https://issues.apache.org/jira/browse/FINERACT-429
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Avik Ganguly
>Assignee: Benura Abeywardena
>Priority: Major
> Labels: gsoc, p2
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I believe multiple instances of the same job can be created by keeping the
> same job identifier but having different job keys. Additional parameter
> nodeId can be saved in the job table defaulting to 1. Default this parameter
> for a single-instance app-server to 1.
> If node.id parameter exists in the application yaml while deploying, set that
> system property to configured node id.
> Front-end can pass the configured node-id of the job instance as a query
> parameter.
> This will allow the organization to configure something like let Node 1 do
> all accruals for North zonal office and Node 2 do all accruals for South
> Zonal office.
> System admin can setup the corresponding mapping for node to IPs/URL while
> configuring load balancer. Example :-
> ```
> //Nginx - Default Round Robin Configuration
> http {
> upstream myapp1 {
> server srv1.example.com;
> server srv2.example.com;
> server srv3.example.com;
> }
>map $query_string $srvr {
> default https://myapp1 // If it doesn't match, send to load
> balancer
> node=1 srv1.example.com;
> node=2 srv2.example.com;
> node=3 srv3.example.com;
>}
> server {
> listen 80;
> location / {
> proxy_pass $srvr;
> }
> }
> }
> ```
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1405) Loan Collateral should be Optional while creating loan account
[ https://issues.apache.org/jira/browse/FINERACT-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426251#comment-17426251 ] Benura Abeywardena commented on FINERACT-1405: -- [~fynmanoj] Hi Manoj ! This needs to be discussed with [~bgowda]. Key idea was to allow collateral to be managed more effectively. > Loan Collateral should be Optional while creating loan account > -- > > Key: FINERACT-1405 > URL: https://issues.apache.org/jira/browse/FINERACT-1405 > Project: Apache Fineract > Issue Type: Bug >Reporter: Manoj Mohanan >Assignee: Manoj Mohanan >Priority: Minor > > Since there is no configuration option to switch on switch off collateral > from loan product, loan collateral should be non manadatory at loan account > creation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1389) Must issue a STARTTLS command first - Send Password to Email
[
https://issues.apache.org/jira/browse/FINERACT-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402471#comment-17402471
]
Benura Abeywardena commented on FINERACT-1389:
--
Hi [~francisguchie], didn't we sort out this problem? Yuh, the port might be
the problem. Will take a look :)
> Must issue a STARTTLS command first - Send Password to Email
>
>
> Key: FINERACT-1389
> URL: https://issues.apache.org/jira/browse/FINERACT-1389
> Project: Apache Fineract
> Issue Type: Bug
> Components: User Management
>Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0
>Reporter: Francis Guchie
>Assignee: Benura Abeywardena
>Priority: Major
> Attachments: image-2021-08-20-23-38-44-951.png
>
>
> When I try to send password to email i get the following error
> {
> "developerMessage": "The request was invalid. This typically will happen due
> to validation errors which are provided.",
> "httpStatusCode": "400",
> "defaultUserMessage": "Validation errors exist.",
> "userMessageGlobalisationCode": "validation.msg.validation.errors.exist",
> "errors": [
> {
> "developerMessage": "Sending email failed; is parameter email is invalid?
> More details available in server log:
> org.springframework.mail.MailSendException: Failed messages:
> com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a STARTTLS
> command first. l15sm4064471ilo.22 - gsmtp\n; message exceptions (1)
> are:\nFailed message 1: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0
> Must issue a STARTTLS command first. l15sm4064471ilo.22 - gsmtp\n",
> "defaultUserMessage": "Sending email failed; is parameter email is invalid?
> More details available in server log:
> org.springframework.mail.MailSendException: Failed messages:
> com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a STARTTLS
> command first. l15sm4064471ilo.22 - gsmtp\n; message exceptions (1)
> are:\nFailed message 1: com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0
> Must issue a STARTTLS command first. l15sm4064471ilo.22 - gsmtp\n",
> "userMessageGlobalisationCode": "error.msg.user.email.invalid",
> "parameterName": "email",
> "value": null,
> "args": [
> {
> "value": "francisguc...@gmail.com"
> }
> ]
> }
> !image-2021-08-20-23-38-44-951.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1289) Tax component not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399104#comment-17399104 ] Benura Abeywardena edited comment on FINERACT-1289 at 8/14/21, 5:55 AM: [~bgowda] This issue is not fixed. I'll not be having enough time in these days to fix this issue. Someone else could work on this issue. I think [~rishabh-99] has already opened a thread regarding this issue on dev fineract. Would you mind taking a look regarding his query ? [~bgowda] was (Author: blasan): [~bgowda] This issue is not fixed. I'll not be having enough time in these days to fix this issue. Someone else could work on this issue. I think [~rishabh-99] has already opened a thread regarding this issue on dev fineract. Would you mind taking a look ? [~bgowda] > Tax component not working as expected > - > > Key: FINERACT-1289 > URL: https://issues.apache.org/jira/browse/FINERACT-1289 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges >Affects Versions: 1.4.0 >Reporter: bharath gowda >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.6.0 > > Attachments: loan charge config.png, loan charge split not > happening.png, loan product config -1.png, loan product config -2.png, tax > component config.jpeg, tax group config.png > > > tax attached to the loan charge is not getting affected at the > loan/accounting level > To reproduce > 1. Create a tax component-> create a tax group with the component created. > 2. Create loan charge(any parameter, refer to the attachment for the > parameters I used) and map the tax group created. > 3. Add the charge to the loan product (with periodic accrual accounting) > enabled > 4. create/approve/disburse a loan from that loan product. > 5. Ideally the charge with the tax attached should have JE splits for charge > amount and tax amount separated. > But the tax bifurcation is not happening > > Have attached > product config screenshot, charge config screenshot, tax config screenshot, > and loan issue screenshot for more understanding > Please add a comment if you need any help > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1289) Tax component not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399104#comment-17399104 ] Benura Abeywardena commented on FINERACT-1289: -- [~bgowda] This issue is not fixed. I'll not be having enough time in these days to fix this issue. Someone else could work on this issue. I think [~rishabh-99] has already opened a thread regarding this issue on dev fineract. Would you mind taking a look ? [~bgowda] > Tax component not working as expected > - > > Key: FINERACT-1289 > URL: https://issues.apache.org/jira/browse/FINERACT-1289 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges >Affects Versions: 1.4.0 >Reporter: bharath gowda >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.6.0 > > Attachments: loan charge config.png, loan charge split not > happening.png, loan product config -1.png, loan product config -2.png, tax > component config.jpeg, tax group config.png > > > tax attached to the loan charge is not getting affected at the > loan/accounting level > To reproduce > 1. Create a tax component-> create a tax group with the component created. > 2. Create loan charge(any parameter, refer to the attachment for the > parameters I used) and map the tax group created. > 3. Add the charge to the loan product (with periodic accrual accounting) > enabled > 4. create/approve/disburse a loan from that loan product. > 5. Ideally the charge with the tax attached should have JE splits for charge > amount and tax amount separated. > But the tax bifurcation is not happening > > Have attached > product config screenshot, charge config screenshot, tax config screenshot, > and loan issue screenshot for more understanding > Please add a comment if you need any help > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-493) Repayment method by Post Dated Checks
[ https://issues.apache.org/jira/browse/FINERACT-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena updated FINERACT-493: Fix Version/s: 1.6.0 > Repayment method by Post Dated Checks > - > > Key: FINERACT-493 > URL: https://issues.apache.org/jira/browse/FINERACT-493 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Reporter: Justine Nam >Assignee: Benura Abeywardena >Priority: Major > Labels: feature, gsoc, p2 > Fix For: 1.6.0 > > > Repayment by Post Dated Checks > In Current updated MifosX, there is no convenient features for Post dated > checks Repayment. > Our company normally require Post Dated Checks to the client as repayment > method when their loan is approved. > If the term is 6 month, we asked them to provide 6 pcs Post Dated Checks for > repayment. > So, If it's possiblewhen we create the loan application for > individuals, make one more optional procedures to encode(input) the Post > Dated Checks details during Disburse Loan application > Normally, Check numbers are increased by 1... > example) > Name of BankDue Date Account No. Check No. Amount > Citi Bank 1/1/2017 230016 *11 1000 > Citi Bank 1/2/2017 230016*12 1000 > Citi Bank 1/3/2017 230016 *13 1000 > Citi Bank 1/4/2017 230016 *14 1000 > Citi Bank 1/5/2017 230016 *15 1000 > Citi Bank 1/6/2017230016*16 1000 > So, When we input the Postdated checks details. > 1. It should automatically generate the rows based on the term(get this data > from Loan application) > - if the term is 6 months, it should generate 6 rows for encoding of Checks > Info. > 2. For Check No. field, when we input first check No. , it should > automatically generate Check no. increased by 1 > 3. This data table is linked with Repayment Schedule. > When we see the repayment schedule , Check No. must be showed (If that data > is encoded) > 4. when we see the collection sheet, those information(like check no, bank > name) will automatically appear and can be edited as well...Also, It can be > cleared(make payment) in Collection Sheet > In current MifosX system, we need to encode one by one whenever there is > due-payment. > Collection Sheet -> Add payment detail -> input the Check detail. > If we have a few post dated checks, it's ok .But If there are many checks > to encode the datails for checks.this is time consuming works. > I hope someone work on this matter.. > thank you -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-493) Repayment method by Post Dated Checks
[ https://issues.apache.org/jira/browse/FINERACT-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reassigned FINERACT-493: --- Assignee: Benura Abeywardena > Repayment method by Post Dated Checks > - > > Key: FINERACT-493 > URL: https://issues.apache.org/jira/browse/FINERACT-493 > Project: Apache Fineract > Issue Type: New Feature > Components: Loan >Reporter: Justine Nam >Assignee: Benura Abeywardena >Priority: Major > Labels: feature, gsoc, p2 > > Repayment by Post Dated Checks > In Current updated MifosX, there is no convenient features for Post dated > checks Repayment. > Our company normally require Post Dated Checks to the client as repayment > method when their loan is approved. > If the term is 6 month, we asked them to provide 6 pcs Post Dated Checks for > repayment. > So, If it's possiblewhen we create the loan application for > individuals, make one more optional procedures to encode(input) the Post > Dated Checks details during Disburse Loan application > Normally, Check numbers are increased by 1... > example) > Name of BankDue Date Account No. Check No. Amount > Citi Bank 1/1/2017 230016 *11 1000 > Citi Bank 1/2/2017 230016*12 1000 > Citi Bank 1/3/2017 230016 *13 1000 > Citi Bank 1/4/2017 230016 *14 1000 > Citi Bank 1/5/2017 230016 *15 1000 > Citi Bank 1/6/2017230016*16 1000 > So, When we input the Postdated checks details. > 1. It should automatically generate the rows based on the term(get this data > from Loan application) > - if the term is 6 months, it should generate 6 rows for encoding of Checks > Info. > 2. For Check No. field, when we input first check No. , it should > automatically generate Check no. increased by 1 > 3. This data table is linked with Repayment Schedule. > When we see the repayment schedule , Check No. must be showed (If that data > is encoded) > 4. when we see the collection sheet, those information(like check no, bank > name) will automatically appear and can be edited as well...Also, It can be > cleared(make payment) in Collection Sheet > In current MifosX system, we need to encode one by one whenever there is > due-payment. > Collection Sheet -> Add payment detail -> input the Check detail. > If we have a few post dated checks, it's ok .But If there are many checks > to encode the datails for checks.this is time consuming works. > I hope someone work on this matter.. > thank you -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-592) Undo a charge waive
[ https://issues.apache.org/jira/browse/FINERACT-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena updated FINERACT-592: Fix Version/s: 1.6.0 Affects Version/s: 1.5.0 > Undo a charge waive > --- > > Key: FINERACT-592 > URL: https://issues.apache.org/jira/browse/FINERACT-592 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Affects Versions: 1.5.0 >Reporter: Jan Antonie Peens >Assignee: Benura Abeywardena >Priority: Minor > Labels: confirm, gsoc, p2 > Fix For: 1.6.0 > > Attachments: image-2021-04-06-20-06-08-917.png > > > Reverse a charge waiver. > We have gotten the situation were a charge was waived by accident and we > would therefore like to undo the mistake. > Would such a feature be possible? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-592) Undo a charge waive
[ https://issues.apache.org/jira/browse/FINERACT-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reassigned FINERACT-592: --- Assignee: Benura Abeywardena > Undo a charge waive > --- > > Key: FINERACT-592 > URL: https://issues.apache.org/jira/browse/FINERACT-592 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Jan Antonie Peens >Assignee: Benura Abeywardena >Priority: Minor > Labels: confirm, gsoc, p2 > Attachments: image-2021-04-06-20-06-08-917.png > > > Reverse a charge waiver. > We have gotten the situation were a charge was waived by accident and we > would therefore like to undo the mistake. > Would such a feature be possible? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-866) Improve Robustness of Mifos X and Apache Fineract by Fixing Issues/Feature Requests in Backlog
[ https://issues.apache.org/jira/browse/FINERACT-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reassigned FINERACT-866: --- Assignee: Benura Abeywardena > Improve Robustness of Mifos X and Apache Fineract by Fixing Issues/Feature > Requests in Backlog > -- > > Key: FINERACT-866 > URL: https://issues.apache.org/jira/browse/FINERACT-866 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Sanyam Goel >Assignee: Benura Abeywardena >Priority: Major > Labels: fineract, gsoc, gsoc2021, mentor > > |*Overview & Objectives* > Mifos X and Apache Fineract is widely used by financial institutions of all > different sizes and methodologies around the world. With that widespread user > base there is a vast array of different processes and procedures that would > like to be supported as slight modifications over the common functionality > provided. Over the past several years, we have captured these minor > enhancements in our issue tracker as feature requests. Also included in this > backlog or additional minor and less critical bugs that have been reported > but have not been fixed yet. This backlog has grown and it would be a very > impactful project for an intern to work on completing as many of these bug > fixes and minor enhancement as possible. > The difficult level of these issues ranges from low to higher and touch all > componets of the platform - most don't require too much domain knowledge but > some will. | > |*Description* > We have groomed the backlog and tagged issues and feature requests that are > relevant for this project with the labels gsoc and/or Volunteer. Priority > level of tasks is measured by p1 being the highest priority. Tasks with an > assigned fix version of either 1.4.0 or 1.5.0 have a higher priority. > There are more than 120 tickets in the saved filter. You are not expected to > complete all of the tasks in the backlog but throughout the internship you > should fix as many issues/feature requests as possible. You will work with > your mentor to deliver a plan for each sprint and adjust velocity as you get > scaled up. > Issues to be worked on can be found under the blocked issue list below| > |*Helpful Skills:* > *HTML, Spring, Hibernate, REST, Java, AngularJS, Javascript, SQL*| > |*Impact:* > Better internal control and financial transparency| > |*Other Resources:* > Getting Started with Apache Fineract: > [https://cwiki.apache.org/confluence/display/FINERACT/Getting+Started+Docs]| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1358) Client Level Collateral Management
[ https://issues.apache.org/jira/browse/FINERACT-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena updated FINERACT-1358: - Description: Client Level Collateral Management allows users to add, update, retrieve. > Client Level Collateral Management > -- > > Key: FINERACT-1358 > URL: https://issues.apache.org/jira/browse/FINERACT-1358 > Project: Apache Fineract > Issue Type: New Feature > Components: Client >Affects Versions: 1.5.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Major > > Client Level Collateral Management allows users to add, update, retrieve. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1360) Loan Level Collateral Management
Benura Abeywardena created FINERACT-1360: Summary: Loan Level Collateral Management Key: FINERACT-1360 URL: https://issues.apache.org/jira/browse/FINERACT-1360 Project: Apache Fineract Issue Type: New Feature Components: Loan Affects Versions: 1.5.0 Reporter: Benura Abeywardena Assignee: Benura Abeywardena Loan Level Collateral Management allows users to add, remove collateral from a loan. During the disbursement, it should check whether total collateral value is sufficient enough with respected to the principal loan amount. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1358) Client Level Collateral Management
Benura Abeywardena created FINERACT-1358: Summary: Client Level Collateral Management Key: FINERACT-1358 URL: https://issues.apache.org/jira/browse/FINERACT-1358 Project: Apache Fineract Issue Type: New Feature Components: Client Affects Versions: 1.5.0 Reporter: Benura Abeywardena Assignee: Benura Abeywardena -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1357) Collateral Management Module
[ https://issues.apache.org/jira/browse/FINERACT-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena updated FINERACT-1357: - Priority: Major (was: Blocker) > Collateral Management Module > > > Key: FINERACT-1357 > URL: https://issues.apache.org/jira/browse/FINERACT-1357 > Project: Apache Fineract > Issue Type: New Feature > Components: Client, Loan >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Major > > Collateral Management module allows to manage collateral details in product, > client & loan levels. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1357) Collateral Management Module
Benura Abeywardena created FINERACT-1357: Summary: Collateral Management Module Key: FINERACT-1357 URL: https://issues.apache.org/jira/browse/FINERACT-1357 Project: Apache Fineract Issue Type: New Feature Components: Client, Loan Reporter: Benura Abeywardena Assignee: Benura Abeywardena Collateral Management module allows to manage collateral details in product, client & loan levels. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1359) Product Level Collateral Management
Benura Abeywardena created FINERACT-1359: Summary: Product Level Collateral Management Key: FINERACT-1359 URL: https://issues.apache.org/jira/browse/FINERACT-1359 Project: Apache Fineract Issue Type: New Feature Affects Versions: 1.5.0 Reporter: Benura Abeywardena Assignee: Benura Abeywardena Product Level Collateral Management allows users to add, update collaterals -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1031) Advanced accounting for fees not working
[ https://issues.apache.org/jira/browse/FINERACT-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reassigned FINERACT-1031: Assignee: Benura Abeywardena > Advanced accounting for fees not working > - > > Key: FINERACT-1031 > URL: https://issues.apache.org/jira/browse/FINERACT-1031 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Loan >Affects Versions: 1.1.0, 1.3.0 >Reporter: bharath gowda >Assignee: Benura Abeywardena >Priority: Major > Labels: gsoc, p1 > Fix For: 1.6.0 > > Attachments: 1.png, 2.png, 3.png, image-2020-06-14-22-19-54-702.png > > > //Resurfaced Issue // > Deepak's description in mailing list: > > I was to map the different accounting GLs for different Fees. I mapped the > GLs to the respective fees. PFA the screenshot. But still in accounting, the > entry has gone to the single GL > https: demo.openmf.org > username: mifos > password: password > > Loan ID: depk02980 > Product Name: deepak -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350619#comment-17350619 ] Benura Abeywardena commented on FINERACT-1308: -- [~francisguchie] Hi, do you mind verifying this issue as well. I hope this also has been fixed. https://issues.apache.org/jira/browse/FINERACT-1031 > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1031) Advanced accounting for fees not working
[ https://issues.apache.org/jira/browse/FINERACT-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350617#comment-17350617 ] Benura Abeywardena commented on FINERACT-1031: -- [~bgowda] I hope this issue is fixed with the latest code base. Would you mind verifying this? From my side I tested the scenarios and worked well. > Advanced accounting for fees not working > - > > Key: FINERACT-1031 > URL: https://issues.apache.org/jira/browse/FINERACT-1031 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Loan >Affects Versions: 1.1.0, 1.3.0 >Reporter: bharath gowda >Priority: Major > Labels: gsoc, p1 > Fix For: 1.6.0 > > Attachments: 1.png, 2.png, 3.png, image-2020-06-14-22-19-54-702.png > > > //Resurfaced Issue // > Deepak's description in mailing list: > > I was to map the different accounting GLs for different Fees. I mapped the > GLs to the respective fees. PFA the screenshot. But still in accounting, the > entry has gone to the single GL > https: demo.openmf.org > username: mifos > password: password > > Loan ID: depk02980 > Product Name: deepak -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1314) Client Familiy Details Edit not working from client view screen
[
https://issues.apache.org/jira/browse/FINERACT-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350584#comment-17350584
]
Benura Abeywardena commented on FINERACT-1314:
--
[~bgowda] Hi sir, would you mind verifying the changes done in the PR?
> Client Familiy Details Edit not working from client view screen
> ---
>
> Key: FINERACT-1314
> URL: https://issues.apache.org/jira/browse/FINERACT-1314
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: bharath gowda
>Assignee: Benura Abeywardena
>Priority: Minor
>
> Edit option of client family details is not working.
>
> To reproduce,
> # Add family details to the client(do not add profession, gender, and
> marital status)
> # Edit the family details and change any field.
> The system will not accept and the error is not handled in the system
> In the Inspect mode, the system is throwing an internal exception for
> "profession, marital and gender status_cv_id " even though these parameters
> are not mandatory
>
> Expected behavior, the system should allow to Edit the family details, even
> when profession, marital and gender fields are not entered.
>
> Exception example is below
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Cannot add or
> upda
> te a child row: a foreign key constraint fails
> (`fineract_default`.`m_family_mem
> bers`, CONSTRAINT `FK_m_family_members_profession_m_code_value` FOREIGN KEY
> (`pr
> ofession_cv_id`) REFERENCES `m_code_value` (`id`)) {prepstmnt 1120209371
> UPDATE
> m_family_members SET age = ?, firstname = ?, gender_cv_id = ?,
> marital_status_cv
> _id = ?, profession_cv_id = ? WHERE id = ?} [code=1452, state=23000]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17349609#comment-17349609 ] Benura Abeywardena commented on FINERACT-1308: -- [~francisguchie] Great > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17349452#comment-17349452 ] Benura Abeywardena edited comment on FINERACT-1308 at 5/21/21, 9:59 PM: [~francisguchie] Please update once you're done was (Author: blasan): [~francisguchie] Update me once you're done > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17349452#comment-17349452 ] Benura Abeywardena commented on FINERACT-1308: -- [~francisguchie] Update me once you're done > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17349425#comment-17349425 ] Benura Abeywardena edited comment on FINERACT-1308 at 5/21/21, 6:18 PM: [~francisguchie] Would you mind trying with the latest code bases (both the fineract & community app) I think this problem has been resolved now was (Author: blasan): [~francisguchie] Would you mind trying with the latest code bases (both the fineract & community app) > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17349425#comment-17349425 ] Benura Abeywardena commented on FINERACT-1308: -- [~francisguchie] Would you mind trying with the latest code bases (both the fineract & community app) > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17349002#comment-17349002 ] Benura Abeywardena commented on FINERACT-1308: -- [~francisguchie] Hi, would you mind sharing a doc if you have regarding this advanced account rules' db architecture? > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1314) Client Familiy Details Edit not working from client view screen
[
https://issues.apache.org/jira/browse/FINERACT-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benura Abeywardena reassigned FINERACT-1314:
Assignee: Benura Abeywardena
> Client Familiy Details Edit not working from client view screen
> ---
>
> Key: FINERACT-1314
> URL: https://issues.apache.org/jira/browse/FINERACT-1314
> Project: Apache Fineract
> Issue Type: Bug
>Affects Versions: 1.4.0
>Reporter: bharath gowda
>Assignee: Benura Abeywardena
>Priority: Minor
>
> Edit option of client family details is not working.
>
> To reproduce,
> # Add family details to the client(do not add profession, gender, and
> marital status)
> # Edit the family details and change any field.
> The system will not accept and the error is not handled in the system
> In the Inspect mode, the system is throwing an internal exception for
> "profession, marital and gender status_cv_id " even though these parameters
> are not mandatory
>
> Expected behavior, the system should allow to Edit the family details, even
> when profession, marital and gender fields are not entered.
>
> Exception example is below
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Cannot add or
> upda
> te a child row: a foreign key constraint fails
> (`fineract_default`.`m_family_mem
> bers`, CONSTRAINT `FK_m_family_members_profession_m_code_value` FOREIGN KEY
> (`pr
> ofession_cv_id`) REFERENCES `m_code_value` (`id`)) {prepstmnt 1120209371
> UPDATE
> m_family_members SET age = ?, firstname = ?, gender_cv_id = ?,
> marital_status_cv
> _id = ?, profession_cv_id = ? WHERE id = ?} [code=1452, state=23000]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-9) Repayment Transactions allocated to FINANCIAL_ACTIVITY.LIABILITY_TRANSFER
[
https://issues.apache.org/jira/browse/FINERACT-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347764#comment-17347764
]
Benura Abeywardena commented on FINERACT-9:
---
[~Luis.Espinoza] Not yet. I bet you've already found the fix needs to be done
(according to the description). Would you mind opening a PR for this? As you've
already got the answer on your hands :) I'll withdraw my assignment.
> Repayment Transactions allocated to FINANCIAL_ACTIVITY.LIABILITY_TRANSFER
> -
>
> Key: FINERACT-9
> URL: https://issues.apache.org/jira/browse/FINERACT-9
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Reporter: Dayna Harp
>Assignee: Benura Abeywardena
>Priority: Major
> Labels: UpdateRequired, p2
>
> https://mifosforge.jira.com/browse/MIFOSX-2438
> All repayment transactions after an account transfer transaction are
> allocated to FINANCIAL_ACTIVITY.LIABILITY_TRANSFER accountAll repayment
> transactions after an account transfer transaction are allocated to
> FINANCIAL_ACTIVITY.LIABILITY_TRANSFER account.
> This is cause by the "isAccountTransfer" boolean outside the for loop on line
> 108 in
> "https://github.com/openMF/mifosx/blob/develop/mifosng-provider/src/main/java/org/mifosplatform/accounting/journalentry/service/AccountingProcessorHelper.java;
> The boolean should be in the for loop.
> boolean isAccountTransfer = (Boolean)
> accountingBridgeData.get("isAccountTransfer");
> @SuppressWarnings("unchecked")
> final List> newTransactionsMap =
> (List>) accountingBridgeData.get("newLoanTransactions");
> for (final Map map : newTransactionsMap) {
> final Long transactionOfficeId = (Long) map.get("officeId");
> final String transactionId = ((Long) map.get("id")).toString();
> final Date transactionDate = ((LocalDate)
> map.get("date")).toDate();
> final LoanTransactionEnumData transactionType =
> (LoanTransactionEnumData) map.get("type");
> final BigDecimal amount = (BigDecimal) map.get("amount");
> final BigDecimal principal = (BigDecimal)
> map.get("principalPortion");
> final BigDecimal interest = (BigDecimal)
> map.get("interestPortion");
> final BigDecimal fees = (BigDecimal) map.get("feeChargesPortion");
> final BigDecimal penalties = (BigDecimal)
> map.get("penaltyChargesPortion");
> final BigDecimal overPayments = (BigDecimal)
> map.get("overPaymentPortion");
> final boolean reversed = (Boolean) map.get("reversed");
> final Long paymentTypeId = (Long) map.get("paymentTypeId");
> final List feePaymentDetails = new
> ArrayList<>();
> final List penaltyPaymentDetails = new
> ArrayList<>();
> // extract charge payment details (if exists)
> if (map.containsKey("loanChargesPaid")) {
> @SuppressWarnings("unchecked")
> final List> loanChargesPaidData =
> (List>) map.get("loanChargesPaid");
> for (final Map loanChargePaid :
> loanChargesPaidData) {
> final Long chargeId = (Long)
> loanChargePaid.get("chargeId");
> final Long loanChargeId = (Long)
> loanChargePaid.get("loanChargeId");
> final boolean isPenalty = (Boolean)
> loanChargePaid.get("isPenalty");
> final BigDecimal chargeAmountPaid = (BigDecimal)
> loanChargePaid.get("amount");
> final ChargePaymentDTO chargePaymentDTO = new
> ChargePaymentDTO(chargeId, loanChargeId, chargeAmountPaid);
> if (isPenalty) {
> penaltyPaymentDetails.add(chargePaymentDTO);
> } else {
> feePaymentDetails.add(chargePaymentDTO);
> }
> }
> }
> if (!isAccountTransfer) {
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17322075#comment-17322075 ] Benura Abeywardena commented on FINERACT-1308: -- [~bgowda] This needs to be fixed along with the issue #1031 > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-1346) Not able to login with the latest Fineract codebase
[ https://issues.apache.org/jira/browse/FINERACT-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena closed FINERACT-1346. Resolution: Not A Problem > Not able to login with the latest Fineract codebase > --- > > Key: FINERACT-1346 > URL: https://issues.apache.org/jira/browse/FINERACT-1346 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Priority: Major > Fix For: 1.5.0 > > Attachments: Screenshot from 2021-04-14 16-52-03.png > > > Not able to login to the Mifos system using the default credentials > (mifos:password). Refer to the following screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (FINERACT-1346) Not able to login with the latest Fineract codebase
[ https://issues.apache.org/jira/browse/FINERACT-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reopened FINERACT-1346: -- > Not able to login with the latest Fineract codebase > --- > > Key: FINERACT-1346 > URL: https://issues.apache.org/jira/browse/FINERACT-1346 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Priority: Major > Fix For: 1.5.0 > > Attachments: Screenshot from 2021-04-14 16-52-03.png > > > Not able to login to the Mifos system using the default credentials > (mifos:password). Refer to the following screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-1346) Not able to login with the latest Fineract codebase
[ https://issues.apache.org/jira/browse/FINERACT-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena closed FINERACT-1346. Resolution: Fixed Worked for me. Server took little more extra time to be available > Not able to login with the latest Fineract codebase > --- > > Key: FINERACT-1346 > URL: https://issues.apache.org/jira/browse/FINERACT-1346 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Priority: Major > Fix For: 1.5.0 > > Attachments: Screenshot from 2021-04-14 16-52-03.png > > > Not able to login to the Mifos system using the default credentials > (mifos:password). Refer to the following screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1346) Not able to login with the latest Fineract codebase
[ https://issues.apache.org/jira/browse/FINERACT-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320923#comment-17320923 ] Benura Abeywardena commented on FINERACT-1346: -- [~bgowda] [~vorburger] please take a look. Followed the documentation and did as it says. > Not able to login with the latest Fineract codebase > --- > > Key: FINERACT-1346 > URL: https://issues.apache.org/jira/browse/FINERACT-1346 > Project: Apache Fineract > Issue Type: Bug >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Priority: Major > Fix For: 1.5.0 > > Attachments: Screenshot from 2021-04-14 16-52-03.png > > > Not able to login to the Mifos system using the default credentials > (mifos:password). Refer to the following screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1346) Not able to login with the latest Fineract codebase
Benura Abeywardena created FINERACT-1346: Summary: Not able to login with the latest Fineract codebase Key: FINERACT-1346 URL: https://issues.apache.org/jira/browse/FINERACT-1346 Project: Apache Fineract Issue Type: Bug Affects Versions: 1.4.0 Reporter: Benura Abeywardena Fix For: 1.5.0 Attachments: Screenshot from 2021-04-14 16-52-03.png Not able to login to the Mifos system using the default credentials (mifos:password). Refer to the following screenshot. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1264) Email Campaigns with Pentaho Reporting Attachments are broken
[
https://issues.apache.org/jira/browse/FINERACT-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317428#comment-17317428
]
Benura Abeywardena edited comment on FINERACT-1264 at 4/9/21, 3:53 AM:
---
[~bgowda] [~vorburger] [~aleks] Is this all about email sending ?
[https://github.com/apache/fineract/pull/1597]
was (Author: blasan):
[~bgowda] [~vorburger] Is this all about email sending ?
https://github.com/apache/fineract/pull/1597
> Email Campaigns with Pentaho Reporting Attachments are broken
> -
>
> Key: FINERACT-1264
> URL: https://issues.apache.org/jira/browse/FINERACT-1264
> Project: Apache Fineract
> Issue Type: Bug
> Components: Reports
>Reporter: Michael Vorburger
>Priority: Critical
> Labels: email
>
> While working on FINERACT-1173, I've noticed that
> {{org.apache.fineract.infrastructure.campaigns.email.service.EmailCampaignWritePlatformCommandHandlerImpl.generateAttachments(EmailCampaign,
> ScheduledEmailAttachmentFileFormat, Map, String,
> StringBuilder)}} use of
> {{org.apache.fineract.infrastructure.dataqueries.service.ReadReportingService.generatePentahoReportAsOutputStream(String,
> String, Map, Locale, AppUser, StringBuilder)}} calls code
> that is completely commented out.
> This was, apparently, broken during the migration from Mifos to Fineract,
> because of the Pentaho removal.
> Fixing that will take a little bit of refactoring. I'd like to do that only
> after having completed FINERACT-1173 (and FINERACT-1177) and having the 2nd
> version of [https://github.com/vorburger/fineract-pentaho]. Once that is
> done, we can pick this up.
> We'll need to change {{ReportingProcessService}} to not be tied to
> {{javax.ws.rs.core.Response}}, as Aleks has done in
> [https://github.com/apache/fineract/pull/1416], so that will be part of the
> answer to fix this. (Although I would suggest that instead of instead of an
> {{OutputStream}} in the Reporting Plugin API we use a
> {{com.google.common.io.ByteSource}}, which can be easily adapted to the
> {{org.springframework.core.io.InputStreamSource}} that
> {{org.springframework.mail.javamail.MimeMessageHelper.addAttachment()}} digs;
> but that's a detail.)
> [~aleks] and [~ptuomola] FYI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1264) Email Campaigns with Pentaho Reporting Attachments are broken
[
https://issues.apache.org/jira/browse/FINERACT-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17317428#comment-17317428
]
Benura Abeywardena commented on FINERACT-1264:
--
[~bgowda] [~vorburger] Is this all about email sending ?
https://github.com/apache/fineract/pull/1597
> Email Campaigns with Pentaho Reporting Attachments are broken
> -
>
> Key: FINERACT-1264
> URL: https://issues.apache.org/jira/browse/FINERACT-1264
> Project: Apache Fineract
> Issue Type: Bug
> Components: Reports
>Reporter: Michael Vorburger
>Priority: Critical
> Labels: email
>
> While working on FINERACT-1173, I've noticed that
> {{org.apache.fineract.infrastructure.campaigns.email.service.EmailCampaignWritePlatformCommandHandlerImpl.generateAttachments(EmailCampaign,
> ScheduledEmailAttachmentFileFormat, Map, String,
> StringBuilder)}} use of
> {{org.apache.fineract.infrastructure.dataqueries.service.ReadReportingService.generatePentahoReportAsOutputStream(String,
> String, Map, Locale, AppUser, StringBuilder)}} calls code
> that is completely commented out.
> This was, apparently, broken during the migration from Mifos to Fineract,
> because of the Pentaho removal.
> Fixing that will take a little bit of refactoring. I'd like to do that only
> after having completed FINERACT-1173 (and FINERACT-1177) and having the 2nd
> version of [https://github.com/vorburger/fineract-pentaho]. Once that is
> done, we can pick this up.
> We'll need to change {{ReportingProcessService}} to not be tied to
> {{javax.ws.rs.core.Response}}, as Aleks has done in
> [https://github.com/apache/fineract/pull/1416], so that will be part of the
> answer to fix this. (Although I would suggest that instead of instead of an
> {{OutputStream}} in the Reporting Plugin API we use a
> {{com.google.common.io.ByteSource}}, which can be easily adapted to the
> {{org.springframework.core.io.InputStreamSource}} that
> {{org.springframework.mail.javamail.MimeMessageHelper.addAttachment()}} digs;
> but that's a detail.)
> [~aleks] and [~ptuomola] FYI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (FINERACT-1339) Cannot create Client Loan Application
[
https://issues.apache.org/jira/browse/FINERACT-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benura Abeywardena closed FINERACT-1339.
Resolution: Fixed
Worked for me
> Cannot create Client Loan Application
> -
>
> Key: FINERACT-1339
> URL: https://issues.apache.org/jira/browse/FINERACT-1339
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Affects Versions: 1.4.0
>Reporter: Benura Abeywardena
>Priority: Major
> Labels: p1
> Fix For: 1.5.0
>
> Attachments: Screenshot from 2021-04-05 01-58-12.png
>
>
> Tried creating a Loan Application with following details as in the
> attachment. But nothing returns. (Checked the server logs but it's not going
> to even prints the logs)
>
> {code:java}
> java.lang.NumberFormatException: Character N is neither a decimal digit
> number, decimal point, nor "e" notation exponential mark.
> at java.base/java.math.BigDecimal.(BigDecimal.java:518)
> at java.base/java.math.BigDecimal.(BigDecimal.java:401)
> at java.base/java.math.BigDecimal.(BigDecimal.java:834)
> at java.base/java.math.BigDecimal.valueOf(BigDecimal.java:1304)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.LoanApplicationTerms.paymentPerPeriod(LoanApplicationTerms.java:1230)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.LoanApplicationTerms.calculateTotalDueForEqualInstallmentRepaymentPeriod(LoanApplicationTerms.java:1335)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.LoanApplicationTerms.pmtForInstallment(LoanApplicationTerms.java:642)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.updateFixedInstallmentAmount(AbstractLoanScheduleGenerator.java:1324)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.updateAmortization(AbstractLoanScheduleGenerator.java:2556)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.generate(AbstractLoanScheduleGenerator.java:132)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.generate(AbstractLoanScheduleGenerator.java:67)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.service.LoanScheduleAssembler.assembleLoanScheduleFrom(LoanScheduleAssembler.java:650)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanAssembler.assembleApplication(LoanAssembler.java:310)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanAssembler.assembleFrom(LoanAssembler.java:164)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanApplicationWritePlatformServiceJpaRepositoryImpl.submitApplication(LoanApplicationWritePlatformServiceJpaRepositoryImpl.java:316)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanApplicationWritePlatformServiceJpaRepositoryImpl$$FastClassBySpringCGLIB$$982a3270.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:367)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:118)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:691)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanApplicationWritePlatformServiceJpaRepositoryImpl$$EnhancerBySpringCGLIB$$3a8b3011.submitApplication()
> at
> org.apache.fineract.portfolio.loanaccount.handler.LoanApplicationSubmittalCommandHandler.processCommand(LoanApplicationSubmittalCommandHandler.java:45)
> at
> org.apache.fineract.portfolio.loanaccount.handler.LoanApplicationSubmittalCommandHandler$$FastClassBySpringCGLIB$$8c589fff.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
>
[jira] [Commented] (FINERACT-1339) Cannot create Client Loan Application
[
https://issues.apache.org/jira/browse/FINERACT-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17316210#comment-17316210
]
Benura Abeywardena commented on FINERACT-1339:
--
[~bgowda] Was able to create one. Thanks :)
> Cannot create Client Loan Application
> -
>
> Key: FINERACT-1339
> URL: https://issues.apache.org/jira/browse/FINERACT-1339
> Project: Apache Fineract
> Issue Type: Bug
> Components: Loan
>Affects Versions: 1.4.0
>Reporter: Benura Abeywardena
>Priority: Major
> Labels: p1
> Fix For: 1.5.0
>
> Attachments: Screenshot from 2021-04-05 01-58-12.png
>
>
> Tried creating a Loan Application with following details as in the
> attachment. But nothing returns. (Checked the server logs but it's not going
> to even prints the logs)
>
> {code:java}
> java.lang.NumberFormatException: Character N is neither a decimal digit
> number, decimal point, nor "e" notation exponential mark.
> at java.base/java.math.BigDecimal.(BigDecimal.java:518)
> at java.base/java.math.BigDecimal.(BigDecimal.java:401)
> at java.base/java.math.BigDecimal.(BigDecimal.java:834)
> at java.base/java.math.BigDecimal.valueOf(BigDecimal.java:1304)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.LoanApplicationTerms.paymentPerPeriod(LoanApplicationTerms.java:1230)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.LoanApplicationTerms.calculateTotalDueForEqualInstallmentRepaymentPeriod(LoanApplicationTerms.java:1335)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.LoanApplicationTerms.pmtForInstallment(LoanApplicationTerms.java:642)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.updateFixedInstallmentAmount(AbstractLoanScheduleGenerator.java:1324)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.updateAmortization(AbstractLoanScheduleGenerator.java:2556)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.generate(AbstractLoanScheduleGenerator.java:132)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.generate(AbstractLoanScheduleGenerator.java:67)
> at
> org.apache.fineract.portfolio.loanaccount.loanschedule.service.LoanScheduleAssembler.assembleLoanScheduleFrom(LoanScheduleAssembler.java:650)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanAssembler.assembleApplication(LoanAssembler.java:310)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanAssembler.assembleFrom(LoanAssembler.java:164)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanApplicationWritePlatformServiceJpaRepositoryImpl.submitApplication(LoanApplicationWritePlatformServiceJpaRepositoryImpl.java:316)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanApplicationWritePlatformServiceJpaRepositoryImpl$$FastClassBySpringCGLIB$$982a3270.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:367)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:118)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:691)
> at
> org.apache.fineract.portfolio.loanaccount.service.LoanApplicationWritePlatformServiceJpaRepositoryImpl$$EnhancerBySpringCGLIB$$3a8b3011.submitApplication()
> at
> org.apache.fineract.portfolio.loanaccount.handler.LoanApplicationSubmittalCommandHandler.processCommand(LoanApplicationSubmittalCommandHandler.java:45)
> at
> org.apache.fineract.portfolio.loanaccount.handler.LoanApplicationSubmittalCommandHandler$$FastClassBySpringCGLIB$$8c589fff.invoke()
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
> at
>
[jira] [Commented] (FINERACT-592) Undo a charge waive
[ https://issues.apache.org/jira/browse/FINERACT-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17315795#comment-17315795 ] Benura Abeywardena commented on FINERACT-592: - [~bgowda] [~anthonype...@gmail.com] Thanks for the responses :) > Undo a charge waive > --- > > Key: FINERACT-592 > URL: https://issues.apache.org/jira/browse/FINERACT-592 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Jan Antonie Peens >Priority: Minor > Labels: confirm, gsoc, p2 > Attachments: image-2021-04-06-20-06-08-917.png > > > Reverse a charge waiver. > We have gotten the situation were a charge was waived by accident and we > would therefore like to undo the mistake. > Would such a feature be possible? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-592) Undo a charge waive
[ https://issues.apache.org/jira/browse/FINERACT-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314668#comment-17314668 ] Benura Abeywardena commented on FINERACT-592: - [~bgowda] Would you mind adding a use case of this feature with steps to reproduce? :) > Undo a charge waive > --- > > Key: FINERACT-592 > URL: https://issues.apache.org/jira/browse/FINERACT-592 > Project: Apache Fineract > Issue Type: Improvement > Components: Loan >Reporter: Jan Antonie Peens >Priority: Minor > Labels: confirm, gsoc, p2 > > Reverse a charge waiver. > We have gotten the situation were a charge was waived by accident and we > would therefore like to undo the mistake. > Would such a feature be possible? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1339) Cannot create Client Loan Application
[
https://issues.apache.org/jira/browse/FINERACT-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benura Abeywardena updated FINERACT-1339:
-
Description:
Tried creating a Loan Application with following details as in the attachment.
But nothing returns. (Checked the server logs but it's not going to even prints
the logs)
{code:java}
java.lang.NumberFormatException: Character N is neither a decimal digit number,
decimal point, nor "e" notation exponential mark.
at java.base/java.math.BigDecimal.(BigDecimal.java:518)
at java.base/java.math.BigDecimal.(BigDecimal.java:401)
at java.base/java.math.BigDecimal.(BigDecimal.java:834)
at java.base/java.math.BigDecimal.valueOf(BigDecimal.java:1304)
at
org.apache.fineract.portfolio.loanaccount.loanschedule.domain.LoanApplicationTerms.paymentPerPeriod(LoanApplicationTerms.java:1230)
at
org.apache.fineract.portfolio.loanaccount.loanschedule.domain.LoanApplicationTerms.calculateTotalDueForEqualInstallmentRepaymentPeriod(LoanApplicationTerms.java:1335)
at
org.apache.fineract.portfolio.loanaccount.loanschedule.domain.LoanApplicationTerms.pmtForInstallment(LoanApplicationTerms.java:642)
at
org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.updateFixedInstallmentAmount(AbstractLoanScheduleGenerator.java:1324)
at
org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.updateAmortization(AbstractLoanScheduleGenerator.java:2556)
at
org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.generate(AbstractLoanScheduleGenerator.java:132)
at
org.apache.fineract.portfolio.loanaccount.loanschedule.domain.AbstractLoanScheduleGenerator.generate(AbstractLoanScheduleGenerator.java:67)
at
org.apache.fineract.portfolio.loanaccount.loanschedule.service.LoanScheduleAssembler.assembleLoanScheduleFrom(LoanScheduleAssembler.java:650)
at
org.apache.fineract.portfolio.loanaccount.service.LoanAssembler.assembleApplication(LoanAssembler.java:310)
at
org.apache.fineract.portfolio.loanaccount.service.LoanAssembler.assembleFrom(LoanAssembler.java:164)
at
org.apache.fineract.portfolio.loanaccount.service.LoanApplicationWritePlatformServiceJpaRepositoryImpl.submitApplication(LoanApplicationWritePlatformServiceJpaRepositoryImpl.java:316)
at
org.apache.fineract.portfolio.loanaccount.service.LoanApplicationWritePlatformServiceJpaRepositoryImpl$$FastClassBySpringCGLIB$$982a3270.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at
org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:367)
at
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:118)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:691)
at
org.apache.fineract.portfolio.loanaccount.service.LoanApplicationWritePlatformServiceJpaRepositoryImpl$$EnhancerBySpringCGLIB$$3a8b3011.submitApplication()
at
org.apache.fineract.portfolio.loanaccount.handler.LoanApplicationSubmittalCommandHandler.processCommand(LoanApplicationSubmittalCommandHandler.java:45)
at
org.apache.fineract.portfolio.loanaccount.handler.LoanApplicationSubmittalCommandHandler$$FastClassBySpringCGLIB$$8c589fff.invoke()
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:771)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at
org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:367)
at
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:118)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:749)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:691)
at
[jira] [Commented] (FINERACT-1339) Cannot create Client Loan Application
[ https://issues.apache.org/jira/browse/FINERACT-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314615#comment-17314615 ] Benura Abeywardena commented on FINERACT-1339: -- [~bgowda] Please take a look. Thanks :) > Cannot create Client Loan Application > - > > Key: FINERACT-1339 > URL: https://issues.apache.org/jira/browse/FINERACT-1339 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Priority: Major > Labels: p1 > Fix For: 1.5.0 > > Attachments: Screenshot from 2021-04-05 01-58-12.png > > > Tried creating a Loan Application with following details as in the > attachment. But nothing returns. (Checked the server logs but it's not going > to even prints the logs) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-1339) Cannot create Client Loan Application
Benura Abeywardena created FINERACT-1339: Summary: Cannot create Client Loan Application Key: FINERACT-1339 URL: https://issues.apache.org/jira/browse/FINERACT-1339 Project: Apache Fineract Issue Type: Bug Components: Loan Affects Versions: 1.4.0 Reporter: Benura Abeywardena Fix For: 1.5.0 Attachments: Screenshot from 2021-04-05 01-58-12.png Tried creating a Loan Application with following details as in the attachment. But nothing returns. (Checked the server logs but it's not going to even prints the logs) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1334) Fineract Credit Bureau Integration Phase 4
[ https://issues.apache.org/jira/browse/FINERACT-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17301067#comment-17301067 ] Benura Abeywardena commented on FINERACT-1334: -- [~edcable] Sir, I've an interest for working on this. Can anyone apply for this idea? > Fineract Credit Bureau Integration Phase 4 > -- > > Key: FINERACT-1334 > URL: https://issues.apache.org/jira/browse/FINERACT-1334 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ed Cable >Priority: Major > Labels: gsoc2021, mentor > > h2. Mentors > * [~nikhilpa...@yahoo.in] > * [~rrpawar] > Nayan Ambali, Ed Cable > h2. Overview & Objectives > Because of regulatory reasons or to do background check of a client (risk > management), MFIs depend on credit bureaus. As part of it, MFI must submit > client details to credit bureau and also need to pull client information from > credit bureau before approving any new loans to a client. Apache Fineract can > be integrated with a popular CBs in India and from other regions (based on > the demand). > h2. Description > Building off the work that was kicked off in 2016, during the 2020 Google > Summer of Code, Rahul Pawar, completed the credit bureau integration module > with integrations for the credit bureau in Myanmar, MCIX. This project will > continue extending the functionality of the module and work on integrations > with the major credit bureaus in Latin America and Sub-Saharan Africa. > The major functionality will be sending the data to CBs on regular intervals > in the format CB expects. And option to pull the client’s information from CB > whenever loan officer/branch manager/ user wants to view the information for > a particular client. > h2.Helpful Skills > SQL, Java, Javascript, Git, Web Services, Big Data (Hadoop, Hive) > h2. Impact > The credit report shows account information such as repayment record, > defaults, type of loan, amount of loan, etc. of the customer. This > information facilitates prudent decision-making when the credit underwriter > processes the loan application. This help MFI to reduce the risk of bad loans > and reduces the multiple lendings to same person from different MFIs. > h2. Other Resources > Documentation: > https://cwiki.apache.org/confluence/display/FINERACT/Documentation+to+use+Integrated+Credit+Bureau > For the scope of this project , see > https://jira.apache.org/jira/browse/FINERACT-734 > Detailed requirements: https://goo.gl/aZWMZa > Source Code: > https://github.com/apache/fineract/pulls?q=is%3Apr+is%3Aclosed+credit+bureau -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1335) Integration Test Email Sending features
[ https://issues.apache.org/jira/browse/FINERACT-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300914#comment-17300914 ] Benura Abeywardena commented on FINERACT-1335: -- [~vorburger] Please consider Francis's comment sir :) Will check on these ASAP > Integration Test Email Sending features > --- > > Key: FINERACT-1335 > URL: https://issues.apache.org/jira/browse/FINERACT-1335 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Priority: Major > > Finearact has a number of features which send emails. > They are currently not tested - the goal here would be to add integration > test coverage for those feature. > https://greenmail-mail-test.github.io/greenmail/ to me seems like a great > tool to do this! > FINERACT-1070 and FINERACT-1270 have some context. > [~BLasan] [~francisguchie] [~ptuomola] interested in taking this? ;) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1270) Unify Fineract 3 (!) different email sender utilities
[
https://issues.apache.org/jira/browse/FINERACT-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300909#comment-17300909
]
Benura Abeywardena edited comment on FINERACT-1270 at 3/13/21, 4:15 PM:
[~vorburger] This is a good point. Will resolve the issue
https://issues.apache.org/jira/browse/FINERACT-1335?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
first. [~francisguchie] Need your help :)
was (Author: blasan):
[~vorburger] This is a good point. Will resolve the issue
https://issues.apache.org/jira/browse/FINERACT-1335?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
first. [~francisguchie] Need you help :)
> Unify Fineract 3 (!) different email sender utilities
> -
>
> Key: FINERACT-1270
> URL: https://issues.apache.org/jira/browse/FINERACT-1270
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Michael Vorburger
>Priority: Major
>
> While looking into addressing FINERACT-1092, I've just noticed that the
> Fineract code base has not 1 and not 2 but 3 (!) classes which send email:
> *
> org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService
> *
> org.apache.fineract.infrastructure.campaigns.email.service.EmailMessageJobEmailServiceImpl
> *
> org.apache.fineract.infrastructure.reportmailingjob.service.ReportMailingJobEmailServiceImpl
> The best thing is that 2 of those use {{org.springframework.mail.javamail}}
> whereas the 3rd (and probably oldest?) uses {{org.apache.commons.mail}}
> instead.
> They, apparently, also use 3 completely different mail server configurations
> in the database! This doesn't make any sense - I cannot imagine anyone
> wanting to use 3 different mail server for 3 purposes.
> Let's merge all this? Best step by step, in a series of several small PRs,
> instead of 1 big one. The DB change may also require DB migration scripts to
> remove the old config (depending on how we want to "migrate").
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1270) Unify Fineract 3 (!) different email sender utilities
[
https://issues.apache.org/jira/browse/FINERACT-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300909#comment-17300909
]
Benura Abeywardena commented on FINERACT-1270:
--
[~vorburger] This is a good point. Will resolve the issue
https://issues.apache.org/jira/browse/FINERACT-1335?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
first. [~francisguchie] Need you help :)
> Unify Fineract 3 (!) different email sender utilities
> -
>
> Key: FINERACT-1270
> URL: https://issues.apache.org/jira/browse/FINERACT-1270
> Project: Apache Fineract
> Issue Type: Improvement
>Reporter: Michael Vorburger
>Priority: Major
>
> While looking into addressing FINERACT-1092, I've just noticed that the
> Fineract code base has not 1 and not 2 but 3 (!) classes which send email:
> *
> org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService
> *
> org.apache.fineract.infrastructure.campaigns.email.service.EmailMessageJobEmailServiceImpl
> *
> org.apache.fineract.infrastructure.reportmailingjob.service.ReportMailingJobEmailServiceImpl
> The best thing is that 2 of those use {{org.springframework.mail.javamail}}
> whereas the 3rd (and probably oldest?) uses {{org.apache.commons.mail}}
> instead.
> They, apparently, also use 3 completely different mail server configurations
> in the database! This doesn't make any sense - I cannot imagine anyone
> wanting to use 3 different mail server for 3 purposes.
> Let's merge all this? Best step by step, in a series of several small PRs,
> instead of 1 big one. The DB change may also require DB migration scripts to
> remove the old config (depending on how we want to "migrate").
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1335) Integration Test Email Sending features
[ https://issues.apache.org/jira/browse/FINERACT-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300908#comment-17300908 ] Benura Abeywardena commented on FINERACT-1335: -- [~vorburger] That would be great sir!! [~francisguchie] Shall we take up this issue? > Integration Test Email Sending features > --- > > Key: FINERACT-1335 > URL: https://issues.apache.org/jira/browse/FINERACT-1335 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger >Priority: Major > > Finearact has a number of features which send emails. > They are currently not tested - the goal here would be to add integration > test coverage for those feature. > https://greenmail-mail-test.github.io/greenmail/ to me seems like a great > tool to do this! > FINERACT-1070 and FINERACT-1270 have some context. > [~BLasan] [~francisguchie] [~ptuomola] interested in taking this? ;) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1089) Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY in InterestRateChartReadPlatformServiceImpl
[
https://issues.apache.org/jira/browse/FINERACT-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296849#comment-17296849
]
Benura Abeywardena commented on FINERACT-1089:
--
[~aleks] Will give an update by tonight
> Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY in
> InterestRateChartReadPlatformServiceImpl
> --
>
> Key: FINERACT-1089
> URL: https://issues.apache.org/jira/browse/FINERACT-1089
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Michael Vorburger
>Assignee: Benura Abeywardena
>Priority: Blocker
> Fix For: 1.5.0
>
>
> See FINERACT-932 for general background; I've found this in logs of
> https://www.fineract.dev, this seems to be a similar problem to that was
> previously fixed in FINERACT-995 and FINERACT-1061:
> {noformat}
> org.springframework.dao.TransientDataAccessResourceException:
> PreparedStatementCallback; SQL [select irc.id as ircId, irc.name as ircName,
> irc.description as ircDescription,irc.from_date as ircFromDate, irc.end_date
> as ircEndDate, irc.is_primary_grouping_by_amount as
> isPrimaryGroupingByAmount, ircd.id as ircdId, ircd.description as
> ircdDescription, ircd.period_type_enum ircdPeriodTypeId, ircd.from_period as
> ircdFromPeriod, ircd.to_period as ircdToPeriod, ircd.amount_range_from as
> ircdAmountRangeFrom, ircd.amount_range_to as ircdAmountRangeTo,
> ircd.annual_interest_rate as ircdAnnualInterestRate, curr.code as
> currencyCode, curr.name as currencyName, curr.internationalized_name_code as
> currencyNameCode, curr.display_symbol as currencyDisplaySymbol,
> curr.decimal_places as currencyDigits, curr.currency_multiplesof as
> inMultiplesOf, sp.id as savingsProductId, sp.name as savingsProductName,
> iri.id as iriId, iri.entiry_type as entityType, iri.attribute_name as
> attributeName , iri.condition_type as conditionType, iri.attribute_value as
> attributeValue, iri.incentive_type as incentiveType, iri.amount as amount,
> code.code_value as attributeValueDesc from m_interest_rate_chart irc left
> join m_interest_rate_slab ircd on irc.id=ircd.interest_rate_chart_id left
> join m_interest_incentives iri on iri.interest_rate_slab_id = ircd.id left
> join m_code_value code on code.id = iri.attribute_value left join m_currency
> curr on ircd.currency_code= curr.code left join
> m_deposit_product_interest_rate_chart dpirc on
> irc.id=dpirc.interest_rate_chart_id left join m_savings_product sp on
> sp.id=dpirc.deposit_product_id where sp.id = ? order by irc.id, CASE WHEN
> isPrimaryGroupingByAmount then ircd.amount_range_from WHEN
> isPrimaryGroupingByAmount then ircd.amount_range_to END,ircd.from_period,
> ircd.to_period,CASE WHEN !isPrimaryGroupingByAmount then
> ircd.amount_range_from WHEN !isPrimaryGroupingByAmount then
> ircd.amount_range_to END]; Operation not allowed for a result set of type
> ResultSet.TYPE_FORWARD_ONLY.; nested exception is java.sql.SQLException:
> Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY.
> at
> org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.doTranslate
> (SQLStateSQLExceptionTranslator.java:110)
> at
> org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate
> (AbstractFallbackSQLExceptionTranslator.java:72)
> at
> org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate
> (AbstractFallbackSQLExceptionTranslator.java:81)
> at
> org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate
> (AbstractFallbackSQLExceptionTranslator.java:81)
> at org.springframework.jdbc.core.JdbcTemplate.translateException
> (JdbcTemplate.java:1443)
> at org.springframework.jdbc.core.JdbcTemplate.execute
> (JdbcTemplate.java:633)
> at org.springframework.jdbc.core.JdbcTemplate.query
> (JdbcTemplate.java:669)
> at org.springframework.jdbc.core.JdbcTemplate.query
> (JdbcTemplate.java:700)
> at org.springframework.jdbc.core.JdbcTemplate.query
> (JdbcTemplate.java:718)
> at
> org.apache.fineract.portfolio.interestratechart.service.InterestRateChartReadPlatformServiceImpl.retrieveAllWithSlabs
> (InterestRateChartReadPlatformServiceImpl.java:102)
> Caused by: java.sql.SQLException: Operation not allowed for a result set of
> type ResultSet.TYPE_FORWARD_ONLY.
> at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException
> (SQLError.java:129)
> at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException
> (SQLError.java:97)
> at
> com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException
> (SQLExceptionsMapping.java:122)
> at
[jira] [Created] (FINERACT-1324) Add resource limits to FINERACT server
Benura Abeywardena created FINERACT-1324: Summary: Add resource limits to FINERACT server Key: FINERACT-1324 URL: https://issues.apache.org/jira/browse/FINERACT-1324 Project: Apache Fineract Issue Type: Improvement Affects Versions: 1.4.0 Reporter: Benura Abeywardena Assignee: Benura Abeywardena Fix For: 1.5.0 It's good to add resource limits and requests in order to stop fineract server from over consuming the cluster resources -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1296) Needs to add Liveness & Readiness Probes for fineract server deployment
[ https://issues.apache.org/jira/browse/FINERACT-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena resolved FINERACT-1296. -- Resolution: Fixed > Needs to add Liveness & Readiness Probes for fineract server deployment > --- > > Key: FINERACT-1296 > URL: https://issues.apache.org/jira/browse/FINERACT-1296 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > It's better to add liveliness & readiness probes for fineract container in > order to avoid manual restarting of a container if it gets failed and to > determine when the container will be available for accepting traffic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1296) Needs to add Liveness & Readiness Probes for fineract server deployment
[ https://issues.apache.org/jira/browse/FINERACT-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292610#comment-17292610 ] Benura Abeywardena commented on FINERACT-1296: -- [~aleks] I'll make a PR for this today :) > Needs to add Liveness & Readiness Probes for fineract server deployment > --- > > Key: FINERACT-1296 > URL: https://issues.apache.org/jira/browse/FINERACT-1296 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > It's better to add liveliness & readiness probes for fineract container in > order to avoid manual restarting of a container if it gets failed and to > determine when the container will be available for accepting traffic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1012) Spring Security OAuth 2.x to Spring Security 5.2.x
[
https://issues.apache.org/jira/browse/FINERACT-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292584#comment-17292584
]
Benura Abeywardena commented on FINERACT-1012:
--
[~aleks] Sorry sir, I didn't have a time to spend for this issue. If we are in
a hurry to release shall we move this issue for the next release sir?
> Spring Security OAuth 2.x to Spring Security 5.2.x
> --
>
> Key: FINERACT-1012
> URL: https://issues.apache.org/jira/browse/FINERACT-1012
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.4.0
>Reporter: Michael Vorburger
>Assignee: Benura Abeywardena
>Priority: Critical
> Labels: beginner
> Fix For: 1.5.0
>
>
> The bump of spring-security-oauth2 from 2.3.6.RELEASE to 2.4.1.RELEASE in
> https://github.com/apache/fineract/pull/863 as part of FINERACT-963
> introduced usage of {{@Deprecated}} code, which we are trying to avoid (and
> which since FINERACT-959 we're intentionally making the build fail).
> I'm going to use a {{@SuppressWarnings("deprecation")}} to be able to do the
> upgrade anyway, because upgrading a security related library to its latest
> version seems like a sensible thing to do, but we really should remove the
> suppression and switch to using Spring's newer APIs.
> https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide
> affects {{UserDetailsApiResource}} and
> {{TwoFactorAuthenticationFilter.createUpdatedAuthentication()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292581#comment-17292581 ] Benura Abeywardena commented on FINERACT-1070: -- [~aleks] I've already opened a PR for this. Check [https://github.com/apache/fineract/pull/1597] . Need a review from you and [~vorburger] sir > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png, image-2021-02-06-00-17-36-048.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1296) Needs to add Liveness & Readiness Probes for fineract server deployment
[ https://issues.apache.org/jira/browse/FINERACT-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292579#comment-17292579 ] Benura Abeywardena commented on FINERACT-1296: -- [~aleks] Sir, this is for k8s deployment. Not an essential one. But it's good if we could set up liveness and readiness probes for the fineract pod too. This can be fixed within 1 day. > Needs to add Liveness & Readiness Probes for fineract server deployment > --- > > Key: FINERACT-1296 > URL: https://issues.apache.org/jira/browse/FINERACT-1296 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > It's better to add liveliness & readiness probes for fineract container in > order to avoid manual restarting of a container if it gets failed and to > determine when the container will be available for accepting traffic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1296) Needs to add Liveness & Readiness Probes for fineract server deployment
[ https://issues.apache.org/jira/browse/FINERACT-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena updated FINERACT-1296: - Summary: Needs to add Liveness & Readiness Probes for fineract server deployment (was: Needs to add Liveliness & Readiness Probes for fineract server deployment) > Needs to add Liveness & Readiness Probes for fineract server deployment > --- > > Key: FINERACT-1296 > URL: https://issues.apache.org/jira/browse/FINERACT-1296 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > It's better to add liveliness & readiness probes for fineract container in > order to avoid manual restarting of a container if it gets failed and to > determine when the container will be available for accepting traffic -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17291367#comment-17291367 ] Benura Abeywardena commented on FINERACT-1070: -- [~francisguchie] [~vorburger] I think this is due to the smtp server configurations we've done. (According to [~al...@imperialcoop.com]'s comment) I think we could close this issue and the relevant PR > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png, image-2021-02-06-00-17-36-048.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-935) StaffNotFoundException at StaffRepositoryWrapper
[
https://issues.apache.org/jira/browse/FINERACT-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17287983#comment-17287983
]
Benura Abeywardena commented on FINERACT-935:
-
[~vorburger] Still valid?
> StaffNotFoundException at StaffRepositoryWrapper
>
>
> Key: FINERACT-935
> URL: https://issues.apache.org/jira/browse/FINERACT-935
> Project: Apache Fineract
> Issue Type: Bug
>Reporter: Michael Vorburger
>Priority: Major
>
> See FINERACT-932 for general background, and determine if this error log can
> and should be "fixed", or if this represents a condition that shouldn't be
> logged as an error (or conclude that this is a totally valid error log that
> is useful, any why):
> {code}org.apache.fineract.organisation.staff.exception.StaffNotFoundException
> at
> org.apache.fineract.organisation.staff.domain.StaffRepositoryWrapper.lambda$findByOfficeHierarchyWithNotFoundDetection$1(StaffRepositoryWrapper.java:54)
> at java.util.Optional.orElseThrow(Optional.java:290)
> at
> org.apache.fineract.organisation.staff.domain.StaffRepositoryWrapper.findByOfficeHierarchyWithNotFoundDetection(StaffRepositoryWrapper.java:54)
> at
> org.apache.fineract.portfolio.client.service.ClientWritePlatformServiceJpaRepositoryImpl.createClient(ClientWritePlatformServiceJpaRepositoryImpl.java:248)
> at
> org.apache.fineract.portfolio.client.service.ClientWritePlatformServiceJpaRepositoryImpl$$FastClassBySpringCGLIB$$71ca1b7f.invoke(){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1012) Spring Security OAuth 2.x to Spring Security 5.2.x
[
https://issues.apache.org/jira/browse/FINERACT-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17280546#comment-17280546
]
Benura Abeywardena commented on FINERACT-1012:
--
[~vorburger] Thanks for the response sir :)
> Spring Security OAuth 2.x to Spring Security 5.2.x
> --
>
> Key: FINERACT-1012
> URL: https://issues.apache.org/jira/browse/FINERACT-1012
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.4.0
>Reporter: Michael Vorburger
>Priority: Critical
> Labels: beginner
> Fix For: 1.5.0
>
>
> The bump of spring-security-oauth2 from 2.3.6.RELEASE to 2.4.1.RELEASE in
> https://github.com/apache/fineract/pull/863 as part of FINERACT-963
> introduced usage of {{@Deprecated}} code, which we are trying to avoid (and
> which since FINERACT-959 we're intentionally making the build fail).
> I'm going to use a {{@SuppressWarnings("deprecation")}} to be able to do the
> upgrade anyway, because upgrading a security related library to its latest
> version seems like a sensible thing to do, but we really should remove the
> suppression and switch to using Spring's newer APIs.
> https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide
> affects {{UserDetailsApiResource}} and
> {{TwoFactorAuthenticationFilter.createUpdatedAuthentication()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FINERACT-1012) Spring Security OAuth 2.x to Spring Security 5.2.x
[
https://issues.apache.org/jira/browse/FINERACT-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benura Abeywardena reassigned FINERACT-1012:
Assignee: Benura Abeywardena
> Spring Security OAuth 2.x to Spring Security 5.2.x
> --
>
> Key: FINERACT-1012
> URL: https://issues.apache.org/jira/browse/FINERACT-1012
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.4.0
>Reporter: Michael Vorburger
>Assignee: Benura Abeywardena
>Priority: Critical
> Labels: beginner
> Fix For: 1.5.0
>
>
> The bump of spring-security-oauth2 from 2.3.6.RELEASE to 2.4.1.RELEASE in
> https://github.com/apache/fineract/pull/863 as part of FINERACT-963
> introduced usage of {{@Deprecated}} code, which we are trying to avoid (and
> which since FINERACT-959 we're intentionally making the build fail).
> I'm going to use a {{@SuppressWarnings("deprecation")}} to be able to do the
> upgrade anyway, because upgrading a security related library to its latest
> version seems like a sensible thing to do, but we really should remove the
> suppression and switch to using Spring's newer APIs.
> https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide
> affects {{UserDetailsApiResource}} and
> {{TwoFactorAuthenticationFilter.createUpdatedAuthentication()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1222) SDK Swagger Client Java API DefaultApi should disappear and operations go to other Api interfaces
[
https://issues.apache.org/jira/browse/FINERACT-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17280437#comment-17280437
]
Benura Abeywardena commented on FINERACT-1222:
--
[~vorburger] I would like to take up this issue
> SDK Swagger Client Java API DefaultApi should disappear and operations go to
> other Api interfaces
> -
>
> Key: FINERACT-1222
> URL: https://issues.apache.org/jira/browse/FINERACT-1222
> Project: Apache Fineract
> Issue Type: Bug
> Components: SDK
>Reporter: Michael Vorburger
>Priority: Critical
> Labels: beginner
>
> I've just noticed {{org.apache.fineract.client.services.DefaultApi}}
> containing a lot (like a 100?) of methods from {{accountsTemplate()}} to
> {{validate()}} which all look like they should belong into one of the other
> existing {{*Api}} interfaces.
> Not sure why this happens - some Swagger annotation missing?
> [~aleks] [~ChinmayKulkarni] [~ptuomola] [~manthan] any idea?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FINERACT-1222) SDK Swagger Client Java API DefaultApi should disappear and operations go to other Api interfaces
[
https://issues.apache.org/jira/browse/FINERACT-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benura Abeywardena reassigned FINERACT-1222:
Assignee: Benura Abeywardena
> SDK Swagger Client Java API DefaultApi should disappear and operations go to
> other Api interfaces
> -
>
> Key: FINERACT-1222
> URL: https://issues.apache.org/jira/browse/FINERACT-1222
> Project: Apache Fineract
> Issue Type: Bug
> Components: SDK
>Reporter: Michael Vorburger
>Assignee: Benura Abeywardena
>Priority: Critical
> Labels: beginner
>
> I've just noticed {{org.apache.fineract.client.services.DefaultApi}}
> containing a lot (like a 100?) of methods from {{accountsTemplate()}} to
> {{validate()}} which all look like they should belong into one of the other
> existing {{*Api}} interfaces.
> Not sure why this happens - some Swagger annotation missing?
> [~aleks] [~ChinmayKulkarni] [~ptuomola] [~manthan] any idea?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FINERACT-1012) Spring Security OAuth 2.x to Spring Security 5.2.x
[
https://issues.apache.org/jira/browse/FINERACT-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benura Abeywardena reassigned FINERACT-1012:
Assignee: (was: Benura Abeywardena)
> Spring Security OAuth 2.x to Spring Security 5.2.x
> --
>
> Key: FINERACT-1012
> URL: https://issues.apache.org/jira/browse/FINERACT-1012
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.4.0
>Reporter: Michael Vorburger
>Priority: Critical
> Labels: beginner
> Fix For: 1.5.0
>
>
> The bump of spring-security-oauth2 from 2.3.6.RELEASE to 2.4.1.RELEASE in
> https://github.com/apache/fineract/pull/863 as part of FINERACT-963
> introduced usage of {{@Deprecated}} code, which we are trying to avoid (and
> which since FINERACT-959 we're intentionally making the build fail).
> I'm going to use a {{@SuppressWarnings("deprecation")}} to be able to do the
> upgrade anyway, because upgrading a security related library to its latest
> version seems like a sensible thing to do, but we really should remove the
> suppression and switch to using Spring's newer APIs.
> https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide
> affects {{UserDetailsApiResource}} and
> {{TwoFactorAuthenticationFilter.createUpdatedAuthentication()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1012) Spring Security OAuth 2.x to Spring Security 5.2.x
[
https://issues.apache.org/jira/browse/FINERACT-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17280169#comment-17280169
]
Benura Abeywardena commented on FINERACT-1012:
--
[~vorburger] I'll unassigned myself from this issue. If [~vincent.fuchs] is not
active anymore I would like to take up this issue. Thanks
> Spring Security OAuth 2.x to Spring Security 5.2.x
> --
>
> Key: FINERACT-1012
> URL: https://issues.apache.org/jira/browse/FINERACT-1012
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.4.0
>Reporter: Michael Vorburger
>Assignee: Benura Abeywardena
>Priority: Critical
> Labels: beginner
> Fix For: 1.5.0
>
>
> The bump of spring-security-oauth2 from 2.3.6.RELEASE to 2.4.1.RELEASE in
> https://github.com/apache/fineract/pull/863 as part of FINERACT-963
> introduced usage of {{@Deprecated}} code, which we are trying to avoid (and
> which since FINERACT-959 we're intentionally making the build fail).
> I'm going to use a {{@SuppressWarnings("deprecation")}} to be able to do the
> upgrade anyway, because upgrading a security related library to its latest
> version seems like a sensible thing to do, but we really should remove the
> suppression and switch to using Spring's newer APIs.
> https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide
> affects {{UserDetailsApiResource}} and
> {{TwoFactorAuthenticationFilter.createUpdatedAuthentication()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FINERACT-1012) Spring Security OAuth 2.x to Spring Security 5.2.x
[
https://issues.apache.org/jira/browse/FINERACT-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benura Abeywardena reassigned FINERACT-1012:
Assignee: Benura Abeywardena
> Spring Security OAuth 2.x to Spring Security 5.2.x
> --
>
> Key: FINERACT-1012
> URL: https://issues.apache.org/jira/browse/FINERACT-1012
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.4.0
>Reporter: Michael Vorburger
>Assignee: Benura Abeywardena
>Priority: Critical
> Labels: beginner
> Fix For: 1.5.0
>
>
> The bump of spring-security-oauth2 from 2.3.6.RELEASE to 2.4.1.RELEASE in
> https://github.com/apache/fineract/pull/863 as part of FINERACT-963
> introduced usage of {{@Deprecated}} code, which we are trying to avoid (and
> which since FINERACT-959 we're intentionally making the build fail).
> I'm going to use a {{@SuppressWarnings("deprecation")}} to be able to do the
> upgrade anyway, because upgrading a security related library to its latest
> version seems like a sensible thing to do, but we really should remove the
> suppression and switch to using Spring's newer APIs.
> https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide
> affects {{UserDetailsApiResource}} and
> {{TwoFactorAuthenticationFilter.createUpdatedAuthentication()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1012) Spring Security OAuth 2.x to Spring Security 5.2.x
[
https://issues.apache.org/jira/browse/FINERACT-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17280116#comment-17280116
]
Benura Abeywardena commented on FINERACT-1012:
--
[~vorburger] Shall I work on this?
> Spring Security OAuth 2.x to Spring Security 5.2.x
> --
>
> Key: FINERACT-1012
> URL: https://issues.apache.org/jira/browse/FINERACT-1012
> Project: Apache Fineract
> Issue Type: Bug
> Components: Security
>Affects Versions: 1.4.0
>Reporter: Michael Vorburger
>Priority: Critical
> Labels: beginner
> Fix For: 1.5.0
>
>
> The bump of spring-security-oauth2 from 2.3.6.RELEASE to 2.4.1.RELEASE in
> https://github.com/apache/fineract/pull/863 as part of FINERACT-963
> introduced usage of {{@Deprecated}} code, which we are trying to avoid (and
> which since FINERACT-959 we're intentionally making the build fail).
> I'm going to use a {{@SuppressWarnings("deprecation")}} to be able to do the
> upgrade anyway, because upgrading a security related library to its latest
> version seems like a sensible thing to do, but we really should remove the
> suppression and switch to using Spring's newer APIs.
> https://github.com/spring-projects/spring-security/wiki/OAuth-2.0-Migration-Guide
> affects {{UserDetailsApiResource}} and
> {{TwoFactorAuthenticationFilter.createUpdatedAuthentication()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1291) Wrong disbursement date for loans and transaction date for savings account
[ https://issues.apache.org/jira/browse/FINERACT-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17280083#comment-17280083 ] Benura Abeywardena commented on FINERACT-1291: -- [~bgowda] Sir, can you verify this scenario? [~anmotayo] Would you mind adding the steps to reproduce this? > Wrong disbursement date for loans and transaction date for savings account > -- > > Key: FINERACT-1291 > URL: https://issues.apache.org/jira/browse/FINERACT-1291 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Anu Omotayo >Assignee: Benura Abeywardena >Priority: Blocker > Fix For: 1.2.0 > > Attachments: Mifos loan Disbursal Date Issue.png > > > We noticed that the submitted, approval and disbursal date were different > from the chosen date. We selected the current date which is 7th January 2021 > for submission, approval and disbursement, however, after submission, > approval and disbursement, the date for the following changes in the account > detail of the client to 6th January. This was tested on the link shared as > well, we got the same result. > [https://openmf.github.io/community-app/?baseApiUrl=https%3A%2F%2Fdemo.fineract.dev=default] > > We encountered the same issue for deposit and withdrawal transactions on > savings accounts. It seems the system is doing Transaction date - 1 (T - 1) > for all transactions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17280071#comment-17280071 ] Benura Abeywardena commented on FINERACT-1308: -- [~francisguchie] Would you mind adding the POST url? Need to check the api and its services which handle this request :) > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17280057#comment-17280057 ] Benura Abeywardena commented on FINERACT-1070: -- [~francisguchie] Can you change the "From" email to another gmail. Also change the email address passed to "email.addTo(emailDetails.getAddress(), emailDetails.getContactName());" method. Just replace the "emailDetails.getAddress()" with a valid gmail(Not the email you provide when creating the user). > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png, image-2021-02-06-00-17-36-048.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279365#comment-17279365 ] Benura Abeywardena edited comment on FINERACT-1070 at 2/5/21, 6:42 AM: --- [~francisguchie] Hi, I've added some changes. Please run again and check the logs whether they print the same values you passed. I've added some logs in that file. So you can run the relevant scenario and watch the FINEARCT logs to confirm the configuration values used by java email service. Please try it and attach the logs here if you get errors. Thanks! :) was (Author: blasan): [~francisguchie] Hi I've added some changes. Please run again and check the logs whether they print the same values you passed. I've added some logs in that file. So you can run the relevant scenario and watch the FINEARCT logs to confirm the configuration values used by java email service. Please try it and attach the logs here if you get errors. Thanks! :) > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279365#comment-17279365 ] Benura Abeywardena edited comment on FINERACT-1070 at 2/5/21, 6:42 AM: --- [~francisguchie] Hi, I've added some changes. Please run again and check the logs whether they are going to print the same values you passed. I've added some logs in that file. So you can run the relevant scenario and watch the FINEARCT logs to confirm the configuration values used by java email service. Please try it and attach the logs here if you get errors. Thanks! :) was (Author: blasan): [~francisguchie] Hi, I've added some changes. Please run again and check the logs whether they print the same values you passed. I've added some logs in that file. So you can run the relevant scenario and watch the FINEARCT logs to confirm the configuration values used by java email service. Please try it and attach the logs here if you get errors. Thanks! :) > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17278994#comment-17278994 ] Benura Abeywardena commented on FINERACT-1070: -- I think we need to check the logs whether the required parameters are passing properly to the email sending function. I'll check this by tomorrow and give you an update > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17278994#comment-17278994 ] Benura Abeywardena edited comment on FINERACT-1070 at 2/4/21, 5:27 PM: --- [~francisguchie] I think we need to check the logs whether the required parameters are passing properly to the email sending function. I'll check this by tomorrow and give you an update was (Author: blasan): I think we need to check the logs whether the required parameters are passing properly to the email sending function. I'll check this by tomorrow and give you an update > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1309) Back Dated Transactions
[ https://issues.apache.org/jira/browse/FINERACT-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17277043#comment-17277043 ] Benura Abeywardena commented on FINERACT-1309: -- [~francisguchie] So basically you're saying that there's an issue with the conversion of date to timestamp in FIENRACT server right? > Back Dated Transactions > --- > > Key: FINERACT-1309 > URL: https://issues.apache.org/jira/browse/FINERACT-1309 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.5.0 >Reporter: Francis Guchie >Priority: Major > > When a user makes a transaction on a particular date, the created date is the > correct timestamp yet the created or transaction or submitted on dates are > set a day before -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17276976#comment-17276976 ] Benura Abeywardena commented on FINERACT-1308: -- [~francisguchie] Great!!! > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17276433#comment-17276433 ] Benura Abeywardena edited comment on FINERACT-1308 at 2/1/21, 4:31 PM: --- [~francisguchie] Yuh, I'll pick up this issue :) And what happened with the email issue ? was (Author: blasan): [~francisguchie] Yuh, I'll pick up this issue :) And what happened in the email issue ? > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17276433#comment-17276433 ] Benura Abeywardena commented on FINERACT-1308: -- [~francisguchie] Yuh, I'll pick up this issue :) And what happened in the email issue ? > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1308) Advance Accounting Rule is not being reflected in transactions
[ https://issues.apache.org/jira/browse/FINERACT-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reassigned FINERACT-1308: Assignee: Benura Abeywardena > Advance Accounting Rule is not being reflected in transactions > -- > > Key: FINERACT-1308 > URL: https://issues.apache.org/jira/browse/FINERACT-1308 > Project: Apache Fineract > Issue Type: Bug > Components: Loan, Savings >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Major > Attachments: image-2021-02-01-15-46-58-471.png > > > Take an example of the image below of a configuration where the advanced > accounting rule has been set on a loan / savings product ( i think this > applies for all other products - but have not tested it yet. > When you take a dive of the browsers console, the *paymentTypeId* in the json > message body clearly shows that the correct id is being sent in the POST > request, However, fineract is defaulting to using the default FUND SOURCE in > this case its *"CASH BOOK"* > !image-2021-02-01-15-46-58-471.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17276411#comment-17276411 ] Benura Abeywardena commented on FINERACT-1070: -- [~francisguchie] Great. Please comment the exceptions if you get :) > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1289) Tax component not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17275813#comment-17275813 ] Benura Abeywardena commented on FINERACT-1289: -- [~bgowda] Sir can you specify the exact path where the error occurs? > Tax component not working as expected > - > > Key: FINERACT-1289 > URL: https://issues.apache.org/jira/browse/FINERACT-1289 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges >Affects Versions: 1.4.0 >Reporter: bharath gowda >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.5.0 > > Attachments: loan charge config.png, loan charge split not > happening.png, loan product config -1.png, loan product config -2.png, tax > component config.jpeg, tax group config.png > > > tax attached to the loan charge is not getting affected at the > loan/accounting level > To reproduce > 1. Create a tax component-> create a tax group with the component created. > 2. Create loan charge(any parameter, refer to the attachment for the > parameters I used) and map the tax group created. > 3. Add the charge to the loan product (with periodic accrual accounting) > enabled > 4. create/approve/disburse a loan from that loan product. > 5. Ideally the charge with the tax attached should have JE splits for charge > amount and tax amount separated. > But the tax bifurcation is not happening > > Have attached > product config screenshot, charge config screenshot, tax config screenshot, > and loan issue screenshot for more understanding > Please add a comment if you need any help > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reassigned FINERACT-1070: Assignee: Benura Abeywardena (was: Michael Vorburger) > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Benura Abeywardena >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17275487#comment-17275487 ] Benura Abeywardena edited comment on FINERACT-1070 at 1/30/21, 5:52 AM: [~francisguchie] Hi, Could you please try out the changes made in [PR-1597|https://github.com/apache/fineract/pull/1597] was (Author: blasan): [~francisguchie] Hi, Could you please try the changes made in [PR-1597|https://github.com/apache/fineract/pull/1597] > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Michael Vorburger >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17275487#comment-17275487 ] Benura Abeywardena edited comment on FINERACT-1070 at 1/30/21, 5:51 AM: [~francisguchie] Hi, Could you please try the changes made in [PR-1597|https://github.com/apache/fineract/pull/1597] was (Author: blasan): [~francisguchie] Could you please try the changes made in [PR-1597|https://github.com/apache/fineract/pull/1597] > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Michael Vorburger >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17275487#comment-17275487 ] Benura Abeywardena commented on FINERACT-1070: -- [~francisguchie] Could you please try the changes made in [PR-1597|https://github.com/apache/fineract/pull/1597] > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Michael Vorburger >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274521#comment-17274521 ] Benura Abeywardena commented on FINERACT-1070: -- [~francisguchie] I'll check this out > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Michael Vorburger >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274426#comment-17274426 ] Benura Abeywardena commented on FINERACT-1070: -- [~francisguchie] Yuh, then it's definitely with the implementation. I think you are very close to it. Did you try by changing the if conditions as you mentioned? > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Michael Vorburger >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[
https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274411#comment-17274411
]
Benura Abeywardena commented on FINERACT-1070:
--
[~francisguchie] Were you able to send the email by running the following
command instead of using the FINERACT server?**
{code:java}
echo -e 'Subject: test\n\nTesting ssmtp configs for 465 n 587' | sendmail -v
u...@gmail.com{code}
> Email Service Configurations defaults to port 25 irrespective of Port number
> specified
> --
>
> Key: FINERACT-1070
> URL: https://issues.apache.org/jira/browse/FINERACT-1070
> Project: Apache Fineract
> Issue Type: Bug
> Components: User Management
>Affects Versions: 1.4.0
>Reporter: Francis Guchie
>Assignee: Michael Vorburger
>Priority: Critical
> Fix For: 1.5.0
>
> Attachments: email Service Configurations.png,
> image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png,
> image-2020-12-12-17-36-26-558.png
>
>
> Even if use sets the following, MifosX will not send emails
> 1- Configure the server on which mifos is installed to be able to send Emails
> - One can do this by installing sSMTP on the server and testing email sending
> on the command line
> 2- if using a gmail address only ports 465 and 587 will work because port 25
> is by default disabled on google servers This includes very many other VPS /
> Mail servers
> 3- Configure the port under the Email External Services Configuration
> one will still get the error below
> 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18]
> com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException
> The RuntimeException could not be mapped to a response, re-throwing to the
> HTTP container
>
> org.apache.fineract.infrastructure.core.service.PlatformEmailSendException:
> org.apache.commons.mail.EmailException:
> Sending the email to the following server failed : smtp.gmail.com:25
> at
> org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274397#comment-17274397 ] Benura Abeywardena edited comment on FINERACT-1070 at 1/29/21, 12:26 PM: - [~francisguchie] Yuh would like to give a try :) was (Author: blasan): [~francisguchie] Yuh would like to take a look :) > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Michael Vorburger >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274397#comment-17274397 ] Benura Abeywardena commented on FINERACT-1070: -- [~francisguchie] Yuh would like to take a look :) > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Michael Vorburger >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-1070) Email Service Configurations defaults to port 25 irrespective of Port number specified
[ https://issues.apache.org/jira/browse/FINERACT-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17274390#comment-17274390 ] Benura Abeywardena commented on FINERACT-1070: -- [~vorburger] Is this issue been resolved sir? > Email Service Configurations defaults to port 25 irrespective of Port number > specified > -- > > Key: FINERACT-1070 > URL: https://issues.apache.org/jira/browse/FINERACT-1070 > Project: Apache Fineract > Issue Type: Bug > Components: User Management >Affects Versions: 1.4.0 >Reporter: Francis Guchie >Assignee: Michael Vorburger >Priority: Critical > Fix For: 1.5.0 > > Attachments: email Service Configurations.png, > image-2020-10-15-11-17-57-324.png, image-2020-12-02-11-56-01-572.png, > image-2020-12-12-17-36-26-558.png > > > Even if use sets the following, MifosX will not send emails > 1- Configure the server on which mifos is installed to be able to send Emails > - One can do this by installing sSMTP on the server and testing email sending > on the command line > 2- if using a gmail address only ports 465 and 587 will work because port 25 > is by default disabled on google servers This includes very many other VPS / > Mail servers > 3- Configure the port under the Email External Services Configuration > one will still get the error below > 03-Jul-2020 19:59:41.251 SEVERE [https-jsse-nio-443-exec-18] > com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException > The RuntimeException could not be mapped to a response, re-throwing to the > HTTP container > > org.apache.fineract.infrastructure.core.service.PlatformEmailSendException: > org.apache.commons.mail.EmailException: > Sending the email to the following server failed : smtp.gmail.com:25 > at > org.apache.fineract.infrastructure.core.service.GmailBackedPlatformEmailService.sendDefinedEmail(GmailBackedPlatformEmailService.java:81) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-1300) Needs to add init-container to check MYSQL server is up and running for Fineract server
[ https://issues.apache.org/jira/browse/FINERACT-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena closed FINERACT-1300. Merged to develop branch > Needs to add init-container to check MYSQL server is up and running for > Fineract server > --- > > Key: FINERACT-1300 > URL: https://issues.apache.org/jira/browse/FINERACT-1300 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Labels: features > Fix For: 1.5.0 > > > As Fineract-cn server accesses MYSQL container for storing MYSQL related > data, it's better to add an init-container to check whether MYSQL server is > up and running. By doing this we can reduce (barely stop) the number of > restarts done by the Fineract container -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1292) Needs to add ReadinessProbe for MySql pod
[ https://issues.apache.org/jira/browse/FINERACT-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena resolved FINERACT-1292. -- Resolution: Fixed > Needs to add ReadinessProbe for MySql pod > - > > Key: FINERACT-1292 > URL: https://issues.apache.org/jira/browse/FINERACT-1292 > Project: Apache Fineract > Issue Type: Task >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > In mysql deployment it's better to add ReadinessProbe which tells when the > container will be available for accepting traffic. This can be achieved by > using a command like `mysqladmin ping -u -p` to check whether > a mysql user has been properly created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-1292) Needs to add ReadinessProbe for MySql pod
[ https://issues.apache.org/jira/browse/FINERACT-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena closed FINERACT-1292. Merged to develop branch > Needs to add ReadinessProbe for MySql pod > - > > Key: FINERACT-1292 > URL: https://issues.apache.org/jira/browse/FINERACT-1292 > Project: Apache Fineract > Issue Type: Task >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > In mysql deployment it's better to add ReadinessProbe which tells when the > container will be available for accepting traffic. This can be achieved by > using a command like `mysqladmin ping -u -p` to check whether > a mysql user has been properly created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1300) Needs to add init-container to check MYSQL server is up and running for Fineract server
[ https://issues.apache.org/jira/browse/FINERACT-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena resolved FINERACT-1300. -- Resolution: Fixed > Needs to add init-container to check MYSQL server is up and running for > Fineract server > --- > > Key: FINERACT-1300 > URL: https://issues.apache.org/jira/browse/FINERACT-1300 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Labels: features > Fix For: 1.5.0 > > > As Fineract-cn server accesses MYSQL container for storing MYSQL related > data, it's better to add an init-container to check whether MYSQL server is > up and running. By doing this we can reduce (barely stop) the number of > restarts done by the Fineract container -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1301) Need to add resource limitations to fineract & mysql deployments
[ https://issues.apache.org/jira/browse/FINERACT-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena resolved FINERACT-1301. -- Resolution: Fixed > Need to add resource limitations to fineract & mysql deployments > > > Key: FINERACT-1301 > URL: https://issues.apache.org/jira/browse/FINERACT-1301 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Major > Labels: features > Fix For: 1.5.0 > > > It's better to add resource limitations for the deployments so it will > prevent over consumption of cluster resources -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1289) Tax component not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reassigned FINERACT-1289: Assignee: Benura Abeywardena > Tax component not working as expected > - > > Key: FINERACT-1289 > URL: https://issues.apache.org/jira/browse/FINERACT-1289 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges >Affects Versions: 1.4.0 >Reporter: bharath gowda >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.5.0 > > Attachments: loan charge config.png, loan charge split not > happening.png, loan product config -1.png, loan product config -2.png, tax > component config.jpeg, tax group config.png > > > tax attached to the loan charge is not getting affected at the > loan/accounting level > To reproduce > 1. Create a tax component-> create a tax group with the component created. > 2. Create loan charge(any parameter, refer to the attachment for the > parameters I used) and map the tax group created. > 3. Add the charge to the loan product (with periodic accrual accounting) > enabled > 4. create/approve/disburse a loan from that loan product. > 5. Ideally the charge with the tax attached should have JE splits for charge > amount and tax amount separated. > But the tax bifurcation is not happening > > Have attached > product config screenshot, charge config screenshot, tax config screenshot, > and loan issue screenshot for more understanding > Please add a comment if you need any help > -- This message was sent by Atlassian Jira (v8.3.4#803005)
