Mifos Configuration Project
The goal of this project is to implement the functionality described in Improve Mifos Configuration Process desired feature.
Project Team
- Van Mittal-Henkle
- Kimloan Ho
Project Artifacts
- Mifos Configuration Project Stories
- Background information documents _ Design considerations goals amp discussion _ Open Issues
Final Project Status - 22 October 2007
Going forward, work on configuration related stories will be integrated into the general Mifos 1.1 release effort, so no status updates are expected for this page after the 22 October 2007 update.
Weekly Work Summary
22 October
- Move Fiscal Year Configuration data to a separate config file * completed work on this story
15 October
- Move Fiscal Year Configuration data to a separate config file * continued work on this story
08 October
- Move Localization data to a separate config file * completed work on this story
- Move Fiscal Year Configuration data to a separate config file * began work on this story
- Bug fixes for previous configuration stories * resolved issues 1448 & 1449
01 October
- Move Localization data to a separate config file * continued work on this story
24 September
- Move Accounting Rules to a separate config file story * completed work on this story
- Move Fiscal Year Configuration data to a separate config file * deferred because of reprioritization
- Move Localization data to a separate config file * began work on this story
17 September
- Move Accounting Rules to a separate config file story _ implemented initial file based configuration support in Mifos _ initial work moving accounting rules to configuration files and refactoring related code
- Localization/Internationalization scoping * reported on initial investigation of internationalization work
- Move General Ledger code definitions to a separate config file story * deferred
10 September
- Localization/Internationalization scoping * began scoping of internationalization work to support localization of Mifos
- Move General Ledger code definitions to a separate config file story * deferred
- Move Accounting Rules to a separate config file story * reviewed Apache Commons Configuration functionality and planned implementation
3 September
- Custom Fields UI story (Add/Edit) _ completed backend functionality for creating and updating custom fields _ story is now complete
- Move General Ledger code definitions to a separate config file story _ implemented dynamic General Ledger Account creation _ refactored code to eliminate usage of COAIDMapperEntity
27 August
- Custom Fields UI story (Add/Edit) _ implemented UI for editing Custom Fields (UI work now complete) _ continued work on backend functionality for creating and updating custom fields
- Move General Ledger code definitions to a separate config file story * implemented ability to export the Chart of Accounts to XML
17 August
- Custom Fields UI story (Add/Edit) _ completed UI work on Define New Custom Field Screen _ completed UI work on Preview screen
- Move General Ledger code definitions to a separate config file story _ expanded test coverage to cover all financial mappings _ refactored financial action mappings to make it configurable * created a Spring based configuration for financial action mappings
13 August
- Accepted Payment Types UI story * completed this story
- Custom Fields UI story (Add/Edit) * worked on the Define/Edit Additional fields screens
- Move General Ledger code definitions to a separate config file story _ began refactoring of financial action mappings to support configuration _ deferred deciding on a format for specifying financial action to general ledger account mappings
3 August ~~~~~~~~
- Accepted Payment Types UI story _ continued backend work on this story including refactoring existing classes. _ integrated payment type label customization
- Move General Ledger code definitions to a separate config file story * investigated current General Ledger functionality and determined that additional configuration is required to implement this story. Configuration to map financial actions to general ledger accounts will need to be supported.
- Fix for issue 1395 - Exception error when editing a look-up value
27 July
- Custom Fields UI story (View Fields) * completed work on the View Additional Fields for one category page
- Accepted Payment Types UI story * implemented backend functionality to support Accepted Payment Types UI screen
20 July
- continued work on the View Additional Fields for one category page
- worked on defining backend functionality required for Accepted Payment Types UI screens * Note: our initial understanding of the code indicated that backend support was already in place for this story, but it was not. Implementing the story will potentially require database schema modifications along with supporting code. The estimate for this story has been adjusted accordingly (+3 points).
13 July
- Work has begun on both the Custom Fields UI story and the Accepted Payment Types UI story
- implemented a custom tag to support View Additional Fields screen
- View Additional Fields UI screen is functional and complete
- implemented a custom tag to support View Additional Fields defined for one category
- work on View Additional Fields for one category web page is in progress.
- Accepted Payment Types UI screen is functional using stubbed out data
6 July
- completed the Lookup Options UI story
- finalized lookup options UI using most recent UI layout
- completed lookup options validation
- verified correct lookup options page flow and back button behavior
- note: since this functionality has a dependency on the work in progress for java based database upgrades (in order to avoid lookup option ID conflicts), the define lookup value options link has not yet been turned on.
29 June
- changed lookup options UI flow to match new UI
- rewrote unit tests and Action related code for new UI
- wrote unit tests for validation
- worked to get struts based validation working (note: understanding and getting struts based validation working has been more time consuming than expected)
22 June
- implemented UI to update lookup values
- implemented UI to add lookup values
- completed look-up options UI except for struts based validation
- discussed alternative look-up options UI and anticipate completing the look-up options UI story based on the new UI
- reviewed front end and back end work for the custom fields UI story
- fixed a localization bug related to building Mifos in a French locale
15 June
- completed work on lookup value creation and update methods
- created a read-only version of the UI screen including unit tests
- added the Spring framework to the project, initially for localization support
- began work to support localization using external properties files.
- added permissions for lookup value page
- continued work to support lookup value add/update functionality
8 June
- completed initial project scoping and estimates
- code review to understand lookup value related classes, hibernate config and tag libraries.
- updated database schema to support dynamic lookup value creation.
- implemented tests for adding and updating lookup values
- created initial implementation of lookup value creation and update methods (but not yet passing tests)
- cleaned up existing code related to lookup values
- began work on creating the lookup value JSP page and related struts classes