[
http://mifosforge.jira.com/browse/MIFOS-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
keithwoodlock updated MIFOS-2428:
---------------------------------
Fix Version/s: (was: Mifos Backlog)
Unscheduled
> Mifos still runs with invalid financial action mappings, causing runtime
> errors
> -------------------------------------------------------------------------------
>
> Key: MIFOS-2428
> URL: http://mifosforge.jira.com/browse/MIFOS-2428
> Project: mifos
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: Release 1.3
> Environment: Platform: All, OS: All
> Reporter: Adam Monsen
> Assignee: mifosdeveloperqueue
> Priority: Major
> Fix For: Unscheduled
>
>
> EXECUTIVE SUMMARY
> If financial action mappings refer to non-existant general ledger accounts,
> confusing runtime exceptions occur.
> STEPS TO REPRODUCE
> * customize chart of accounts as mentioned in the Mifos Configuration Guide,
> changing only FEEPOSTING (in <property name="actionToCreditAccount">) to map
> to
> a nonexistant GL code, for instance, 31307
> * as mentioned in issue 2425, try to define a new fee
> EXPECTED BEHAVIOR
> shown form to add a new fee
> ACTUAL BEHAVIOR
> server error; browser displays "Fatal chart of accounts error: account with
> general ledger code 31307 not found.".
> ADDITIONAL INFORMATION
> This is documented on
> http://www.mifos.org/knowledge/support/deploying-mifos/configuration/guide#creating-your-own-financial-action-mappings
> ... "For Mifos to function correctly, all actions must be mapped to an
> existing
> GL account."
> The failure condition(s) for mapping to non-existant GL codes includes one
> where
> the application appears to function nominally until certain operations are
> performed, such as those mentioned in issue 2425, issue 2426, and issue 2427.
> Proposed fix:
> * create a new unit test that makes sure Mifos enforces valid financial action
> mappings
> * create a startup check in FinancialActionInitializer to ensure that
> financial
> action mappings refer to extant gl codes, crashing Mifos if a mapping is
> incorrect
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
