[jira] [Resolved] (FINERACT-312) For Loan with interest recalculation periodic accrual with respect to current date is not getting modified after repayment in Transaction page

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain resolved FINERACT-312.
---
   Resolution: Fixed
Fix Version/s: 0.7.0-incubating

With Below PR issue is resolved. 
https://github.com/apache/incubator-fineract/pull/286

> For Loan with interest recalculation periodic accrual with respect to current 
> date is not getting modified after repayment in Transaction page
> --
>
> Key: FINERACT-312
> URL: https://issues.apache.org/jira/browse/FINERACT-312
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>  Labels: p1
> Fix For: 0.7.0-incubating
>
> Attachments: 35.png, 36.png, 37.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2119
> Original Description:
> 1. Create a loan product with following datasets:
> Principal: 1, no. of Installments: 12, repaid every 1 month, Nominal 
> interest rate: 1%pm,Amortization: Equal installments, Interest Method: 
> Declining Balance, Interest Calculation Period: Same as repayment 
> period,Repayment Strategy:RBI (India),Recalculate Interest: Yes,Advance 
> payments adjustment type: Reduce number of installments, Pre-closure interest 
> calculation rule: Calculate till pre closure date, Interest recalculation 
> compounding on:None, Frequency for recalculate Outstanding Principal: Same as 
> repayment period, with accounting enabled for periodic accrual.
> 2. Submit new loan application for a client on 01 March 2015 approve and 
> disburse on same date.
> 3. Click on Admin -> system -> Scheduler job - run scheduler job "Add 
> Periodic Accrual Transactions".
> 4. Navigate back to Transactions page and verify the accrued interest as on 
> current date.
> 5. Make first repayment on exact due date then verify the transaction page 
> the accrued interest as on current date is not modified.
> > The accrued interest as on current date is not getting modified even after 
> > multiple repayments. 
> Please refer the screen shot attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Surveys Discussion: SPM Framework vs Data Tables for User-Defined Surveys

[Ed Cable]

Bringing on to the mailing a discussion, we've been having amongst a number
of volunteers working on building out the UI for the SPM framework.

See

Now I have some other questions regarding the flexibility of the
surveys/SPM framework and how it relates to data tables. Is the surveys
framework only for pre-defined scorecards like PPI, IRIS, MPAT, UN SDGs,
etc? Or is it also to create brand new "surveys".

My first question would be this. If I want to create a survey from scratch
(i.e. a completely unique 15-question business plan survey) should I do
this via a Data Table or should I use your surveys framework. If the
latter, should the surveys framework be used to define a question bank (of
multiple question types - free-form, text, multi-select, etc.) and then
from this question bank, create a survey (i.e. give it a title, select
questions) and then save as a survey). If this is all possible, I want to
work with volunteers to finalize the wireframes Nayan worked on and
implement this survey wizard to create surveys powered by the Surveys
Framework.

Ed


-- Forwarded message --
From: Ed Cable 
Date: Mon, Jan 23, 2017 at 11:21 AM
Subject: Re: PPI Json tables
To: Markus Geiß 
Cc: Shaik Nazeer , Nathan McClellan <
nat...@mentorsinternational.org>, Adi Raju ,
Gaurav Saini , Nayan Ambali <
na...@confluxtechnologies.com>, Samrat Ghosh 


HI Markus,

Sorry for the long delay in replying to this thread but I do want to make
sure I'm 100% clear on what you've told me.

So once the ppi surveys that have been converted to XML have been merged
into ppi-uploader, for each instance of Mifos X to have access to the PPI
surveys a user simply needs to run download and run the ppi-uploader tool
acoording to the instructions in the READme: https://github.com/ope
nMF/ppi-uploader/blob/master/README.md

All the PPI surveys in the tool are then available to all tenants on that
instance? Nothing needs to be done to select which tenant or which PPI
surveys you want available?

But this is done per instance, by running the ppi-uploader tool we can't
make them available in the war file so that all the PPIs are available as
part of the release download.

The PPI-uploader doesn't need to be run at upgrades; only if there are new
versions of PPI added in that one wants available.

So this makes the PPIs available in the instance but we still need a
front-end UI for the web app in which to select an available PPI and
capture a survey instance of it, correct?

So for the UI, we need:

1) UI to select an available PPI scorecard for a given country and then
create a survey instance of this (ideally this could be done at different
entities - client, loan)
2) UI to record the instance. For example if in step 1 above I wanted to
create a survey instance of the PH PPI at the client level I now need a
button within the client record to record survey and then display the
scorecard
3) UI to view recorded survey. Now that a survey is recorded, I need to be
able to view that recorded survey from the client record and see the
date/time stamp/version. Is the date/version all recorded in background
able to to be displayed.

Now I have some other questions regarding the flexibility of the
surveys/SPM framework and how it relates to data tables. Is the surveys
framework only for pre-defined scorecards like PPI, IRIS, MPAT, UN SDGs,
etc? Or is it also to create brand new "surveys".

My first question would be this. If I want to create a survey from scratch
(i.e. a completely unique 15-question business plan survey) should I do
this via a Data Table or should I use your surveys framework. If the
latter, should the surveys framework be used to define a question bank (of
multiple question types - free-form, text, multi-select, etc.) and then
from this question bank, create a survey (i.e. give it a title, select
questions) and then save as a survey). If this is all possible, I want to
work with volunteers to finalize the wireframes Nayan worked on and
implement this survey wizard to create surveys powered by the Surveys
Framework.

Thanks,

Ed

Re: Please help evaluate Fineract's readiness for graduation

[Jim Jagielski]

Can you add Write access for my cwiki account: Jim Jagielski, j...@apache.org

Thx
> On Feb 15, 2017, at 11:20 AM, Myrle Krantz  wrote:
> 
> Hello Fineracters,
> 
> I believe we've made enough progress to start the process of graduation.
> 
> Because I believe that we are ready for graduation, I've created a draft
> "Graduation Resolution"
> 
> 
> https://cwiki.apache.org/confluence/display/FINERACT/Graduation+Resolution
> 
> Please review especially the following points:
> * the proposed list of initial members, (I want verification from *every*
> *initial* *member*)
> * their associations, and
> * the proposed chair of the PMC. (Myrle Krantz)
> 
> I've adjusted the Maturity Evaluation.  Anywhere that I changed the
> estimation of maturity, I removed people's approval, so please check me and
> add your name back if you agree with the changed evaluation.  When you're
> looking at the maturity evaluation, you'll see that we aren't perfect.  I
> do not believe the incubator provides us value in addressing the remaining
> issues, so I'm not treating them as blockers for graduation.
> 
> https://cwiki.apache.org/confluence/display/FINERACT/Maturity+Evaluation
> 
> Once changes and discussions have settled down, and once we have a final
> list of initial members, I will call a vote on submitting our graduation to
> the incubator.  My goal is that our graduation resolution be submitted to
> the ASF board by the March board meeting.
> 
> Greets,
> Myrle
> 
> 
> On Wed, Feb 15, 2017 at 1:32 AM, Ed Cable  wrote:
> 
>> Just doing a check-in as to where we stand.
>> 
>> Nazeer has been addressing some of the outstanding points and has recently
>> posted some additional release management documentation which can be viewed
>> at https://cwiki.apache.org/confluence/pages/viewpage.
>> action?pageId=67640333
>> 
>> I have pushed the changes to the Apache Fineract website github repo and
>> these have been merged the but the website is not reflecting the edits I
>> made.
>> 
>> Nazeer has requested feedback on the Findbugs Implementation he has ready
>> go go.
>> 
>> 2 active threads are being discussed related to security and backwards
>> compatibility.
>> 
>> We are also evaluating a couple additional committers and will soon be
>> ready to call for graduation if our mentors too fee we are ready.
>> 
>> Ed
>> 
>> 
>> 
>> On Fri, Jan 27, 2017 at 10:14 AM, Jim Jagielski  wrote:
>> 
>>> Makes sense.
 On Jan 25, 2017, at 10:52 PM, Shaik Nazeer >> confluxtechnologies.com> wrote:
 
 Instead of modifying Fineract website on every Fineract releases, can
>> we
>>> link required details to Fineract wiki pages?
 For example latest release details can be found at
>>> https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders
 
 Thanks,
 Nazeer
 -Original Message-
 From: Markus Geiß [mailto:mge...@mifos.org]
 Sent: 26 January 2017 01:55
 To: Ed Cable
 Cc: dev (dev@fineract.incubator.apache.org)
 Subject: Re: Please help evaluation Fineract's readiness for graduation
 
 Hey Ed,
 
 the Apache Fineract website is a github repo you'll find at Apache's
>>> github mirror.
 
 Simply fork it, create a new branch, do the needed changes and send a
>> PR.
 
 Best wishes,
 
 Markus Geiss
 Chief Architect
 RɅĐɅЯ, The Mifos Initiative
 
 On Jan 24, 2017 15:58, "Ed Cable"  wrote:
 
> Markus,
> 
> Nazeer is continuing to work on addressing the areas of concern
> related to QU10, QU40, and RE50.
> 
> Could you provide me access to the Apache Fineract website to address
> CO10 and then for CS10 do we want that on the Apache Fineract website
> or the wiki?
> 
> Thanks,
> 
> Ed
> 
> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski 
>> wrote:
> 
>> Agreed.
>> 
>>> On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik 
>> wrote:
>>> 
>>> On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable  wrote:
 Could our Apache Fineract mentors please provide some guidance on
 a
>> couple
 of the areas we need to improve upon:
 
 QU10 "*The project is open and honest about the quality of its
>> code.
 Various levels of quality and maturity for various modules are
 natural
>> and
 acceptable as long as they are clearly communicated." -*
 
 Do you have any other projects you could point to that have strong
 transparent measures of quality and maturity clearly available We
 want
>> to
 follow best practices and adopt similar to display at
 http://fineract.incubator.apache.org
>>> 
>>> Regular deployment of tools like Findbugs is a good indication that
>>> you
>> take
>>> this requirement 

Re: [Fineract] Maturity Evaluation - Quality - PMD & Findbugs integration

[Jim Jagielski]

All good. +1
> On Feb 14, 2017, at 7:30 AM, Shaik Nazeer 
>  wrote:
> 
> Hi all,
> 
> 
> 
> We are planning to integrate 'PMD' and 'Findbugs' gradle plugins as part of
> Fineract build script(s) to maintain the code quality. I feel there
> shouldn't be any licensing issue as these two are used only while building
> the code and these jars will not be included in final war file. Please let
> me know your opinion on this.
> 
> 
> 
> Note: Initial setup will be done to ignore the failures as we need to spend
> some time resolve them. Once existing failures are resolved, we will enable
> to fail the build in case of any error.
> 
> 
> 
> Thanks,
> 
> Nazeer
> 

Re: [Fineract] Maturity Evaluation - Quality - PMD & Findbugs integration

[Myrle Krantz]

+1  I agree this is the best approach Nazeer.

-Myrle

On Tue, Feb 14, 2017 at 1:30 PM, Shaik Nazeer <
nazeer.sh...@confluxtechnologies.com> wrote:

> Hi all,
>
>
>
> We are planning to integrate 'PMD' and 'Findbugs' gradle plugins as part of
> Fineract build script(s) to maintain the code quality. I feel there
> shouldn't be any licensing issue as these two are used only while building
> the code and these jars will not be included in final war file. Please let
> me know your opinion on this.
>
>
>
> Note: Initial setup will be done to ignore the failures as we need to spend
> some time resolve them. Once existing failures are resolved, we will enable
> to fail the build in case of any error.
>
>
>
> Thanks,
>
> Nazeer
>
>

Re: Please help evaluate Fineract's readiness for graduation

[Myrle Krantz]

Hello Fineracters,

I believe we've made enough progress to start the process of graduation.

Because I believe that we are ready for graduation, I've created a draft
"Graduation Resolution"


https://cwiki.apache.org/confluence/display/FINERACT/Graduation+Resolution

Please review especially the following points:
* the proposed list of initial members, (I want verification from *every*
*initial* *member*)
* their associations, and
* the proposed chair of the PMC. (Myrle Krantz)

I've adjusted the Maturity Evaluation.  Anywhere that I changed the
estimation of maturity, I removed people's approval, so please check me and
add your name back if you agree with the changed evaluation.  When you're
looking at the maturity evaluation, you'll see that we aren't perfect.  I
do not believe the incubator provides us value in addressing the remaining
issues, so I'm not treating them as blockers for graduation.

https://cwiki.apache.org/confluence/display/FINERACT/Maturity+Evaluation

Once changes and discussions have settled down, and once we have a final
list of initial members, I will call a vote on submitting our graduation to
the incubator.  My goal is that our graduation resolution be submitted to
the ASF board by the March board meeting.

Greets,
Myrle


On Wed, Feb 15, 2017 at 1:32 AM, Ed Cable  wrote:

> Just doing a check-in as to where we stand.
>
> Nazeer has been addressing some of the outstanding points and has recently
> posted some additional release management documentation which can be viewed
> at https://cwiki.apache.org/confluence/pages/viewpage.
> action?pageId=67640333
>
> I have pushed the changes to the Apache Fineract website github repo and
> these have been merged the but the website is not reflecting the edits I
> made.
>
> Nazeer has requested feedback on the Findbugs Implementation he has ready
> go go.
>
> 2 active threads are being discussed related to security and backwards
> compatibility.
>
> We are also evaluating a couple additional committers and will soon be
> ready to call for graduation if our mentors too fee we are ready.
>
> Ed
>
>
>
> On Fri, Jan 27, 2017 at 10:14 AM, Jim Jagielski  wrote:
>
> > Makes sense.
> > > On Jan 25, 2017, at 10:52 PM, Shaik Nazeer  > confluxtechnologies.com> wrote:
> > >
> > > Instead of modifying Fineract website on every Fineract releases, can
> we
> > link required details to Fineract wiki pages?
> > > For example latest release details can be found at
> > https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders
> > >
> > > Thanks,
> > > Nazeer
> > > -Original Message-
> > > From: Markus Geiß [mailto:mge...@mifos.org]
> > > Sent: 26 January 2017 01:55
> > > To: Ed Cable
> > > Cc: dev (dev@fineract.incubator.apache.org)
> > > Subject: Re: Please help evaluation Fineract's readiness for graduation
> > >
> > > Hey Ed,
> > >
> > > the Apache Fineract website is a github repo you'll find at Apache's
> > github mirror.
> > >
> > > Simply fork it, create a new branch, do the needed changes and send a
> PR.
> > >
> > > Best wishes,
> > >
> > > Markus Geiss
> > > Chief Architect
> > > RɅĐɅЯ, The Mifos Initiative
> > >
> > > On Jan 24, 2017 15:58, "Ed Cable"  wrote:
> > >
> > >> Markus,
> > >>
> > >> Nazeer is continuing to work on addressing the areas of concern
> > >> related to QU10, QU40, and RE50.
> > >>
> > >> Could you provide me access to the Apache Fineract website to address
> > >> CO10 and then for CS10 do we want that on the Apache Fineract website
> > >> or the wiki?
> > >>
> > >> Thanks,
> > >>
> > >> Ed
> > >>
> > >> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski 
> wrote:
> > >>
> > >>> Agreed.
> > >>>
> >  On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik 
> > >>> wrote:
> > 
> >  On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable  wrote:
> > > Could our Apache Fineract mentors please provide some guidance on
> > > a
> > >>> couple
> > > of the areas we need to improve upon:
> > >
> > > QU10 "*The project is open and honest about the quality of its
> code.
> > > Various levels of quality and maturity for various modules are
> > > natural
> > >>> and
> > > acceptable as long as they are clearly communicated." -*
> > >
> > > Do you have any other projects you could point to that have strong
> > > transparent measures of quality and maturity clearly available We
> > > want
> > >>> to
> > > follow best practices and adopt similar to display at
> > > http://fineract.incubator.apache.org
> > 
> >  Regular deployment of tools like Findbugs is a good indication that
> >  you
> > >>> take
> >  this requirement seriously.
> > 
> > > *QU30: The project provides a well-documented channel to report
> > >>> security
> > > issues, along with a documented way of responding to them.*
> > >
> > > Currently we just link 

[jira] [Updated] (FINERACT-363) Penalty to be attached/updated to a loan account which was created when a loan product had no penalty/penalty with different amount

[Edward Cable (JIRA)]

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

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

> Penalty to be attached/updated to a loan account which was created when a 
> loan product had no penalty/penalty with different amount 
> 
>
> Key: FINERACT-363
> URL: https://issues.apache.org/jira/browse/FINERACT-363
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Mexina Daniel
>Assignee: Markus Geiss
>  Labels: p1
>
> 1. Create a loan product without overdue charges (penalty) in Admin -> 
> Product -> Loan Product -> Create Loan Product
> 2. Apply a loan account of that loan product to a client at Clients -> View 
> Client -> New Loan
> 3. Approve a loan,  disburse and make few repayments
> 4. Then create a charge which is overdue (is penalty) in Admin -> Products -> 
> Charges -> Create Charge
> 5. Go to that loan product and attach an overdue charge
> What happens:
> The applied penalty is also attached to that loan which was created before 
> this update
> Expected:
> The loan account should not be updated if it was created before the change, 
> the penalty should be applied to loan accounts that will be applied after 
> update of loan product.
> 6. Update a penalty and change it's amount
> What happens:
> All loan accounts that the penalty is applied, the amount of the penalty will 
> also change.
> Expected:
> The amount of the penalty should not change to the loan accounts that  were 
> attached before the update of the penalty.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-362) Configure Penalty Charge depending on loan's interest rate

[Edward Cable (JIRA)]

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

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

> Configure Penalty Charge depending on loan's interest rate
> --
>
> Key: FINERACT-362
> URL: https://issues.apache.org/jira/browse/FINERACT-362
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>  Labels: p2
>
> Our business requirement is to charge penalties for unpaid overdued 
> installments as follows:
> "Every overdue day, charge (installment capital) * (daily interest rate * 
> 1.5)"
> In other words, this means to penalize the overdue by charging a 50% more of 
> the agreed interest over the due capital. 
> To solve this, a new Charge Calculation type could be created. It should be 
> something like "% Amount of the installment * Annual nominal interest rate / 
> 100". 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (FINERACT-312) For Loan with interest recalculation periodic accrual with respect to current date is not getting modified after repayment in Transaction page

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain reassigned FINERACT-312:
-

Assignee: Shaik Nazeer Hussain  (was: Markus Geiss)

> For Loan with interest recalculation periodic accrual with respect to current 
> date is not getting modified after repayment in Transaction page
> --
>
> Key: FINERACT-312
> URL: https://issues.apache.org/jira/browse/FINERACT-312
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>  Labels: p1
> Attachments: 35.png, 36.png, 37.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2119
> Original Description:
> 1. Create a loan product with following datasets:
> Principal: 1, no. of Installments: 12, repaid every 1 month, Nominal 
> interest rate: 1%pm,Amortization: Equal installments, Interest Method: 
> Declining Balance, Interest Calculation Period: Same as repayment 
> period,Repayment Strategy:RBI (India),Recalculate Interest: Yes,Advance 
> payments adjustment type: Reduce number of installments, Pre-closure interest 
> calculation rule: Calculate till pre closure date, Interest recalculation 
> compounding on:None, Frequency for recalculate Outstanding Principal: Same as 
> repayment period, with accounting enabled for periodic accrual.
> 2. Submit new loan application for a client on 01 March 2015 approve and 
> disburse on same date.
> 3. Click on Admin -> system -> Scheduler job - run scheduler job "Add 
> Periodic Accrual Transactions".
> 4. Navigate back to Transactions page and verify the accrued interest as on 
> current date.
> 5. Make first repayment on exact due date then verify the transaction page 
> the accrued interest as on current date is not modified.
> > The accrued interest as on current date is not getting modified even after 
> > multiple repayments. 
> Please refer the screen shot attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-312) For Loan with interest recalculation periodic accrual with respect to current date is not getting modified after repayment in Transaction page

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on FINERACT-312:
-

GitHub user satish-conflux opened a pull request:

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

FINERACT-312 : For Loan with interest recalculation periodic accrual with 
respect to current date is not getting modified after repayment in Transaction 
page.



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

$ git pull https://github.com/satish-conflux/incubator-fineract FINERACT-312

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

https://github.com/apache/incubator-fineract/pull/286.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 #286


commit 7ceb68fec9adfbb58cb916a7077d01b21794172f
Author: satish-conflux 
Date:   2017-02-15T12:52:09Z

FINERACT-312 : For Loan with interest recalculation periodic accrual with 
respect to current date is not getting modified after repayment in Transaction 
page




> For Loan with interest recalculation periodic accrual with respect to current 
> date is not getting modified after repayment in Transaction page
> --
>
> Key: FINERACT-312
> URL: https://issues.apache.org/jira/browse/FINERACT-312
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: 35.png, 36.png, 37.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2119
> Original Description:
> 1. Create a loan product with following datasets:
> Principal: 1, no. of Installments: 12, repaid every 1 month, Nominal 
> interest rate: 1%pm,Amortization: Equal installments, Interest Method: 
> Declining Balance, Interest Calculation Period: Same as repayment 
> period,Repayment Strategy:RBI (India),Recalculate Interest: Yes,Advance 
> payments adjustment type: Reduce number of installments, Pre-closure interest 
> calculation rule: Calculate till pre closure date, Interest recalculation 
> compounding on:None, Frequency for recalculate Outstanding Principal: Same as 
> repayment period, with accounting enabled for periodic accrual.
> 2. Submit new loan application for a client on 01 March 2015 approve and 
> disburse on same date.
> 3. Click on Admin -> system -> Scheduler job - run scheduler job "Add 
> Periodic Accrual Transactions".
> 4. Navigate back to Transactions page and verify the accrued interest as on 
> current date.
> 5. Make first repayment on exact due date then verify the transaction page 
> the accrued interest as on current date is not modified.
> > The accrued interest as on current date is not getting modified even after 
> > multiple repayments. 
> Please refer the screen shot attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Wrong Interest calculation

[mexina]

Hi Zayyad

Thank you for the clarification.
The workaround worked

Regards

"Zayyad A. Said"  wrote:

>
>Mexina,
>
>The issue is you are trying to calculate monthly interest with weekly 
>repayment schedules.
>
>I have seen this as well and the workaround we have been using is to divide 
>the monthly interest by 4 and then multiply by 52 to get annual rate.
>
>Configure the product with interest per year then see if you will get right 
>interest using weekly schedules.
>
>Regards,
>
>Zayyad A. Said
>
>Sent from Samsung tablet
>
>Mexina Daniel  wrote:
>
>Hi Santosh
>
>For what i know
>
>If Principal  = 50,000, interest = 3% for month
>This means the interest charged for one month is 1500 and for 3 months 
>it will be 4500.
>
>Now in Mifos: when you configure the same principal and interest but 
>repaid every week for 12 weeks (= 3months) it gives total interest 4,154.
>
>The interest for 1 week should be 375 but the system says it is 346 ( 
>gives 4154 after 12 repayment)
>
>
>
>On 02/14/2017 04:26 PM, Santosh Math wrote:
>> Hi Mexina,
>>
>> Could you give me the formula which you are using to calculate interest?
>>
>>
>>
>> On Feb 14, 2017 6:38 PM, "Mexina Daniel"  wrote:
>>
>>> Hi Santosh
>>>
>>> I did check it with "Currency multiple of" 1, it still gives wrong interest
>>>
>>> https://demo.openmf.org/#/viewloanaccount/625
>>>
>>>
>>> When you configure loan term in months and repaid every 1 month it give
>>> correct interest with both "Currency multiple of" 1 and "Currency multiple
>>> of" 100.
>>>
>>> Regards
>>>
>>> On 02/14/2017 01:40 PM, Santosh Math wrote:
>>>
 Hi Mexina,

 I think  you set 'Currency in Multiple of ' 100 and it is rounding off to
 nearest 100th value. Check it again with 'Currency in Multiple of' as 1.

 https://demo.openmf.org/#/editloanproduct/144

 On Tue, Feb 14, 2017 at 3:36 PM, Mexina Daniel 
 wrote:

 Hi dev!
> When you apply a loan and configure loan term 12 weeks, number of
> repayment 12 and repaid every 1 week, the system wrongly calculate
> interest
>
> I reproduced this in https://demo.openmf.org/#/viewloanaccount/624
>
> Am i setting it wrong somewhere?
>
> Thank in advance
>
> --
> Mexina M Daniel
> Lead Software Developer
> Research & Development
>
> Tel:+255 222 618 511 | Mob: +255 712 110 791
>
> Singo Africa Limited
> Block G,Mbezi Beach B| 7 Nakawale Road| P.O.Box 78908| 14121 Dar es
> Salaam
>
> singo.co.tz
>
> Lets grow together
>
>
>
>>> --
>>> Mexina M Daniel
>>> Lead Software Developer
>>> Research & Development
>>>
>>> Tel:+255 222 618 511 | Mob: +255 712 110 791
>>>
>>> Singo Africa Limited
>>> Block G,Mbezi Beach B| 7 Nakawale Road| P.O.Box 78908| 14121 Dar es Salaam
>>>
>>> singo.co.tz
>>>
>>> Lets grow together
>>>
>>>
>
>-- 
>Mexina M Daniel
>Lead Software Developer
>Research & Development
>
>Tel:+255 222 618 511 | Mob: +255 712 110 791
>
>Singo Africa Limited
>Block G,Mbezi Beach B| 7 Nakawale Road| P.O.Box 78908| 14121 Dar es Salaam
>
>singo.co.tz
>
>Lets grow together
>

[jira] [Assigned] (FINERACT-371) Make gradle callable from the top level directory.

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain reassigned FINERACT-371:
-

Assignee: Shaik Nazeer Hussain  (was: Markus Geiss)

> Make gradle callable from the top level directory.
> --
>
> Key: FINERACT-371
> URL: https://issues.apache.org/jira/browse/FINERACT-371
> Project: Apache Fineract
>  Issue Type: Wish
>Reporter: Myrle Krantz
>Assignee: Shaik Nazeer Hussain
>Priority: Minor
>
> Relevant e-mails:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201612.mbox/%3CCA%2BULb%2BvcXGe5C%2ByiXdGS2gTD3vnpcs1e%3DoW5D6hffLSt%2BmOn0A%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (FINERACT-346) Reinvesting of Recurring deposit is not working as expected

[Santosh Math (JIRA)]

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

Santosh Math commented on FINERACT-346:
---

I tested it on 16.12.01.RELEASE. The above issue doesn't exist. 

> Reinvesting of Recurring deposit is not working as expected
> ---
>
> Key: FINERACT-346
> URL: https://issues.apache.org/jira/browse/FINERACT-346
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1-confirm
> Attachments: Scr-411.png, Scr-412.png, Scr-413.png, Scr-414.png, 
> Scr-416.png, Scr-417.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1587
> Original Description:
> 1. Create a Recurring deposit account for a client on 01 June 2014, term is 4 
> months repaid every month -> Approve and disburse on same date.
> 2. Make Deposits on 01 June, 01 July, 01 August and 01 September -> Click on 
> calculate and post interst.
> 3. Also run the scheduler job "Update Deposit Accounts Maturity details" -> 
> Navigate back to the Recurring deposit acount page -> Click on Close button.
> 4. In Close account page enter valid inputs and in action dropdown select 
> Reinvest as option -> Click on save button.
> The existing account got closed and the new Recurring deposit account got 
> created with the balance = closed recurring deposit account.
> > Not able to perform any actions in the newly created Recurring deposit 
> > account.
> > In Savings account over view page the amount displayed for the newly 
> > created Recurring deposit account is twice the amount than closed Recurring 
> > deposit account, (In RD account after reinvesting, the old account get 
> > closed and the new account with different account ID get created with the 
> > initial deposited amount = matured amount in previous account.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (FINERACT-346) Reinvesting of Recurring deposit is not working as expected

[Santosh Math (JIRA)]

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

Santosh Math closed FINERACT-346.
-
Resolution: Fixed

> Reinvesting of Recurring deposit is not working as expected
> ---
>
> Key: FINERACT-346
> URL: https://issues.apache.org/jira/browse/FINERACT-346
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1-confirm
> Attachments: Scr-411.png, Scr-412.png, Scr-413.png, Scr-414.png, 
> Scr-416.png, Scr-417.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1587
> Original Description:
> 1. Create a Recurring deposit account for a client on 01 June 2014, term is 4 
> months repaid every month -> Approve and disburse on same date.
> 2. Make Deposits on 01 June, 01 July, 01 August and 01 September -> Click on 
> calculate and post interst.
> 3. Also run the scheduler job "Update Deposit Accounts Maturity details" -> 
> Navigate back to the Recurring deposit acount page -> Click on Close button.
> 4. In Close account page enter valid inputs and in action dropdown select 
> Reinvest as option -> Click on save button.
> The existing account got closed and the new Recurring deposit account got 
> created with the balance = closed recurring deposit account.
> > Not able to perform any actions in the newly created Recurring deposit 
> > account.
> > In Savings account over view page the amount displayed for the newly 
> > created Recurring deposit account is twice the amount than closed Recurring 
> > deposit account, (In RD account after reinvesting, the old account get 
> > closed and the new account with different account ID get created with the 
> > initial deposited amount = matured amount in previous account.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (FINERACT-334) Cashier can still make cash transactions even if there is not enough money allocated.

[Santosh Math (JIRA)]

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

Santosh Math updated FINERACT-334:
--
Labels: p1  (was: p1-confirm)

> Cashier can still make cash transactions even if there is not enough money 
> allocated.
> -
>
> Key: FINERACT-334
> URL: https://issues.apache.org/jira/browse/FINERACT-334
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: cash_issue1.jpg
>
>
> Reported by Teddhy Bamba https://mifosforge.jira.com/browse/MIFOSX-2783
> Original Description:
> In cash management, we need to allocate money to cashier before starting 
> transactions. however, using the mifosx 16.05.01 you can easilly make 
> transactions when there is no allocation or not enough money allocated 
> without any constraint... This is a critical organisational and security 
> issue.
> The net cash amount from teller should not be Negative.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

RE: Please help evaluation Fineract's readiness for graduation

[Markus Geiß]

Hey Sendoro,

good question. ; o)

We are following the Semantic Version paradigm (http://semver.org/). Given we 
are usually also release new features and not only bugfixes within a release, 
we increase Y in favor of Z. If we'd create a bug fix only release with no 
changes to the API we'd increase Z.

With graduation we will set X to 1, this would also indicate that following 
1.y.z releases won't break because of incompatible API changes.

We were in need to change a lot internally to meet all policies and regulations 
at ASF, so we decided to run 0.y.z during incubation.

Hope this helps. ; o)

Cheers

Markus

-Original Message-
From: send...@singo.co.tz [mailto:send...@singo.co.tz] 
Sent: Wednesday, February 15, 2017 08:56 AM
To: dev@fineract.incubator.apache.org
Cc: Ed Cable 
Subject: Re: Please help evaluation Fineract's readiness for graduation

Dears,

I'm not sure if this is the right thread to ask this question.

So far till today we had been working with Fineract version  x.y.z; whereby, we 
have only touched  x,y i.e. 0.1.0, 0.2.0... and now 0.7.0

While I understand why we haven't touched x, I don't know when we shall touch 
z.  Or rather what is the criteria to touch version .z above?

Though, I thought that  our Fineract application would touch more of "z". Due 
to the level of development it is in.

For example...
- I thought critical bugs which affects core banking functionalities should be 
resolved with emergency priority through patching; and as for versioning, we 
should use the "z" above... and that only new functionalities should touch the 
"y" and "x".

- Also, how many votes are required to push emergence fixes. as for ITIL this 
usually they don't need fully CAB approval. O rather do we have operational 
change approval board... that will approve when what is needed is only "z"?

My apologies if my post is taking you back


Regards
Sendoro







On 2017-02-15 00:32, Ed Cable wrote:
> Just doing a check-in as to where we stand.
> 
> Nazeer has been addressing some of the outstanding points and has 
> recently posted some additional release management documentation which 
> can be viewed at
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=67640
> 333
> 
> I have pushed the changes to the Apache Fineract website github repo 
> and these have been merged the but the website is not reflecting the 
> edits I made.
> 
> Nazeer has requested feedback on the Findbugs Implementation he has 
> ready go go.
> 
> 2 active threads are being discussed related to security and backwards 
> compatibility.
> 
> We are also evaluating a couple additional committers and will soon be 
> ready to call for graduation if our mentors too fee we are ready.
> 
> Ed
> 
> 
> 
> On Fri, Jan 27, 2017 at 10:14 AM, Jim Jagielski 
> wrote:
> 
>> Makes sense.
>> > On Jan 25, 2017, at 10:52 PM, Shaik Nazeer > confluxtechnologies.com> wrote:
>> >
>> > Instead of modifying Fineract website on every Fineract releases, 
>> > can we
>> link required details to Fineract wiki pages?
>> > For example latest release details can be found at
>> https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders
>> >
>> > Thanks,
>> > Nazeer
>> > -Original Message-
>> > From: Markus Geiß [mailto:mge...@mifos.org]
>> > Sent: 26 January 2017 01:55
>> > To: Ed Cable
>> > Cc: dev (dev@fineract.incubator.apache.org)
>> > Subject: Re: Please help evaluation Fineract's readiness for 
>> > graduation
>> >
>> > Hey Ed,
>> >
>> > the Apache Fineract website is a github repo you'll find at 
>> > Apache's
>> github mirror.
>> >
>> > Simply fork it, create a new branch, do the needed changes and send a PR.
>> >
>> > Best wishes,
>> >
>> > Markus Geiss
>> > Chief Architect
>> > RɅĐɅЯ, The Mifos Initiative
>> >
>> > On Jan 24, 2017 15:58, "Ed Cable"  wrote:
>> >
>> >> Markus,
>> >>
>> >> Nazeer is continuing to work on addressing the areas of concern 
>> >> related to QU10, QU40, and RE50.
>> >>
>> >> Could you provide me access to the Apache Fineract website to 
>> >> address
>> >> CO10 and then for CS10 do we want that on the Apache Fineract 
>> >> website or the wiki?
>> >>
>> >> Thanks,
>> >>
>> >> Ed
>> >>
>> >> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski  wrote:
>> >>
>> >>> Agreed.
>> >>>
>>  On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik 
>>  
>> >>> wrote:
>> 
>>  On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable  wrote:
>> > Could our Apache Fineract mentors please provide some guidance 
>> > on a
>> >>> couple
>> > of the areas we need to improve upon:
>> >
>> > QU10 "*The project is open and honest about the quality of its code.
>> > Various levels of quality and maturity for various modules are 
>> > natural
>> >>> and
>> > acceptable as long as they are clearly communicated." -*
>> >
>> > Do you have any other