[jira] [Commented] (FINERACT-380) S3 permission issue -- add system property

[Shaik Nazeer Hussain (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827534#comment-15827534
 ] 

Shaik Nazeer Hussain commented on FINERACT-380:
---

AWS support ticket is raised as we are getting the following exception for 
region Regions.AP_NORTHEAST_2
Java Exception: com.amazonaws.services.s3.model.AmazonS3Exception: Access 
Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request 
ID: x), S3 Extended Request ID: xx

> S3 permission issue -- add system property
> --
>
> Key: FINERACT-380
> URL: https://issues.apache.org/jira/browse/FINERACT-380
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: thynn win
>Assignee: Shaik Nazeer Hussain
>Priority: Critical
>  Labels: p1
>
> Due to signature version 4 issue, I am unable to use S3 with Mifos.
> Amazon suggested we add a system property and could you please help us add 
> this in the next version?
> AWS Error Code: InvalidRequest, AWS Error Message: The authorization 
> mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Stretch Parameter -groupId

[Sampath Kumar G]

Hi Zayyad,

Please find the attachment, insert script for the group as a parameter.

Thanks and regards,
Sampath


​
*Conflux Technologies Pvt Ltd  *

#304, 2nd Floor, 7th Main Road

HRBR Layout 1st Block

Bengaluru, Karnataka, 560043 INDIA


Disclaimer: The information contained in this e-mail message and any
files/attachment transmitted with it is confidential and for the sole use
of the intended recipient(s) or entity identified. If you are not the
intended recipient, please email: supp...@confluxtechnologies.com and
destroy/delete all copies and attachment thereto along with the original
message. Any unauthorised review, use, disclosure, dissemination,
forwarding, printing or copying of this email or any action taken in
reliance on this e-mail is strictly prohibited and is unlawful. The
recipient acknowledges that Conflux Technologies Private Limited or its
subsidiaries and associated companies are unable to exercise control or
ensure or guarantee the integrity of/over the contents of the information
contained in e-mail transmissions. Before opening any attachments, please
check.

On Tue, Jan 17, 2017 at 7:38 PM, Zayyad A. Said <
zay...@intrasofttechnologies.com> wrote:

> Devs,
>
>
>
> I am trying to develop a report which contains groups.
>
>
>
> I need to set Group as parameter to pass to Pentaho as we need report per
> group.
>
>
>
> I don’t see groupId in the table stretchy_parameter, how then can I use
> Group as parameter in my report?
>
>
>
> Kindly but urgently advise on this.
>
>
>
> Thanks & Regards;
>
>
>
>
>
> *
>
> *Zayyad A. Said | Chairman & C.E.O*
>
>
>
> Cell No.: +254 716 615274 | Skype: *zsaid2011*
>
> Email: zay...@intrasofttechnologies.com
>
>
>
> [image: Email banner]
>
>
>

Stretch Parameter -groupId

[Zayyad A. Said]

Devs,

 

I am trying to develop a report which contains groups.

 

I need to set Group as parameter to pass to Pentaho as we need report per
group.

 

I don't see groupId in the table stretchy_parameter, how then can I use
Group as parameter in my report?

 

Kindly but urgently advise on this.

 

Thanks & Regards;

 

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email:  
zay...@intrasofttechnologies.com 

 

Email banner

 

[jira] [Commented] (FINERACT-235) For flat loan with variable installment, foreclosure before first repayment date is collecting full month interest

[Edward Cable (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826092#comment-15826092
 ] 

Edward Cable commented on FINERACT-235:
---

Requirements will be discussed with [~binnygopinath]

> For flat loan with variable installment, foreclosure before first repayment 
> date is collecting full month interest
> --
>
> Key: FINERACT-235
> URL: https://issues.apache.org/jira/browse/FINERACT-235
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
>
> 1. Create loan product with following datasets
> Principal: 1,
> ROI: 12% pa
> Loan term 12 months,
> Repaid every: 1 month,
> Amortization: Equal Installments
> Interest method: Flat
> Variable installment checked.
> 2. Submit new loan application on 01 January 2016, expected disbursement date 
> 01 January 2016.
> 3. Edit repayment schedule and change first repayment date from 01 February 
> 2016 to 15 January 2016.
> 4. Disburse loan on 15 January 2016.
> Foreclose loan on same date.
> Expected result:
> It should not collect any interest if the foreclosed date is same as 
> disbursement date.
> Actual result:
> It is collecting one month interest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-235) For flat loan with variable installment, foreclosure before first repayment date is collecting full month interest

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-235:
--
Labels: confirm p2  (was: confirm)

> For flat loan with variable installment, foreclosure before first repayment 
> date is collecting full month interest
> --
>
> Key: FINERACT-235
> URL: https://issues.apache.org/jira/browse/FINERACT-235
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
>
> 1. Create loan product with following datasets
> Principal: 1,
> ROI: 12% pa
> Loan term 12 months,
> Repaid every: 1 month,
> Amortization: Equal Installments
> Interest method: Flat
> Variable installment checked.
> 2. Submit new loan application on 01 January 2016, expected disbursement date 
> 01 January 2016.
> 3. Edit repayment schedule and change first repayment date from 01 February 
> 2016 to 15 January 2016.
> 4. Disburse loan on 15 January 2016.
> Foreclose loan on same date.
> Expected result:
> It should not collect any interest if the foreclosed date is same as 
> disbursement date.
> Actual result:
> It is collecting one month interest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-235) For flat loan with variable installment, foreclosure before first repayment date is collecting full month interest

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-235:
--
Labels: confirm  (was: )

> For flat loan with variable installment, foreclosure before first repayment 
> date is collecting full month interest
> --
>
> Key: FINERACT-235
> URL: https://issues.apache.org/jira/browse/FINERACT-235
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
>
> 1. Create loan product with following datasets
> Principal: 1,
> ROI: 12% pa
> Loan term 12 months,
> Repaid every: 1 month,
> Amortization: Equal Installments
> Interest method: Flat
> Variable installment checked.
> 2. Submit new loan application on 01 January 2016, expected disbursement date 
> 01 January 2016.
> 3. Edit repayment schedule and change first repayment date from 01 February 
> 2016 to 15 January 2016.
> 4. Disburse loan on 15 January 2016.
> Foreclose loan on same date.
> Expected result:
> It should not collect any interest if the foreclosed date is same as 
> disbursement date.
> Actual result:
> It is collecting one month interest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-235) For flat loan with variable installment, foreclosure before first repayment date is collecting full month interest

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-235:
--
Summary: For flat loan with variable installment, foreclosure before first 
repayment date is collecting full month interest  (was: For flat loan with 
variable instllment, foreclosure before first repayment date is collecting full 
month interest)

> For flat loan with variable installment, foreclosure before first repayment 
> date is collecting full month interest
> --
>
> Key: FINERACT-235
> URL: https://issues.apache.org/jira/browse/FINERACT-235
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>
> 1. Create loan product with following datasets
> Principal: 1,
> ROI: 12% pa
> Loan term 12 months,
> Repaid every: 1 month,
> Amortization: Equal Installments
> Interest method: Flat
> Variable installment checked.
> 2. Submit new loan application on 01 January 2016, expected disbursement date 
> 01 January 2016.
> 3. Edit repayment schedule and change first repayment date from 01 February 
> 2016 to 15 January 2016.
> 4. Disburse loan on 15 January 2016.
> Foreclose loan on same date.
> Expected result:
> It should not collect any interest if the foreclosed date is same as 
> disbursement date.
> Actual result:
> It is collecting one month interest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-234) Can't process bulk JLG loan application [MIFOSX-2137]

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-234:
--
Labels: p1  (was: )

> Can't process bulk JLG loan application [MIFOSX-2137]
> -
>
> Key: FINERACT-234
> URL: https://issues.apache.org/jira/browse/FINERACT-234
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>  Labels: p1
>
> Moved over from https://mifosforge.jira.com/browse/MIFOSX-2137
> I still am unable to save new bulk JLG loan applications even when the 
> meeting frequency matches so it seems like this is still not working.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-230) After Waive interest the installment amount is displaying with the previous amount (before waive installment) in collection sheet

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-230:
--
Labels: p2  (was: )

> After Waive interest the installment amount is displaying with the previous 
> amount (before waive installment) in collection sheet
> -
>
> Key: FINERACT-230
> URL: https://issues.apache.org/jira/browse/FINERACT-230
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p2
>
> 1. Create a loan product, Create a Center and attache Group to it, Attache 
> weekly meeting from 01 June 2016 on friday.
> 2. Create a client under above group and attache JLG loan on 01 June 2016 
> with synk repayment with meeting.
> 3. Approve and disburse the loan
> 4. Waive interest on 03 June 2016.
> 5. Go to collection sheet and enter valid inputs and generate collection 
> sheet for 03 June 2016.
> > Though the interest is waived for first repayment it is still displaying 
> > the previous amount(Before waive).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-221) After submitting the modify application the currency is not getting updated as per the new product

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-221:
--
Labels: confirm p1  (was: )

> After submitting the modify application the currency is not getting updated 
> as per the new product
> --
>
> Key: FINERACT-221
> URL: https://issues.apache.org/jira/browse/FINERACT-221
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> 1. Create 2 loan products, one with Indian rupees as currency and another 
> with US Dollar
> 2. Submit new loan application for a client with the loan prouduct1.
> 3. Click on modify application and modify to product2.
> 4. In the loan general page currency is not getting updated to US Dollar, 
> rather it is remaining as Indian Rupees only.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-226) If the Center meeting date is modified before submitting JLG loan application then repayment schedule generated is not proper

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-226:
--
Labels: confirm p2  (was: )

> If the Center meeting date is modified before submitting JLG loan application 
> then repayment schedule generated is not proper
> -
>
> Key: FINERACT-226
> URL: https://issues.apache.org/jira/browse/FINERACT-226
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
> Attachments: Change center meeting date.png
>
>
> 1. Create a Center and attache meeting on 01 July 2016 with weekly on Friday, 
> Click on modify meeting and change the meeting day as Wednesday.
> 2. Create a Group under that Center and Create a Client under that group.
> 3. Submit new JLG loan application for a client on 06 July 2016. with weekly 
> loan, approve and disburse on 06 July 2016.
> 4. Click on the repayment schedule
> It is displaying first repayment entry on 08 July 2016, which was previous 
> meeting date. It should display first repayment date as from 13 July 2016



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-220) Time format entry in the datatable is accepting only hour: minute and not the second format

[Edward Cable (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826083#comment-15826083
 ] 

Edward Cable commented on FINERACT-220:
---

If support for entry of seconds is needed, can take on as enhancement. Closing 
as a bug.

> Time format entry in the datatable is accepting only hour: minute and not the 
> second format
> ---
>
> Key: FINERACT-220
> URL: https://issues.apache.org/jira/browse/FINERACT-220
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p3
> Attachments: Date and time format.png
>
>
> 1. Create the data table for a client with date and time format, 
> 2. Click on the clients and click on the datable created above and make entry 
> for date and time format, for time format enter value in 12:12:12.and click 
> on the submit button.
> > Error message displayed as bad request.
> > It is accepting only in 12:12 (HH:MM)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-220) Time format entry in the datatable is accepting only hour: minute and not the second format

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-220:
--
Labels: p3  (was: )

> Time format entry in the datatable is accepting only hour: minute and not the 
> second format
> ---
>
> Key: FINERACT-220
> URL: https://issues.apache.org/jira/browse/FINERACT-220
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p3
> Attachments: Date and time format.png
>
>
> 1. Create the data table for a client with date and time format, 
> 2. Click on the clients and click on the datable created above and make entry 
> for date and time format, for time format enter value in 12:12:12.and click 
> on the submit button.
> > Error message displayed as bad request.
> > It is accepting only in 12:12 (HH:MM)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FINERACT-220) Time format entry in the datatable is accepting only hour: minute and not the second format

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable closed FINERACT-220.
-
Resolution: Won't Fix

> Time format entry in the datatable is accepting only hour: minute and not the 
> second format
> ---
>
> Key: FINERACT-220
> URL: https://issues.apache.org/jira/browse/FINERACT-220
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p3
> Attachments: Date and time format.png
>
>
> 1. Create the data table for a client with date and time format, 
> 2. Click on the clients and click on the datable created above and make entry 
> for date and time format, for time format enter value in 12:12:12.and click 
> on the submit button.
> > Error message displayed as bad request.
> > It is accepting only in 12:12 (HH:MM)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-219) Edit Data table Entry for client, date format displayed is improper

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-219:
--
Labels: Github  (was: )

> Edit Data table Entry for client, date format displayed is improper
> ---
>
> Key: FINERACT-219
> URL: https://issues.apache.org/jira/browse/FINERACT-219
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: Github
> Attachments: Edit datable entry.png
>
>
> 1. Create data table for a client. with the data sets as mentioned in the 
> attachment,
> 2. Click on clients-> any created client -> Click on the data table created 
> -> enter the valid inputs and save the page.
> 3. Click on the edit button in the same page.
> > Date and time format displayed is not proper



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-219) Edit Data table Entry for client, date format displayed is improper

[Edward Cable (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826080#comment-15826080
 ] 

Edward Cable commented on FINERACT-219:
---

Move to GitHub Issue Tracker for Community App. 

> Edit Data table Entry for client, date format displayed is improper
> ---
>
> Key: FINERACT-219
> URL: https://issues.apache.org/jira/browse/FINERACT-219
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
> Attachments: Edit datable entry.png
>
>
> 1. Create data table for a client. with the data sets as mentioned in the 
> attachment,
> 2. Click on clients-> any created client -> Click on the data table created 
> -> enter the valid inputs and save the page.
> 3. Click on the edit button in the same page.
> > Date and time format displayed is not proper



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-213) Not able to foreclose the loan on current system date moves to Overpaid state.

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-213:
--
Labels: confirm p1  (was: )

> Not able to foreclose the loan on current system date moves to Overpaid state.
> --
>
> Key: FINERACT-213
> URL: https://issues.apache.org/jira/browse/FINERACT-213
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> 1. Create a loan product (without interest recalculation), Create a client.
> 2. Disburse loan for  a client on 01 August 2016.
> 3. Fore close the loan on current system date.
> > Loan should get closed but moving to overpaid state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-208) For multi tranche loan with variable installment, the repayment schedule generated after making repayment after 2nd tranche disbursement is not proper

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-208:
--
Labels: p2  (was: )

> For multi tranche loan with variable installment, the repayment schedule 
> generated after making repayment after 2nd tranche disbursement is not proper
> --
>
> Key: FINERACT-208
> URL: https://issues.apache.org/jira/browse/FINERACT-208
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p2
> Attachments: Variable isntallment loan.png
>
>
> 1. Create loan product with interest recalculation, Variable installment 
> enabled, multi tranche loan with tranche count as 2.
> 2. Submit new loan application for a client on 01 January 2016, first tranche 
> on same date and 2nd tranche on 01 march 2016.
> 3. After submitting the loan application, click on more and click on edit 
> repayment schedule, add another installment on 15 Feb 2016.
> 4. Approve and disburse first tranche on 01 January 2016.
> 5. Make repayment on 01 February 2016.
> 6. Disburse 2nd tranche on 01 March 2016
> 7. Make repayment on 01 March 2016
> > Click on the repayment schedule in which the interest is getting calculated 
> > wrongly on 01 March 2016.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-207) Loan prepayment fails if Installation Fee charge set

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-207:
--
Labels: confirm p1  (was: )

> Loan prepayment fails if Installation Fee charge set
> 
>
> Key: FINERACT-207
> URL: https://issues.apache.org/jira/browse/FINERACT-207
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Terence Denzil Monteiro
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> For Loan Product where Charge Time Type = Installation Fee,
> if a loan is created and modified before approval
> if I try to prepay the loan, it gives HTTP 500 response code with body:
> {"timestamp":1470637896498,"status":500,"error":"Internal Server 
> Error","exception":"java.lang.NullPointerException","message":null}
> for example, see loan #819 on demo server: 
> https://demo.openmf.org/#/loanaccount/819/prepayloan, for client #10: JAVA BOY



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-205) If the disbursement date is changed to next meeting date during loan disbursement then first repayment date is falling on disbursement date in repayment schedule

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-205:
--
Labels: p1  (was: )

> If the disbursement date is changed to next meeting date during loan 
> disbursement then first repayment date is falling on disbursement date in 
> repayment schedule
> -
>
> Key: FINERACT-205
> URL: https://issues.apache.org/jira/browse/FINERACT-205
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: JLG Loans.png
>
>
> 1. Create simple loan product.
> 2. Create a group with meeting attached, weekly every 1 week Friday, from 01 
> January 2016.
> 3. Create a client under that Group and submit new JLG loan with weekly 
> repayment on 01 January 2016, expected disbursement on 01 January 2016. 
> 4. Approve on 01 January 2016, during disbursement modify date to next 
> meeting date ie on 08 January 2016.
> > The repayment schedule should get generated such that the first repayment 
> > falls on 15 January 2016. But the first repayment falling on the date of 
> > disbursement ie on 08 January 2016.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-176) During allocation and settle cash for a cashier if valid inputs are not given then error message displayed as Unknown data integrity issue

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-176:
--
Labels: p3  (was: )

> During allocation and settle cash for a cashier if valid inputs are not given 
> then error message displayed as Unknown data integrity issue
> --
>
> Key: FINERACT-176
> URL: https://issues.apache.org/jira/browse/FINERACT-176
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p3
> Attachments: AllocationorSettle cash.png
>
>
> 1. Create teller and create a cashier for that teller.
> 2. Click on allocate/settle cash
> > Do not enter any values and click on submit button - 
> > "error.msg.teller.unknown.data.integrity.issue"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-176) During allocation and settle cash for a cashier if valid inputs are not given then error message displayed as Unknown data integrity issue

[Edward Cable (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826071#comment-15826071
 ] 

Edward Cable commented on FINERACT-176:
---

Proper error message to be added. 

> During allocation and settle cash for a cashier if valid inputs are not given 
> then error message displayed as Unknown data integrity issue
> --
>
> Key: FINERACT-176
> URL: https://issues.apache.org/jira/browse/FINERACT-176
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p3
> Attachments: AllocationorSettle cash.png
>
>
> 1. Create teller and create a cashier for that teller.
> 2. Click on allocate/settle cash
> > Do not enter any values and click on submit button - 
> > "error.msg.teller.unknown.data.integrity.issue"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-174) Can't select "Escheat Liability" account for deposit products

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-174:
--
Labels: confirm p2  (was: )

> Can't select "Escheat Liability" account for deposit products
> -
>
> Key: FINERACT-174
> URL: https://issues.apache.org/jira/browse/FINERACT-174
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
> Environment: Product Server (https://demo4.openmf.org)
>Reporter: Edward Cable
>Assignee: subramanyasn
>  Labels: confirm, p2
> Attachments: Screen Shot 2016-06-15 at 2.07.47 PM.png
>
>
> Not sure if this is a bug within Fineract or the Community App (perhaps in 
> selection of the account). 
> While attempting to test out the dormant/inactive savings account feature and 
> the ability to escheat funds after a given number of days, I was unable to 
> configure the general ledger account mapping for the Escheat Liability 
> account  for the savings product I was editing.
> To repro, log in to https://demo4.openmf.org with credentials, 
> Mifos/MifosAdmin
> Go to Products >> Savings Products >> Basic Savings Account >> Edit >> 
> Attempt to select an account for Escheat Liability (I newly created Escheated 
> Deposits).
> Click Submit
> See error message that gets displayed:
> field is required
> error.msg.productToAccountMapping.not.found



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-172) Loan with Moratorium on Interest is not collecting interest during foreclosure

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-172:
--
Labels: p3  (was: )

> Loan with  Moratorium on Interest is not collecting interest during 
> foreclosure
> ---
>
> Key: FINERACT-172
> URL: https://issues.apache.org/jira/browse/FINERACT-172
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p3
> Attachments: foreclosure loan4.png
>
>
> 1. Create a simple loan product with interest calculation as same as 
> repayment, principal 1, ROI 12% pa, repaid every 1 month, declining 
> balance, moratorium on interest as 1.
> 2. Submit new loan application for a client on 01 June 2016, approve and 
> disburse on same date.
> 3. Click on foreclosure and enter date as 15 June 2016.
> > Interest amount for the 14 days is not getting displayed in Loan 
> > foreclosure page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-166) Installment fee should not get collected if the prepay of loan is done before first repayment

[Edward Cable (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826069#comment-15826069
 ] 

Edward Cable commented on FINERACT-166:
---

More details to be added. 

> Installment fee should not get collected if the prepay of loan is done before 
> first repayment
> -
>
> Key: FINERACT-166
> URL: https://issues.apache.org/jira/browse/FINERACT-166
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges, Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p2
>
> 1. Create a loan product with interest recalculation and with installment fee 
> attached. 
> 2. Submit new loan application for a client on 01 Jan 2015. Approve and 
> disburse on same date.
> 3. Prepay the loan on 15 Jan 2015, in prepay loan page the amount displayed 
> is including the charge. but loan get closed. 
> > the charge amount should not get collected in prepay page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-166) Installment fee should not get collected if the prepay of loan is done before first repayment

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-166:
--
Labels: p2  (was: )

> Installment fee should not get collected if the prepay of loan is done before 
> first repayment
> -
>
> Key: FINERACT-166
> URL: https://issues.apache.org/jira/browse/FINERACT-166
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges, Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p2
>
> 1. Create a loan product with interest recalculation and with installment fee 
> attached. 
> 2. Submit new loan application for a client on 01 Jan 2015. Approve and 
> disburse on same date.
> 3. Prepay the loan on 15 Jan 2015, in prepay loan page the amount displayed 
> is including the charge. but loan get closed. 
> > the charge amount should not get collected in prepay page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-165) Not able to Prepay loan after waive charge/Penalty

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-165:
--
Labels: p2  (was: )

> Not able to Prepay loan after waive charge/Penalty
> --
>
> Key: FINERACT-165
> URL: https://issues.apache.org/jira/browse/FINERACT-165
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges, Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p2
>
> 1. Create a loan product with interest recalculation, specified due date 
> charge attached.
> 2. Submit new loan application for a client on 01 Jan 2015, add specified due 
> date charge on 14 Jan 2015, approve and disburse the loan.
> 3. Waive charge applied above.
> 4. Click on prepay and make prepay on 15 Jan 2015.
> > Prepay loan page the amount displayed is not proper also after prepay the 
> > loan will not move to closed state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-164) tranche change is not recalculating interest for the installments before the new tranche date.

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-164:
--
Labels: confirm p1  (was: )

> tranche change is not recalculating interest for the installments before the 
> new tranche date.
> --
>
> Key: FINERACT-164
> URL: https://issues.apache.org/jira/browse/FINERACT-164
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Sachin Kulkarni
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: after.png, before.png
>
>
> tranche change is not recalculating interest for the installments before the 
> new tranche date.
> for example refer the attached 
> (the loan is 2 tranche loans with 1st tranche disbursed)
> in the attachment 2nd tranche was on 14th june
> so the installment had the interest computed based on 14th tranche 
> principle(Refer "before" screenshot)
> later i will change the tranche date from 14th june to 27th july.
> at this time all the installments from 14th june to 27th july interest will 
> be same as before.(Refer "after" screenshot)
> it should have been recomputed this interest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-161) Not able to disburse 2nd tranche after the account closure date with periodic accrual done

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-161:
--
Labels: p2  (was: )

> Not able to disburse 2nd tranche after the account closure date with periodic 
> accrual done
> --
>
> Key: FINERACT-161
> URL: https://issues.apache.org/jira/browse/FINERACT-161
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p2
>
> 1. Create a loan product with following datasets,
> Repayment Strategy:Overdue/Due Fee/Int,Principal
> Repayments:12 every 1 Months on
> Amortization:Equal installments
> Interest:12 per annum (1% Per month) - Declining Balance
> Interest Calculation Period:Daily
> Interest Type:Declining Balance
> Recalculate Interest:Yes
> Days in year:Actual
> Days in month:Actual
> Interest recalculation compounding on:None
> Advance payments adjustment type:Reduce number of installments
> Frequency for recalculate Outstanding Principal:Every -1 days.
> 2. Submit new loan application for a client on 01 January 2015 with 1st 
> tranche on same date and 2nd tranche on 01 March 2015.
> 3. Disburse 1st tranche on 01 January 2015.
> 4. Run periodic accrual on 15 February 2015 and account closure on 15 
> February 2015.
> 5. Disburse 2nd tranche on 20 February 2015.
> > Should allow to disburse 2nd tranche on 20 February 2015.
> not allowing to disburse displays error message "error.msg.accrual.exception"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-159) Not able to disburse the loan after deleting the first three installments in variable installments

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-159:
--
Labels: confirm p1  (was: p1)

> Not able to disburse the loan after deleting the first three installments in 
> variable installments
> --
>
> Key: FINERACT-159
> URL: https://issues.apache.org/jira/browse/FINERACT-159
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
> Attachments: After disbursement1.png
>
>
> 1. Create loan product with following datasets
> Repayment Strategy: Overdue/Due Fee/Int,Principal
> Repayments: 12 every 1 Months on
> Amortization: Equal installments
> Interest: 12 per annum (1% Per month) - Declining Balance
> Grace: On Principal Payment
> Grace: On Interest Payment
> Interest Calculation Period: Daily
> Interest Type: Declining Balance
> Recalculate Interest: Yes
> Days in year: Actual
> Days in month: Actual
> Interest recalculation compounding on: None
> Advance payments adjustment type: Reduce EMI amount
> Frequency for recalculate Outstanding Principal: Daily.
> 2. Submit new loan application for a client on 01 January 2016, and amount as 
> 1.
> 3.Click on more and click on edit repayment schedule. and delete first 3 
> repayments.
> 4. Approve and click on disburse the loan, in loan disbursement page enter 
> valid inputs and click on submit button.
> > Navigated page doesnot contain any loan information rather displays with 
> > out any entries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-159) Not able to disburse the loan after deleting the first three installments in variable installments

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-159:
--
Labels: p1  (was: )

> Not able to disburse the loan after deleting the first three installments in 
> variable installments
> --
>
> Key: FINERACT-159
> URL: https://issues.apache.org/jira/browse/FINERACT-159
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
> Attachments: After disbursement1.png
>
>
> 1. Create loan product with following datasets
> Repayment Strategy: Overdue/Due Fee/Int,Principal
> Repayments: 12 every 1 Months on
> Amortization: Equal installments
> Interest: 12 per annum (1% Per month) - Declining Balance
> Grace: On Principal Payment
> Grace: On Interest Payment
> Interest Calculation Period: Daily
> Interest Type: Declining Balance
> Recalculate Interest: Yes
> Days in year: Actual
> Days in month: Actual
> Interest recalculation compounding on: None
> Advance payments adjustment type: Reduce EMI amount
> Frequency for recalculate Outstanding Principal: Daily.
> 2. Submit new loan application for a client on 01 January 2016, and amount as 
> 1.
> 3.Click on more and click on edit repayment schedule. and delete first 3 
> repayments.
> 4. Approve and click on disburse the loan, in loan disbursement page enter 
> valid inputs and click on submit button.
> > Navigated page doesnot contain any loan information rather displays with 
> > out any entries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-159) Not able to disburse the loan after deleting the first three installments in variable installments

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-159:
--
Labels: confirm p2  (was: confirm p1)

> Not able to disburse the loan after deleting the first three installments in 
> variable installments
> --
>
> Key: FINERACT-159
> URL: https://issues.apache.org/jira/browse/FINERACT-159
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
> Attachments: After disbursement1.png
>
>
> 1. Create loan product with following datasets
> Repayment Strategy: Overdue/Due Fee/Int,Principal
> Repayments: 12 every 1 Months on
> Amortization: Equal installments
> Interest: 12 per annum (1% Per month) - Declining Balance
> Grace: On Principal Payment
> Grace: On Interest Payment
> Interest Calculation Period: Daily
> Interest Type: Declining Balance
> Recalculate Interest: Yes
> Days in year: Actual
> Days in month: Actual
> Interest recalculation compounding on: None
> Advance payments adjustment type: Reduce EMI amount
> Frequency for recalculate Outstanding Principal: Daily.
> 2. Submit new loan application for a client on 01 January 2016, and amount as 
> 1.
> 3.Click on more and click on edit repayment schedule. and delete first 3 
> repayments.
> 4. Approve and click on disburse the loan, in loan disbursement page enter 
> valid inputs and click on submit button.
> > Navigated page doesnot contain any loan information rather displays with 
> > out any entries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-158) Prepay loan with installment fee attached will go to the overpaid state than getting closed

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-158:
--
Labels: p1  (was: )

> Prepay loan with installment fee attached will go to the overpaid state than 
> getting closed
> ---
>
> Key: FINERACT-158
> URL: https://issues.apache.org/jira/browse/FINERACT-158
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: Overpaid state of loan.png
>
>
> 1. Create loan product with following datasets
> Repayment Strategy: Overdue/Due Fee/Int,Principal
> Repayments: 12 every 1 Months on  
> Amortization: Equal installments
> Interest: 12 per annum (1%  Per month) - Declining Balance
> Grace: On Principal Payment   
> Grace: On Interest Payment
> Interest Calculation Period: Same as repayment period
> Interest Type:Declining Balance
> Recalculate Interest: Yes
> Days in year: Actual
> Days in month: Actual
> Interest recalculation compounding on: None
> Advance payments adjustment type: Reduce EMI amount
> Frequency for recalculate Outstanding Principal: Same as repayment period.
> 2. Submit new loan application for a client on 01 March 2016 with installment 
> fee attached (Installment fee - Flat- 100). Approve and disburse on same date.
> 3. Click on Prepay loan and make prepayment on current system date.
> 4. Loan is going to overpaid state than moving to closed state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-156) After Waive specified due date charge (penalty) repayment schedule generated is not proper

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-156:
--
Labels: p1  (was: )

> After Waive specified due date charge (penalty) repayment schedule generated 
> is not proper
> --
>
> Key: FINERACT-156
> URL: https://issues.apache.org/jira/browse/FINERACT-156
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges, Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: Waive specified due date penalty.png
>
>
> 1. Create a loan product with following datasets,
> Repayment Strategy:Overdue/Due Fee/Int,Principal
> Repayments:12 every 1 Months on  
> Amortization:Equal installments
> Interest:12 per annum (1%  Per month) - Declining Balance
> Interest Calculation Period:Daily
> Interest Type:Declining Balance
> Recalculate Interest:Yes
> Days in year:Actual
> Days in month:Actual
> Interest recalculation compounding on:None
> Advance payments adjustment type:Reduce number of installments
> Frequency for recalculate Outstanding Principal:Every -1 days
> 2. Submit new loan application for a client on 01 Jan 2016, add specified due 
> date charge (created as penalty Flat 100) on 15 Jan 2016.
> 3.Approve and disburse the loan on 01 Jan 2016.
> 4. Click on Charges and Waive the charge applied.
> 5. Click on the repayment schedule in which the first repayment is got 
> modified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-156) After Waive specified due date charge (penalty) repayment schedule generated is not proper

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-156:
--
Component/s: Charges

> After Waive specified due date charge (penalty) repayment schedule generated 
> is not proper
> --
>
> Key: FINERACT-156
> URL: https://issues.apache.org/jira/browse/FINERACT-156
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges, Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
> Attachments: Waive specified due date penalty.png
>
>
> 1. Create a loan product with following datasets,
> Repayment Strategy:Overdue/Due Fee/Int,Principal
> Repayments:12 every 1 Months on  
> Amortization:Equal installments
> Interest:12 per annum (1%  Per month) - Declining Balance
> Interest Calculation Period:Daily
> Interest Type:Declining Balance
> Recalculate Interest:Yes
> Days in year:Actual
> Days in month:Actual
> Interest recalculation compounding on:None
> Advance payments adjustment type:Reduce number of installments
> Frequency for recalculate Outstanding Principal:Every -1 days
> 2. Submit new loan application for a client on 01 Jan 2016, add specified due 
> date charge (created as penalty Flat 100) on 15 Jan 2016.
> 3.Approve and disburse the loan on 01 Jan 2016.
> 4. Click on Charges and Waive the charge applied.
> 5. Click on the repayment schedule in which the first repayment is got 
> modified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-146) In Demo version loans awaiting for approval is not getting displayed properly under Checker in box and tasks

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-146:
--
Labels: p1  (was: )

> In Demo version loans awaiting for approval is not getting displayed properly 
> under Checker in box and tasks
> 
>
> Key: FINERACT-146
> URL: https://issues.apache.org/jira/browse/FINERACT-146
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: Mifos X Client 2016-04-29 04-17-41.png, Mifos X Client 
> 2016-04-29 04-19-11.png
>
>
> In demo version after clicking on the checker inbox and tasks, the recently 
> submitted loan awaiting for approval is not getting displayed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-142) In loan "Account Detail" page the maturity date is displayed is not proper

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-142:
--
Labels: confirm p2  (was: confirm)

> In loan "Account Detail" page the maturity date is displayed is not proper
> --
>
> Key: FINERACT-142
> URL: https://issues.apache.org/jira/browse/FINERACT-142
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
> Attachments: Maturity date.png
>
>
> 1. Create a loan product with interest recalculation enabled (Interest 
> calculation - daily and recalculation -daily). monthly repayment.
> 2. Submit new loan application for a client on 01 Jan 2015. Approve and 
> disburse loan on same date.
> 3. Click on the repayment schedule in which the new row with the  interest 
> accrued till current date is displayed.
> 4. Click on the Account detail page in which the loan maturity date is 
> displayed as today's system date.
> Expected:
> The loan maturity date should not get modified due to the new row created 
> with the interest accrued till current system date. It should be as per 
> original schedule.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-142) In loan "Account Detail" page the maturity date is displayed is not proper

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-142:
--
Labels: confirm  (was: )

> In loan "Account Detail" page the maturity date is displayed is not proper
> --
>
> Key: FINERACT-142
> URL: https://issues.apache.org/jira/browse/FINERACT-142
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm
> Attachments: Maturity date.png
>
>
> 1. Create a loan product with interest recalculation enabled (Interest 
> calculation - daily and recalculation -daily). monthly repayment.
> 2. Submit new loan application for a client on 01 Jan 2015. Approve and 
> disburse loan on same date.
> 3. Click on the repayment schedule in which the new row with the  interest 
> accrued till current date is displayed.
> 4. Click on the Account detail page in which the loan maturity date is 
> displayed as today's system date.
> Expected:
> The loan maturity date should not get modified due to the new row created 
> with the interest accrued till current system date. It should be as per 
> original schedule.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-137) Created parent GL account is not displaying properly in the dropdown while creating the GL Account

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-137:
--
Labels: confirm p1  (was: )

> Created parent GL account is not displaying properly in the dropdown while 
> creating the GL Account
> --
>
> Key: FINERACT-137
> URL: https://issues.apache.org/jira/browse/FINERACT-137
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Accounting
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: Create GL Account page.png
>
>
> 1. Create a GL account for Assets and Account usage as Header.
> 2. Create a GL account for Assets, account usage as Detail and parent as 
> created above.
> 3. It is allowing to create the GL account for assets with Account usage as 
> detail. 
> > If the Header is more than 12 in entities then it is not getting displayed 
> > in the drop down under Parent while creating the GL account.
> > The Header accounts created is getting displayed under Parent dropdown for 
> > all account types. it should get filtered according to the account types. 
> > Eg. If the account type is Equity only equity related header accounts 
> > should get displayed under parent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-126) Not able to Submit the loan application if multi tranche is added and the "Expected disbursement on" field is left blank displays internal server error

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-126:
--
Labels: confirm p1  (was: )

> Not able to Submit the loan application if multi tranche is added and the 
> "Expected disbursement on" field is left blank displays internal server error
> ---
>
> Key: FINERACT-126
> URL: https://issues.apache.org/jira/browse/FINERACT-126
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: null point exception2.png, null point exception..png
>
>
> 1. Create a simple loan product with multi tranche.
> 2. Click on Clients -> Client -> New Loan -> Select the above product -> 
> Enter submitted date as 01 March 2016 and Expected disbursement date as same. 
> Select 2 tranches and for the first tranche enter the valid inputs and for 
> the second tranche add only amount and click on submit button.
> > Displayed Internal server error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-126) Not able to Submit the loan application if multi tranche is added and the "Expected disbursement on" field is left blank displays internal server error

[Edward Cable (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826053#comment-15826053
 ] 

Edward Cable commented on FINERACT-126:
---

Works fine on first tranche disbursal but issue present on second.

> Not able to Submit the loan application if multi tranche is added and the 
> "Expected disbursement on" field is left blank displays internal server error
> ---
>
> Key: FINERACT-126
> URL: https://issues.apache.org/jira/browse/FINERACT-126
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: null point exception2.png, null point exception..png
>
>
> 1. Create a simple loan product with multi tranche.
> 2. Click on Clients -> Client -> New Loan -> Select the above product -> 
> Enter submitted date as 01 March 2016 and Expected disbursement date as same. 
> Select 2 tranches and for the first tranche enter the valid inputs and for 
> the second tranche add only amount and click on submit button.
> > Displayed Internal server error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-126) Not able to Submit the loan application if multi tranche is added and the "Expected disbursement on" field is left blank displays internal server error

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-126:
--
Labels: p1  (was: confirm p1)

> Not able to Submit the loan application if multi tranche is added and the 
> "Expected disbursement on" field is left blank displays internal server error
> ---
>
> Key: FINERACT-126
> URL: https://issues.apache.org/jira/browse/FINERACT-126
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: null point exception2.png, null point exception..png
>
>
> 1. Create a simple loan product with multi tranche.
> 2. Click on Clients -> Client -> New Loan -> Select the above product -> 
> Enter submitted date as 01 March 2016 and Expected disbursement date as same. 
> Select 2 tranches and for the first tranche enter the valid inputs and for 
> the second tranche add only amount and click on submit button.
> > Displayed Internal server error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-117) Tranche disbursement charge % disbursed amount is displaying as -ve amount if the 2nd tranche disbursed is with lesser amount and charge was waived before 2nd disbursem

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-117:
--
Labels: p1  (was: )

> Tranche disbursement charge % disbursed amount is displaying as -ve amount if 
> the 2nd tranche disbursed is with lesser amount and charge was waived before 
> 2nd disbursement
> ---
>
> Key: FINERACT-117
> URL: https://issues.apache.org/jira/browse/FINERACT-117
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: Mifos X Client 2016-03-24 15-30-57.png
>
>
> 1. Create a tranche disbursement charge with % disbursement amount.
> 2. Create a tranche loan with 2 tranche count, attache the above charge to it.
> 3. Submit new loan application for a client on 01 January 2016 with first 
> tranche of 5000 on same date and second tranche of 5000 on 01 March 2016.
> 4. Approve and disburse the first tranche on 01 January 2016.
> 5. Click on Charges and waive charge on 01 March 2016.
> 6. Disburse the 2nd tranche on 01 March 2016 and while disbursement change 
> the amount to 2000.
> 7. Click on Repayment schedule in which the tranche disbursement charge is 
> displaying as -30 (Suppose to disburse 5000 so 1%of 5000=50. Waived 50 and 
> Disbursed 2000. 1% of 2000=20.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-115) In Loan tranche details page if any tranche is added, "Tranche disbursement charge" is getting added twice"

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-115:
--
Labels: p1  (was: )

> In Loan tranche details page if any tranche is added, "Tranche disbursement 
> charge" is getting added twice"
> ---
>
> Key: FINERACT-115
> URL: https://issues.apache.org/jira/browse/FINERACT-115
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: Add trache details page.png
>
>
> 1. Create a loan product with interest recalculation enabled, Tranche count 
> as 3 and Tranche disbursement charge attached as Flat-100.
> 2. Submit new loan application for a client on 01 January 2016, with 2 
> tranches attached as 5000 on 01 January 2016 and 2nd tranche 5000 on 01 March 
> 2016.
> 3. Approve and disburse the first tranche.
> 4. While disbursing the 2nd tranche change amount to 3000 and disburse the 
> 2nd tranche on 01 March 2016.
> 5. Click on Loan tranche details page and add another tranche on 24 March 
> 2016 and amount as 2000.
> 6. Click on repayment schedule in which the charge applied as 200.
> > It should be 100.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-106) Not able to change week day in Center meeting with weekly meeting attached, displays Internal server error

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-106:
--
Labels: confirm p1  (was: )

> Not able to change week day in Center meeting with weekly meeting attached, 
> displays Internal server error
> --
>
> Key: FINERACT-106
> URL: https://issues.apache.org/jira/browse/FINERACT-106
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: Edit Center meeting.png
>
>
> 1. Create a Center with weekly meeting attached from 01 March 2016 and every 
> week on Friday.
> 2. Click on edit meeting and change day in a week as Wednesday and click on 
> submit button.
> > Not able to save the page displays internal server error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-105) Issue related to Change future meeting functionality

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-105:
--
Labels: confirm p2  (was: )

> Issue related to Change future meeting functionality
> 
>
> Key: FINERACT-105
> URL: https://issues.apache.org/jira/browse/FINERACT-105
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
>
> 1. If the loan is disbursed on 01 March 2016 and first repayment date is on 
> 01 April 2016, then it should allow to change future meeting date with in 
> current system date to 30 April 2016.
> > If the future meeting date is set to current system date then first 
> > repayment should fall on today's date only.
> 2. It should not allow to change future meeting date from 01 April 2016 to 01 
> May 2016 or beyond that,(beyond immediate next meeting date) and proper error 
> message should get displayed.
> 3. If the future meeting date is changed from 01 April 2016 to today's system 
> date and again changed to 05 April 2016, then first repayment date should 
> fall on 05 April 2016.
> 4. After change in future meeting date from 01 April 2016 to today's system 
> date and new loan is disbursed on 01 March 2016 then first repayment date 
> should fall on today's (current system) date.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-99) Waiving of charge results in an incorrect account balance status

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-99:
-
Labels: confirm p1  (was: )

> Waiving of charge results in an incorrect account balance status
> 
>
> Key: FINERACT-99
> URL: https://issues.apache.org/jira/browse/FINERACT-99
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> Example affected loan:
> - The summary for this loan shows it as active: Contract > Paid, however 
> Outstanding balance is 0.
> - When checking the Transactions the balance is -67 (which suggests overpaid).
> - And finally the "Disbursed Loan Report" reports an overdue status with a 
> balance of 0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-99) Waiving of charge results in an incorrect account balance status

[Edward Cable (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826043#comment-15826043
 ] 

Edward Cable commented on FINERACT-99:
--

[~emmanueln...@musoni.eu] Can you please provide reproducible steps and the 
details of the loan product you have configured.

> Waiving of charge results in an incorrect account balance status
> 
>
> Key: FINERACT-99
> URL: https://issues.apache.org/jira/browse/FINERACT-99
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> Example affected loan:
> - The summary for this loan shows it as active: Contract > Paid, however 
> Outstanding balance is 0.
> - When checking the Transactions the balance is -67 (which suggests overpaid).
> - And finally the "Disbursed Loan Report" reports an overdue status with a 
> balance of 0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-98) unable to delete a tranche from loan tranche details screen

[Edward Cable (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826040#comment-15826040
 ] 

Edward Cable commented on FINERACT-98:
--

This one should be fixed but other issues related to tranches have arisen. 

> unable to delete a tranche from loan tranche details screen
> ---
>
> Key: FINERACT-98
> URL: https://issues.apache.org/jira/browse/FINERACT-98
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: bharath c
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> steps to reproduce:
> 1.create a 2 tranche loan
> 2.disburse 2 tranches
> 3.undo the last tranche using "undo last tranche" option
> 4.try to delete the 2nd tranche from "loan tranche details"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-98) unable to delete a tranche from loan tranche details screen

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-98:
-
Labels: confirm p1  (was: )

> unable to delete a tranche from loan tranche details screen
> ---
>
> Key: FINERACT-98
> URL: https://issues.apache.org/jira/browse/FINERACT-98
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: bharath c
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> steps to reproduce:
> 1.create a 2 tranche loan
> 2.disburse 2 tranches
> 3.undo the last tranche using "undo last tranche" option
> 4.try to delete the 2nd tranche from "loan tranche details"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-89) 1st tranche will appear twice in repayment schedule when disbursement date and first repayment date is on same date

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-89:
-
Labels: confirm p1  (was: )

> 1st tranche will appear twice in repayment schedule when disbursement date 
> and first repayment date is on same date
> ---
>
> Key: FINERACT-89
> URL: https://issues.apache.org/jira/browse/FINERACT-89
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: bharath c
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: issue.png
>
>
> 1st tranche will appear twice in repayment schedule when disbursement date 
> and first repayment date is on same date
> steps to produce:-
> example
> create a tranche loan
> 1.expected disbursement date =04 January 2016
> 2. first repayment date = 04 January 2016
> see loan no-  308 in demo serveer 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FINERACT-87) Attache meeting should not get displayed after the meeting is attached to a Group

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable resolved FINERACT-87.
--
Resolution: Fixed

Attach meeting option is no longer displayed on demo 3 running 16.12.01 - edit 
button is available. 

> Attache meeting should not get displayed after the meeting is attached to a 
> Group
> -
>
> Key: FINERACT-87
> URL: https://issues.apache.org/jira/browse/FINERACT-87
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p3
> Attachments: Attache meeting-2.png
>
>
> Create a Group and attach meeting to it. Even after attaching meeting the 
> "Attache meeting" field is displaying under more. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-87) Attache meeting should not get displayed after the meeting is attached to a Group

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-87:
-
Labels: p3  (was: )

> Attache meeting should not get displayed after the meeting is attached to a 
> Group
> -
>
> Key: FINERACT-87
> URL: https://issues.apache.org/jira/browse/FINERACT-87
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p3
> Attachments: Attache meeting-2.png
>
>
> Create a Group and attach meeting to it. Even after attaching meeting the 
> "Attache meeting" field is displaying under more. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-80) Group loans not included in resultset returned by "LoanReadPlatformServiceImpl.retrieveAll" method

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-80:
-
Issue Type: Improvement  (was: Bug)

> Group loans not included in resultset returned by 
> "LoanReadPlatformServiceImpl.retrieveAll" method
> --
>
> Key: FINERACT-80
> URL: https://issues.apache.org/jira/browse/FINERACT-80
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>  Labels: p2
>
> *Replace the following line:*
> {code}
> sqlBuilder.append(" join m_office o on o.id = c.office_id");
> {code}
> *with:*
> {code}
> sqlBuilder.append(" join m_office o on (o.id = c.office_id or o.id = 
> g.office_id) ");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-80) Group loans not included in resultset returned by "LoanReadPlatformServiceImpl.retrieveAll" method

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-80:
-
Labels: p2  (was: )

> Group loans not included in resultset returned by 
> "LoanReadPlatformServiceImpl.retrieveAll" method
> --
>
> Key: FINERACT-80
> URL: https://issues.apache.org/jira/browse/FINERACT-80
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>  Labels: p2
>
> *Replace the following line:*
> {code}
> sqlBuilder.append(" join m_office o on o.id = c.office_id");
> {code}
> *with:*
> {code}
> sqlBuilder.append(" join m_office o on (o.id = c.office_id or o.id = 
> g.office_id) ");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [ANNOUNCE] Apache Fineract 0.6.0-incubating Release

[Andy Wenk]

Hey all,

congrats for the new release ;-). I heard about Fineract the first time and had 
a look to the website and the wiki pages (just scanned a bit). It sounds 
interesting. I would love to read  more about real life usecases. Can anyone 
point me to some posts or info where I get an idea how to use this piece of 
software?

Thanks a lot in advance!

All the best

Andy

--
Andy Wenk
RockIt!

Hamburg / Germany

GPG public key: https://pgp.mit.edu/pks/lookup?op=get&search=0x4F1D0C59BC90917D

> On 17 Jan 2017, at 13:54, Nazeer Shaik  wrote:
> 
> Hi all,
> 
> The Apache Fineract team would like to announce the release of Apache 
> Fineract 0.6.0-incubating with source and binary artifacts.
> 
> Apache Fineract is an open source system for core banking as a platform. 
> Fineract provides a reliable, robust, and affordable solution for 
> entrepreneurs, financial institutions, and service providers to offer 
> financial services to the world’s 2 billion under banked and unbanked.
> 
> More details regarding Apache Fineract can be found at 
> http://fineract.incubator.apache.org/
> 
> The release artifacts can be downloaded here:
> https://dist.apache.org/repos/dist/release/incubator/fineract/0.6.0-incubating/
> 
> The release notes can be found here:
> https://cwiki.apache.org/confluence/display/FINERACT/0.6.0-incubating+Release-+Apache+Fineract
> 
> Thanks!
> The Apache Fineract Team 
> --- DISCLAIMER  Apache Fineract is an effort undergoing incubation at The 
> Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. 
> Incubation is required of all newly accepted projects until a further review 
> indicates that the infrastructure, communications, and decision making 
> process have stabilized in a manner consistent with other successful ASF 
> projects. While incubation status is not necessarily a reflection of the 
> completeness or stability of the code,it does indicate that the project has 
> yet to be fully endorsed by the ASF.
> 

[jira] [Updated] (FINERACT-78) Specified due date percentage charge calculation uses loan principal amount instead of installment principal amount

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-78:
-
Labels: confirm p1  (was: p1)

> Specified due date percentage charge calculation uses loan principal amount 
> instead of installment principal amount
> ---
>
> Key: FINERACT-78
> URL: https://issues.apache.org/jira/browse/FINERACT-78
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: Sp. Charge 1.png, Sp. Charge 2.png, Sp. Charge 3.png, 
> Sp. Charge 4.png
>
>
> Specified due date percentage charge calculation uses loan principal amount 
> instead of installment principal amount.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-78) Specified due date percentage charge calculation uses loan principal amount instead of installment principal amount

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-78:
-
Labels: p1  (was: )

> Specified due date percentage charge calculation uses loan principal amount 
> instead of installment principal amount
> ---
>
> Key: FINERACT-78
> URL: https://issues.apache.org/jira/browse/FINERACT-78
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: Sp. Charge 1.png, Sp. Charge 2.png, Sp. Charge 3.png, 
> Sp. Charge 4.png
>
>
> Specified due date percentage charge calculation uses loan principal amount 
> instead of installment principal amount.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-69) Wrong interest amount when using Rounding Mode - Down/Floor for Flat Loans

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-69:
-
Issue Type: Improvement  (was: Bug)

> Wrong interest amount when using Rounding Mode - Down/Floor for Flat Loans
> --
>
> Key: FINERACT-69
> URL: https://issues.apache.org/jira/browse/FINERACT-69
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: George Lteif
>Assignee: Markus Geiss
> Attachments: screenshot-1.png
>
>
> For organizations using the Floor rounding Mode, the expected behavior is to 
> have the rounding rules done for the loan schedules and not the total 
> interest amount
> what is currently done in Mifos X is applying the rounding rule on the total 
> interest amount calculated first which is leading to a loss of profit for the 
> organization
> Scenario:
> create a FLAT interest loan product with a monthly 1.3% interest rate
> rounding mode is set to Floor
> create a loan for the amount of 2900$ over a period of 21 months repayments 
> (one repayment per month)
> expected result would be
> 2900*1.3%*21 repayments = 791.7 
> it should always be rounded up here regardless of the rounding mode being set 
> to not lead to any loss of profit
> interest calculated in MifosX is 791 (screenshot attaches)
> which is a 0.7$ or 1$  less than expected



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-36) User defined Templates do not work when Tomcat is behind a proxy

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-36:
-
Labels: p3  (was: )

> User defined Templates do not work when Tomcat is behind a proxy
> 
>
> Key: FINERACT-36
> URL: https://issues.apache.org/jira/browse/FINERACT-36
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: System
> Environment: Linux, Nginx that proxy passes to Tomcat, OpenJDK7
>Reporter: James Rowe
>Assignee: Markus Geiss
>  Labels: p3
>
> Related to https://mifosforge.jira.com/browse/MIFOSX-2322 This issue was 
> raised by our client and the fix provided did not actually resolve the root 
> issue. As mentioned in the Environment section, our server is a multitenant 
> server and has Nginx set up to proxy requests to Tomcat. Because of this 
> setup though, User defined templates do not work. Looking through the code 
> (https://github.com/openMF/mifosx/blob/develop/fineract-provider/src/main/java/org/apache/fineract/template/service/TemplateMergeService.java)
>  I have found out that the TemplateMergeService uses the HTTP API to return 
> the results for the templates. The issue is it tries to connect to the wrong 
> port and with the wrong tenant. The tomcat server is running on port 8008 and 
> 8443 and the template merge service attempts to connect on port 80/433. Nginx 
> will receive the request and ignore them because of how my routing rules are 
> set up. Our server is setup to give a subdomain to each tenant and nginx uses 
> this subdomain name to set the Fineract-Platform-Id header on the request. 
> Because the API tries to connect on localhost (without any subdomain), the 
> requests made from the API to the API fail to connect. It doesn't really 
> matter in the end, since the service grabs the wrong tenant information. I'm 
> not sure where it gets the tenant identifier from, but it chose "default" as 
> the tenant when it should have used the name of our client instead. (As a 
> precaution, our default tenant is a completely empty tenant)
> In summary, the TemplateMergeService attempts to make calls to the API, but 
> fails to ascertain the correct settings to connect to the API. It fails to 
> choose the correct tenant identifier (uses default, when that is not 
> correct), connects on the wrong port (80 instead of 8008), and doesn't use 
> the right server name for the port it connects to. The last two issues are 
> very related as a proper fix would be to either change the port or change the 
> server name. I hope this is enough information to write a fix, but if you 
> need any more information let me know. I'll be glad to help however I can.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-24) Getting internal server error when trying to post repayment for some loans

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-24:
-
Labels: p3 unable  (was: p3)

> Getting internal server error when trying to post repayment for some loans
> --
>
> Key: FINERACT-24
> URL: https://issues.apache.org/jira/browse/FINERACT-24
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: p3, unable
>
> https://mifosforge.jira.com/browse/MIFOSX-2373 - see attachments and comments
> When trying to post repayment for our loans (plain vanilla installment loans),
> we get the following error. This happens in about 10% of cases:
> "timestamp": 1449545515301
> "status": 500
> "error": "Internal Server Error"
> "exception": "java.lang.ArithmeticException"
> "message": "Non-terminating decimal expansion; no exact representable decimal 
> result."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-24) Getting internal server error when trying to post repayment for some loans

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-24:
-
Labels: p3  (was: confirm p3)

> Getting internal server error when trying to post repayment for some loans
> --
>
> Key: FINERACT-24
> URL: https://issues.apache.org/jira/browse/FINERACT-24
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: p3
>
> https://mifosforge.jira.com/browse/MIFOSX-2373 - see attachments and comments
> When trying to post repayment for our loans (plain vanilla installment loans),
> we get the following error. This happens in about 10% of cases:
> "timestamp": 1449545515301
> "status": 500
> "error": "Internal Server Error"
> "exception": "java.lang.ArithmeticException"
> "message": "Non-terminating decimal expansion; no exact representable decimal 
> result."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-23) Fees rounding off attached to the loan is not working as expected

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-23:
-
Labels: p3  (was: )

> Fees rounding off attached to the loan is not working as expected
> -
>
> Key: FINERACT-23
> URL: https://issues.apache.org/jira/browse/FINERACT-23
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges, Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: p3
>
> https://mifosforge.jira.com/browse/MIFOSX-2374
> Currently in the community app Fees rounding off is not happening properly,
> Eg. In a loan product if 
> Decimal Places-2
> Currency in Multiples Of-1
> Installment in multiples of-1,
> Disbursement fees defined as 9.877% of Approved amount, 
> Principal is 1, ROI - 18%pm, repaid every 1,
> Loan term- 26 weeks.
> After disbursement if the repayment schedule is clicked then fees displayed 
> is not rounded off. 
> Please find the demo link
> https://demo.openmf.org/#/viewloanaccount/6172



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-22) Adding Floating Interest Rate "Error" - cannot create floating rate

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-22:
-
Labels: confirm p1  (was: )

> Adding Floating Interest Rate "Error" - cannot create floating rate
> ---
>
> Key: FINERACT-22
> URL: https://issues.apache.org/jira/browse/FINERACT-22
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2391 - see attachments
> When a user tries to add a new Floating rate, non-descript "Error" is 
> returned.
> 2nd MAJOR ISSUE: New Product cannot be created if Floating Rate not defined. 
> "Error
> The parameter `isLinkedToFloatingInterestRates` has been passed and is not 
> supported for this request." returned.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-21) Waive overdue charge is not working as expected

[Edward Cable (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826008#comment-15826008
 ] 

Edward Cable commented on FINERACT-21:
--

On original issue was moved to Ready for Testing - checking if still a bug. 

> Waive overdue charge is not working as expected
> ---
>
> Key: FINERACT-21
> URL: https://issues.apache.org/jira/browse/FINERACT-21
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments
> 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply 
> the above created charge to it.
> 2. Submit new loan application for a client on 01 October 2015 approve and 
> disburse on same date.
> 3. Execute the scheduler job "Apply penalty for overdue loans",
> 4. Navigate back to the same loan account page and click on the charges and 
> waive charge on 01 November 2015.
> > Charge got waved, but in the repayment schedule wrong entries got created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-21) Waive overdue charge is not working as expected

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-21:
-
Labels: confirm  (was: )

> Waive overdue charge is not working as expected
> ---
>
> Key: FINERACT-21
> URL: https://issues.apache.org/jira/browse/FINERACT-21
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments
> 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply 
> the above created charge to it.
> 2. Submit new loan application for a client on 01 October 2015 approve and 
> disburse on same date.
> 3. Execute the scheduler job "Apply penalty for overdue loans",
> 4. Navigate back to the same loan account page and click on the charges and 
> waive charge on 01 November 2015.
> > Charge got waved, but in the repayment schedule wrong entries got created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-21) Waive overdue charge is not working as expected

[Edward Cable (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Edward Cable updated FINERACT-21:
-
Labels: confirm p1  (was: confirm)

> Waive overdue charge is not working as expected
> ---
>
> Key: FINERACT-21
> URL: https://issues.apache.org/jira/browse/FINERACT-21
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments
> 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply 
> the above created charge to it.
> 2. Submit new loan application for a client on 01 October 2015 approve and 
> disburse on same date.
> 3. Execute the scheduler job "Apply penalty for overdue loans",
> 4. Navigate back to the same loan account page and click on the charges and 
> waive charge on 01 November 2015.
> > Charge got waved, but in the repayment schedule wrong entries got created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[ANNOUNCE] Apache Fineract 0.6.0-incubating Release

[Nazeer Shaik]

Hi all,



The Apache Fineract team would like to announce the release of Apache
Fineract 0.6.0-incubating with source and binary artifacts.



*Apache Fineract is an open source system for core banking as a platform.
Fineract provides a reliable, robust, and affordable solution for
entrepreneurs, financial institutions, and service providers to offer
financial services to the world’s 2 billion under banked and unbanked.*



More details regarding Apache Fineract can be found at
http://fineract.incubator.apache.org/



The release artifacts can be downloaded here:

https://dist.apache.org/repos/dist/release/incubator/fineract/0.6.0-incubating/



The release notes can be found here:

https://cwiki.apache.org/confluence/display/FINERACT/0.6.0-incubating+Release-+Apache+Fineract



Thanks!

The Apache Fineract Team

--- DISCLAIMER  Apache Fineract is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code,it does indicate that the project
has yet to be fully endorsed by the ASF.

[RESULT][VOTE] [APACHE FINERACT] 0.6.0-incubating for release

[Nazeer Shaik]

Hi all,

The Apache Fineract 0.6.0-incubating release vote is now closed and has
passed as follows:


*3 binding votes.*

*Justin McLean*

*Jim Jagielski*

*John D Ament*


[*3*] +1 (binding) votes

[0] -1 (binding) votes


Thanks to all reviewing the release.

Nazeer

[jira] [Commented] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error

[Shaik Nazeer Hussain (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825958#comment-15825958
 ] 

Shaik Nazeer Hussain commented on FINERACT-364:
---

Sent a PR https://github.com/apache/incubator-fineract/pull/276.
 

> Submitting Collection Sheet through Maker Checker Throwing Error
> 
>
> Key: FINERACT-364
> URL: https://issues.apache.org/jira/browse/FINERACT-364
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>Priority: Blocker
>  Labels: p1
> Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png
>
>
> 1. Enable Maker Checker in System>>Configuration.
> 2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select 
> the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
> 3. Disburse JLG Loan to a client.
> 4. Go to collection sheet and fill the details and select the center name but 
> don't select the group name.
> 5. Click  on Submit button, which goes to Checker Inbox. 
> 6. When you try to approve it , it throws the error.
> "The parameter `loanTransactions` has been passed and is not supported for 
> this request.
> The parameter `SavingsTransactions` has been passed and is not supported for 
> this request."  
> Check the attached file/screenshots.
> The above same error is thrown when,
> > You select both center and group and submit collection sheet. 
> > We try to submit through 'productive collection sheet'.
> > We try to submit 'Individual Collection Sheet'. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825956#comment-15825956
 ] 

ASF GitHub Bot commented on FINERACT-364:
-

GitHub user nazeer1100126 opened a pull request:

https://github.com/apache/incubator-fineract/pull/276

FINERACT-364 - Submitting Collection Sheet through Maker Checker Throwing 
Error



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nazeer1100126/incubator-fineract 
develop_FINERACT-364

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-fineract/pull/276.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #276


commit 0173c8d05fd33a7ac59358beb4321edcca6f9b68
Author: Nazeer Hussain Shaik 
Date:   2017-01-17T12:08:01Z

FINERACT-364




> Submitting Collection Sheet through Maker Checker Throwing Error
> 
>
> Key: FINERACT-364
> URL: https://issues.apache.org/jira/browse/FINERACT-364
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>Priority: Blocker
>  Labels: p1
> Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png
>
>
> 1. Enable Maker Checker in System>>Configuration.
> 2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select 
> the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
> 3. Disburse JLG Loan to a client.
> 4. Go to collection sheet and fill the details and select the center name but 
> don't select the group name.
> 5. Click  on Submit button, which goes to Checker Inbox. 
> 6. When you try to approve it , it throws the error.
> "The parameter `loanTransactions` has been passed and is not supported for 
> this request.
> The parameter `SavingsTransactions` has been passed and is not supported for 
> this request."  
> Check the attached file/screenshots.
> The above same error is thrown when,
> > You select both center and group and submit collection sheet. 
> > We try to submit through 'productive collection sheet'.
> > We try to submit 'Individual Collection Sheet'. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Fineract 0.6.0 (incubating)

[Nazeer Shaik]

Thank you John.

On Tue, Jan 17, 2017 at 5:26 PM, John D. Ament 
wrote:

> Yes, please treat my vote as a +1 :-)
>
> On Tue, Jan 17, 2017 at 4:42 AM Nazeer Shaik <
> nazeer.sh...@confluxtechnologies.com> wrote:
>
> > Hi John,
> >
> > As you suggested we have closed the issue https://issues.apache.org/
> > jira/browse/FINERACT-357
> >  and created two
> > separate issues to address
> > remaining 2 suggestions/reviews.
> > https://issues.apache.org/jira/browse/FINERACT-371
> > https://issues.apache.org/jira/browse/FINERACT-368
> >
> > With this change, can we assume your vote is +1? :-)
> >
> > Thanks,
> > Nazeer
> >
> > Thanks,
> > Nazeer
> >
> > *Principal Architect, **Conflux Technologies Pvt Ltd
> > *
> >
> > *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> > Bengaluru, Karnataka, 560043 INDIA
> >
> >
> > Disclaimer: The information contained in this e-mail message and any
> > files/attachment transmitted with it is confidential and for the sole use
> > of the intended recipient(s) or entity identified. If you are not the
> > intended recipient, please email: supp...@confluxtechnologies.com and
> > destroy/delete all copies and attachment thereto along with the original
> > message. Any unauthorized review, use, disclosure, dissemination,
> > forwarding, printing or copying of this email or any action taken in
> > reliance on this e-mail is strictly prohibited and is unlawful. The
> > recipient acknowledges that Conflux Technologies Private Limited or its
> > subsidiaries and associated companies are unable to exercise control or
> > ensure or guarantee the integrity of/over the contents of the information
> > contained in e-mail transmissions. Before opening any attachments, please
> > check.
> >
> > On Thu, Jan 12, 2017 at 9:47 PM, Jim Jagielski  wrote:
> >
> > > +1. Thx!
> > >
> > > > On Jan 12, 2017, at 7:36 AM, Nazeer Shaik 
> > > wrote:
> > > >
> > > > Hi John,
> > > >
> > > > We have closed the Jira issue
> > > > https://issues.apache.org/jira/browse/FINERACT-357 and created two
> > > separate
> > > > jira issues for remaining two items.RAT is integrated such a way it
> > will
> > > > check all directories and files from top level directory. So nothing
> > will
> > > > be missed.
> > > >
> > > > Thanks,
> > > > Nazeer
> > > >
> > > > On Thu, Jan 12, 2017 at 5:34 PM, John D. Ament <
> johndam...@apache.org>
> > > > wrote:
> > > >
> > > >> On Thu, Jan 12, 2017 at 2:23 AM Nazeer Shaik <
> > nazeer1100...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> Hi John,
> > > >>>
> > > >>> Thank you for reviewing this release.
> > > >>>
> > > >>> 1) I have kept https://issues.apache.org/jira/browse/FINERACT-357
> > open
> > > >> as
> > > >>> we have addressed 4 out of 6 suggestions given for 0.5.0-incubating
> > > >>> release. Other two will be addressed in next/future releases. I
> have
> > > >> added
> > > >>> these details in note section of current release email.
> > > >>>
> > > >>
> > > >> I would ask that you close the ticket w/ the completed tasks, and
> > > create a
> > > >> new one with the remaining items.
> > > >>
> > > >> I'm willing to change to a +1 if this occurs.
> > > >>
> > > >>
> > > >>> 2) You need to follow the build instructions mentioned in the
> > > readme.md
> > > >>> file to build from source. We have mentioned these details on every
> > > >>> release.
> > > >>>
> > > >>
> > > >> My struggle is that you have a build directory in one of the child
> > dirs.
> > > >> There is no top level build - as a result, there's no easy way to
> run
> > > rat
> > > >> from the root.  This means that there are a number of files not
> easily
> > > >> verified.
> > > >>
> > > >>
> > > >>>
> > > >>> *Build & RAT verification steps can be found at:*
> > > >>>
> > > >>>
> > > >>> https://github.com/apache/incubator-fineract/blob/0.6.0-
> > > >> incubating/README.md
> > > >>> or refer 'README.md' in *apache-fineract-0.6.0-
> incubating-src.tar.gz*
> > > >>>
> > > >>> Please let us know if you are still not able to build after
> following
> > > >> these
> > > >>> steps.
> > > >>>
> > > >>> Nazeer
> > > >>>
> > > >>> On Thu, Jan 12, 2017 at 8:28 AM, John D. Ament <
> > johndam...@apache.org>
> > > >>> wrote:
> > > >>>
> > >  Nazeer,
> > > 
> > >  Sorry but -1.  There was a ticket raised to address release issues
> > in
> > > >> the
> > >  prior release vote.  The IPMC typically looks to see those release
> > > >> issue
> > >  tickets reolved in the following release.
> > > 
> > >  https://issues.apache.org/jira/browse/FINERACT-357 was not
> resolved
> > > in
> > >  this
> > >  release.
> > > 
> > >  Can you explain why not?
> > > 
> > >  I still struggle to figure out how to build fineract.  In fact,
> the
> > >  build.sh script still does not work.
> > > 
> > >  John
> > > 
> > >  On Wed, Jan 11, 2017 at 3:46 AM Nazeer Shaik <
> > 

Re: [VOTE] Release Apache Fineract 0.6.0 (incubating)

[John D. Ament]

Yes, please treat my vote as a +1 :-)

On Tue, Jan 17, 2017 at 4:42 AM Nazeer Shaik <
nazeer.sh...@confluxtechnologies.com> wrote:

> Hi John,
>
> As you suggested we have closed the issue https://issues.apache.org/
> jira/browse/FINERACT-357
>  and created two
> separate issues to address
> remaining 2 suggestions/reviews.
> https://issues.apache.org/jira/browse/FINERACT-371
> https://issues.apache.org/jira/browse/FINERACT-368
>
> With this change, can we assume your vote is +1? :-)
>
> Thanks,
> Nazeer
>
> Thanks,
> Nazeer
>
> *Principal Architect, **Conflux Technologies Pvt Ltd
> *
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>
>
> Disclaimer: The information contained in this e-mail message and any
> files/attachment transmitted with it is confidential and for the sole use
> of the intended recipient(s) or entity identified. If you are not the
> intended recipient, please email: supp...@confluxtechnologies.com and
> destroy/delete all copies and attachment thereto along with the original
> message. Any unauthorized review, use, disclosure, dissemination,
> forwarding, printing or copying of this email or any action taken in
> reliance on this e-mail is strictly prohibited and is unlawful. The
> recipient acknowledges that Conflux Technologies Private Limited or its
> subsidiaries and associated companies are unable to exercise control or
> ensure or guarantee the integrity of/over the contents of the information
> contained in e-mail transmissions. Before opening any attachments, please
> check.
>
> On Thu, Jan 12, 2017 at 9:47 PM, Jim Jagielski  wrote:
>
> > +1. Thx!
> >
> > > On Jan 12, 2017, at 7:36 AM, Nazeer Shaik 
> > wrote:
> > >
> > > Hi John,
> > >
> > > We have closed the Jira issue
> > > https://issues.apache.org/jira/browse/FINERACT-357 and created two
> > separate
> > > jira issues for remaining two items.RAT is integrated such a way it
> will
> > > check all directories and files from top level directory. So nothing
> will
> > > be missed.
> > >
> > > Thanks,
> > > Nazeer
> > >
> > > On Thu, Jan 12, 2017 at 5:34 PM, John D. Ament 
> > > wrote:
> > >
> > >> On Thu, Jan 12, 2017 at 2:23 AM Nazeer Shaik <
> nazeer1100...@apache.org>
> > >> wrote:
> > >>
> > >>> Hi John,
> > >>>
> > >>> Thank you for reviewing this release.
> > >>>
> > >>> 1) I have kept https://issues.apache.org/jira/browse/FINERACT-357
> open
> > >> as
> > >>> we have addressed 4 out of 6 suggestions given for 0.5.0-incubating
> > >>> release. Other two will be addressed in next/future releases. I have
> > >> added
> > >>> these details in note section of current release email.
> > >>>
> > >>
> > >> I would ask that you close the ticket w/ the completed tasks, and
> > create a
> > >> new one with the remaining items.
> > >>
> > >> I'm willing to change to a +1 if this occurs.
> > >>
> > >>
> > >>> 2) You need to follow the build instructions mentioned in the
> > readme.md
> > >>> file to build from source. We have mentioned these details on every
> > >>> release.
> > >>>
> > >>
> > >> My struggle is that you have a build directory in one of the child
> dirs.
> > >> There is no top level build - as a result, there's no easy way to run
> > rat
> > >> from the root.  This means that there are a number of files not easily
> > >> verified.
> > >>
> > >>
> > >>>
> > >>> *Build & RAT verification steps can be found at:*
> > >>>
> > >>>
> > >>> https://github.com/apache/incubator-fineract/blob/0.6.0-
> > >> incubating/README.md
> > >>> or refer 'README.md' in *apache-fineract-0.6.0-incubating-src.tar.gz*
> > >>>
> > >>> Please let us know if you are still not able to build after following
> > >> these
> > >>> steps.
> > >>>
> > >>> Nazeer
> > >>>
> > >>> On Thu, Jan 12, 2017 at 8:28 AM, John D. Ament <
> johndam...@apache.org>
> > >>> wrote:
> > >>>
> >  Nazeer,
> > 
> >  Sorry but -1.  There was a ticket raised to address release issues
> in
> > >> the
> >  prior release vote.  The IPMC typically looks to see those release
> > >> issue
> >  tickets reolved in the following release.
> > 
> >  https://issues.apache.org/jira/browse/FINERACT-357 was not resolved
> > in
> >  this
> >  release.
> > 
> >  Can you explain why not?
> > 
> >  I still struggle to figure out how to build fineract.  In fact, the
> >  build.sh script still does not work.
> > 
> >  John
> > 
> >  On Wed, Jan 11, 2017 at 3:46 AM Nazeer Shaik <
> > nazeer1100...@apache.org
> > >>>
> >  wrote:
> > 
> > > Hello Incubator PMC,
> > >
> > >
> > >
> > > The Apache Fineract community has voted and approved the proposal
> to
> > > release Apache Fineract 0.6.0 (incubating). We now kindly request
> the
> > > Incubator *PMC* members review and vote on this incubator release.
> > >
> > >
> > >
> > > Apach

[jira] [Assigned] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error

[Shaik Nazeer Hussain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shaik Nazeer Hussain reassigned FINERACT-364:
-

Assignee: Shaik Nazeer Hussain  (was: Markus Geiss)

> Submitting Collection Sheet through Maker Checker Throwing Error
> 
>
> Key: FINERACT-364
> URL: https://issues.apache.org/jira/browse/FINERACT-364
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>Priority: Blocker
>  Labels: p1
> Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png
>
>
> 1. Enable Maker Checker in System>>Configuration.
> 2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select 
> the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
> 3. Disburse JLG Loan to a client.
> 4. Go to collection sheet and fill the details and select the center name but 
> don't select the group name.
> 5. Click  on Submit button, which goes to Checker Inbox. 
> 6. When you try to approve it , it throws the error.
> "The parameter `loanTransactions` has been passed and is not supported for 
> this request.
> The parameter `SavingsTransactions` has been passed and is not supported for 
> this request."  
> Check the attached file/screenshots.
> The above same error is thrown when,
> > You select both center and group and submit collection sheet. 
> > We try to submit through 'productive collection sheet'.
> > We try to submit 'Individual Collection Sheet'. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-364:
--
Description: 
1. Enable Maker Checker in System>>Configuration.
2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select the 
center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
3. Disburse JLG Loan to a client.
4. Go to collection sheet and fill the details and select the center name but 
don't select the group name.
5. Click  on Submit button, which goes to Checker Inbox. 
6. When you try to approve it , it throws the error.

"The parameter `loanTransactions` has been passed and is not supported for this 
request.
The parameter `SavingsTransactions` has been passed and is not supported for 
this request."  
Check the attached file/screenshots.

The above same error is thrown when,
> You select both center and group and submit collection sheet. 
> We try to submit through 'productive collection sheet'.
> We try to submit 'Individual Collection Sheet'. 

  was:
1. Enable Maker Checker in System>>Configuration.
2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select the 
center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
3. Disburse JLG Loan to a client.
4. Go to collection sheet and fill the details and select the center name but 
don't select the group name.
5. Click  on Submit button, which goes to Checker Inbox. 
6. When you try to approve it , it throws the error.

"The parameter `loanTransactions` has been passed and is not supported for this 
request.
The parameter `SavingsTransactions` has been passed and is not supported for 
this request."  
Check the attached file/screenshots.

The above same error is thrown when,
> You select both center and group and submit collection sheet. 
> We try submit through 'productive collection sheet'.
> We try to submit 'Individual Collection Sheet'. 


> Submitting Collection Sheet through Maker Checker Throwing Error
> 
>
> Key: FINERACT-364
> URL: https://issues.apache.org/jira/browse/FINERACT-364
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Blocker
>  Labels: p1
> Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png
>
>
> 1. Enable Maker Checker in System>>Configuration.
> 2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select 
> the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
> 3. Disburse JLG Loan to a client.
> 4. Go to collection sheet and fill the details and select the center name but 
> don't select the group name.
> 5. Click  on Submit button, which goes to Checker Inbox. 
> 6. When you try to approve it , it throws the error.
> "The parameter `loanTransactions` has been passed and is not supported for 
> this request.
> The parameter `SavingsTransactions` has been passed and is not supported for 
> this request."  
> Check the attached file/screenshots.
> The above same error is thrown when,
> > You select both center and group and submit collection sheet. 
> > We try to submit through 'productive collection sheet'.
> > We try to submit 'Individual Collection Sheet'. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-364:
--
Description: 
1. Enable Maker Checker in System>>Configuration.
2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select the 
center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
3. Disburse JLG Loan to a client.
4. Go to collection sheet and fill the details and select the center name but 
don't select the group name.
5. Click  on Submit button, which goes to Checker Inbox. 
6. When you try to approve it , it throws the error.

"The parameter `loanTransactions` has been passed and is not supported for this 
request.
The parameter `SavingsTransactions` has been passed and is not supported for 
this request."  
Check the attached file/screenshots.

The above same error is thrown when,
> You select both center and group and submit collection sheet. 
> We try submit through 'productive collection sheet'.
> We try to submit 'Individual Collection Sheet'. 

  was:
1. Enable Maker Checker in System>>Configuration.
2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select the 
center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
3. Disburse JLG Loan to a client.
4. Go to collection sheet and fill the details and select the center name but 
don't select the group name.
5. Click  on Submit button, which goes to Checker Inbox. 
6. When you try to approve it , it throws the error,

"The parameter `loanTransactions` has been passed and is not supported for this 
request.
The parameter `SavingsTransactions` has been passed and is not supported for 
this request."  
Check the attached file/screenshots. 


> Submitting Collection Sheet through Maker Checker Throwing Error
> 
>
> Key: FINERACT-364
> URL: https://issues.apache.org/jira/browse/FINERACT-364
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Blocker
>  Labels: p1
> Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png
>
>
> 1. Enable Maker Checker in System>>Configuration.
> 2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select 
> the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
> 3. Disburse JLG Loan to a client.
> 4. Go to collection sheet and fill the details and select the center name but 
> don't select the group name.
> 5. Click  on Submit button, which goes to Checker Inbox. 
> 6. When you try to approve it , it throws the error.
> "The parameter `loanTransactions` has been passed and is not supported for 
> this request.
> The parameter `SavingsTransactions` has been passed and is not supported for 
> this request."  
> Check the attached file/screenshots.
> The above same error is thrown when,
> > You select both center and group and submit collection sheet. 
> > We try submit through 'productive collection sheet'.
> > We try to submit 'Individual Collection Sheet'. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error

[Shaik Nazeer Hussain (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15825793#comment-15825793
 ] 

Shaik Nazeer Hussain commented on FINERACT-364:
---

Same issue with even group collection sheet.

> Submitting Collection Sheet through Maker Checker Throwing Error
> 
>
> Key: FINERACT-364
> URL: https://issues.apache.org/jira/browse/FINERACT-364
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Blocker
>  Labels: p1
> Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png
>
>
> 1. Enable Maker Checker in System>>Configuration.
> 2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select 
> the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
> 3. Disburse JLG Loan to a client.
> 4. Go to collection sheet and fill the details and select the center name but 
> don't select the group name.
> 5. Click  on Submit button, which goes to Checker Inbox. 
> 6. When you try to approve it , it throws the error,
> "The parameter `loanTransactions` has been passed and is not supported for 
> this request.
> The parameter `SavingsTransactions` has been passed and is not supported for 
> this request."  
> Check the attached file/screenshots. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Fineract 0.6.0 (incubating)

[Nazeer Shaik]

Hi John,

As you suggested we have closed the issue https://issues.apache.org/
jira/browse/FINERACT-357 and created two separate issues to address
remaining 2 suggestions/reviews.
https://issues.apache.org/jira/browse/FINERACT-371
https://issues.apache.org/jira/browse/FINERACT-368

With this change, can we assume your vote is +1? :-)

Thanks,
Nazeer

Thanks,
Nazeer

*Principal Architect, **Conflux Technologies Pvt Ltd
*

*Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
Bengaluru, Karnataka, 560043 INDIA


Disclaimer: The information contained in this e-mail message and any
files/attachment transmitted with it is confidential and for the sole use
of the intended recipient(s) or entity identified. If you are not the
intended recipient, please email: supp...@confluxtechnologies.com and
destroy/delete all copies and attachment thereto along with the original
message. Any unauthorized review, use, disclosure, dissemination,
forwarding, printing or copying of this email or any action taken in
reliance on this e-mail is strictly prohibited and is unlawful. The
recipient acknowledges that Conflux Technologies Private Limited or its
subsidiaries and associated companies are unable to exercise control or
ensure or guarantee the integrity of/over the contents of the information
contained in e-mail transmissions. Before opening any attachments, please
check.

On Thu, Jan 12, 2017 at 9:47 PM, Jim Jagielski  wrote:

> +1. Thx!
>
> > On Jan 12, 2017, at 7:36 AM, Nazeer Shaik 
> wrote:
> >
> > Hi John,
> >
> > We have closed the Jira issue
> > https://issues.apache.org/jira/browse/FINERACT-357 and created two
> separate
> > jira issues for remaining two items.RAT is integrated such a way it will
> > check all directories and files from top level directory. So nothing will
> > be missed.
> >
> > Thanks,
> > Nazeer
> >
> > On Thu, Jan 12, 2017 at 5:34 PM, John D. Ament 
> > wrote:
> >
> >> On Thu, Jan 12, 2017 at 2:23 AM Nazeer Shaik 
> >> wrote:
> >>
> >>> Hi John,
> >>>
> >>> Thank you for reviewing this release.
> >>>
> >>> 1) I have kept https://issues.apache.org/jira/browse/FINERACT-357 open
> >> as
> >>> we have addressed 4 out of 6 suggestions given for 0.5.0-incubating
> >>> release. Other two will be addressed in next/future releases. I have
> >> added
> >>> these details in note section of current release email.
> >>>
> >>
> >> I would ask that you close the ticket w/ the completed tasks, and
> create a
> >> new one with the remaining items.
> >>
> >> I'm willing to change to a +1 if this occurs.
> >>
> >>
> >>> 2) You need to follow the build instructions mentioned in the
> readme.md
> >>> file to build from source. We have mentioned these details on every
> >>> release.
> >>>
> >>
> >> My struggle is that you have a build directory in one of the child dirs.
> >> There is no top level build - as a result, there's no easy way to run
> rat
> >> from the root.  This means that there are a number of files not easily
> >> verified.
> >>
> >>
> >>>
> >>> *Build & RAT verification steps can be found at:*
> >>>
> >>>
> >>> https://github.com/apache/incubator-fineract/blob/0.6.0-
> >> incubating/README.md
> >>> or refer 'README.md' in *apache-fineract-0.6.0-incubating-src.tar.gz*
> >>>
> >>> Please let us know if you are still not able to build after following
> >> these
> >>> steps.
> >>>
> >>> Nazeer
> >>>
> >>> On Thu, Jan 12, 2017 at 8:28 AM, John D. Ament 
> >>> wrote:
> >>>
>  Nazeer,
> 
>  Sorry but -1.  There was a ticket raised to address release issues in
> >> the
>  prior release vote.  The IPMC typically looks to see those release
> >> issue
>  tickets reolved in the following release.
> 
>  https://issues.apache.org/jira/browse/FINERACT-357 was not resolved
> in
>  this
>  release.
> 
>  Can you explain why not?
> 
>  I still struggle to figure out how to build fineract.  In fact, the
>  build.sh script still does not work.
> 
>  John
> 
>  On Wed, Jan 11, 2017 at 3:46 AM Nazeer Shaik <
> nazeer1100...@apache.org
> >>>
>  wrote:
> 
> > Hello Incubator PMC,
> >
> >
> >
> > The Apache Fineract community has voted and approved the proposal to
> > release Apache Fineract 0.6.0 (incubating). We now kindly request the
> > Incubator *PMC* members review and vote on this incubator release.
> >
> >
> >
> > Apache Fineract is an open source system for core banking as a
> >>> platform.
> > Fineract provides a reliable, robust, and affordable solution for
> > entrepreneurs, financial institutions, and service providers to offer
> > financial services to the world’s 2 billion under banked and
> >> unbanked.
>  More
> > information can be found at http://fineract.incubator.apache.org/
> >
> >
> >
> > The Apache Fineract-0.6.0-incubating release candidate is now
> >> available
> > with the following artifacts