[
http://mifosforge.jira.com/browse/MIFOS-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukasz Chudy updated MIFOS-2774:
--------------------------------
Status: Verified (was: Resolved)
> No change history entry recorded when an inactive savings account is
> re-activated due to a deposit
> --------------------------------------------------------------------------------------------------
>
> Key: MIFOS-2774
> URL: http://mifosforge.jira.com/browse/MIFOS-2774
> Project: mifos
> Issue Type: Bug
> Components: Savings Account
> Affects Versions: Release 1.4
> Reporter: johnwoodlock
> Assignee: mifosqa
> Fix For: Release E
>
>
> When an inactive savings account gets a deposit it gets reactivated.
> However, a change history record isn't created.
> This happens regardless of whether collection sheet or the savings accounts
> payments page is used.
> Initial impact analysis tech info.
> There are two methods which handle savings deposits... both in SavingsBO
> 1. makePayment(final PaymentData paymentData) by way of
> AccountBO.applyPayment(final PaymentData paymentData)
> 2. deposit(final AccountPaymentEntity payment, final CustomerBO
> payingCustomer)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
