[jira] [Created] (FINERACT-239) Ability to adjust Principal and Interest as a super user
Dayna Harp created FINERACT-239: --- Summary: Ability to adjust Principal and Interest as a super user Key: FINERACT-239 URL: https://issues.apache.org/jira/browse/FINERACT-239 Project: Apache Fineract Issue Type: Wish Reporter: Dayna Harp Assignee: Markus Geiss https://mifosforge.jira.com/browse/MIFOSX-2518 This should allow you to make adjustments on the principal and/or interest balances of a loan account for correction purposes. The adjustment process should always be a voucher transaction not cash and should be fixed by default. *Credit Principal*. This allows you to correct an erroneous posting of disbursement, whether a wrong amount was posted for the disbursement or it was posted to a wrong account. *Debit Principal*. This allows you to correct an erroneous posting of a repayment, whether a wrong amount was posted or it was posted to a wrong account. *Credit Accrual. *This allows you to correct erroneous posting of loan accruals—interest, penalties and charges—to an account or to waive penalties. This is also used to reduce accruals whenever there was a delay in the posting of a repayment. *Debit Accrual.* This allows you to apply loan accruals—interest, penalties and charges—to an account in cases of repayment cancellation. This is particularly necessary if the cancellation occurred after the day that the repayment was posted -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-240) System User Administrations
Dayna Harp created FINERACT-240: --- Summary: System User Administrations Key: FINERACT-240 URL: https://issues.apache.org/jira/browse/FINERACT-240 Project: Apache Fineract Issue Type: Wish Reporter: Dayna Harp Assignee: Markus Geiss https://mifosforge.jira.com/browse/MIFOSX-2185 As a system administrator, I would like to be able to:- * see which user is logged or not logged into Mifos X. ||User Name||Status|| |mifos|Connected| |admin|Connected| |robert|Not Connected| * forcefully logout a logged in user remotely * not be able to edit user credentials plus assigning a role when a user is logged in * see which machine the user is logged in from * restrict users from logging in from multiple computer/devices simultaneously i.e if user A is logged in from PC1, and if he tries to login from PC2, Mifos X should be able to tell the user that he is already login from PC1 and should reject this login unless he logout from PC1 then he can proceed with this login session * enable audit trail to track PC/Device names with user name against any action the user performs in Mifos X e.g Creating a client. a column can be added (pc_name) for this. All this can make administration and tracking of any errors perfect -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-238) Account Entry Closure
Dayna Harp created FINERACT-238: --- Summary: Account Entry Closure Key: FINERACT-238 URL: https://issues.apache.org/jira/browse/FINERACT-238 Project: Apache Fineract Issue Type: Wish Reporter: Dayna Harp Assignee: Markus Geiss Priority: Critical https://mifosforge.jira.com/browse/MIFOSX-2644 When making account closure for a day, the system should reject closing entries if there are some users logged into the system. It should only allow one user with rights to make closing entry to do this else should throw error that users are still logged into the system hence can not close books of accounts. This can be used to make End of days. At this point it should check all wrong journal entry posting and generated reports accounting especially GL Accounts balances against Customer Account balances - Totals should be the same e.g Voluntary Savings GL total = Voluntary Customer Savings total etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FINERACT-236) Savings product configuration changes should affect existing accounts
Dayna Harp created FINERACT-236: --- Summary: Savings product configuration changes should affect existing accounts Key: FINERACT-236 URL: https://issues.apache.org/jira/browse/FINERACT-236 Project: Apache Fineract Issue Type: Bug Reporter: Dayna Harp Assignee: Markus Geiss https://mifosforge.jira.com/browse/MIFOSX-2510 If an institution changes a configuration in either a particular loans or savings product, this change should be applied to already existing accounts created. E.g if during savings product creation, MFI sets Min Balance as 5,000 and after some time decided to change it 10,000 then i think this should not be applied to new accounts created after this change but rather cut across any other existing account. This should apply to loan product configurations. These are some of the ways this can be achieved:- # This product configuration account values like Min Balance, Interest rate etc should not be stored in the account table but rather a pointer can be set to them # When a change is made to a product configuration, in the respective accounts table i.e loan account table or savings account table depending on the product type being modified, changes must be updated accounting like if interest rate or min balance value is change, query should be include when submitting these changes to effect them in the account table, some time like select * from m_savings_account where product_id = (product id being modified), then update the necessary values in the table This should be for :- * Savings Product * Recurring Deposit * Fixed Deposit * Charges -- This message was sent by Atlassian JIRA (v6.3.4#6332)
RE: [VOTE] [FINERACT] 0.4.0-incubating for release
+1 -Original Message- From: Nazeer Shaik [mailto:nazeer1100...@apache.org] Sent: Monday, October 17, 2016 01:31 PM To: dev@fineract.incubator.apache.org Subject: [VOTE] [FINERACT] 0.4.0-incubating for release Hello Fineract community, We have created 0.4.0-incubating release, with the artifacts below up for a vote. *These are the goals of this release:* - Removed hibernate dependency from the Fineract and integrated OpenJPA as default JPA provider - Share the new features that have been developed so far, to give the community a good sense of the upcoming 0.4.0 release *For more information including release notes, please see:* https://cwiki.apache.org/confluence/display/FINERACT/0. 4.0-incubating+Release-+Apache+Fineract This is a *source code tar ball* only release. *** Please download, review and vote by Thu Oct 20, 2016 @ 6pm PST *** *Source Files:* https://dist.apache.org/repos/dist/dev/incubator/fineract/0.4.0-incubating/ *Commit to be voted on:* https://git-wip-us.apache.org/repos/asf?p=incubator-fineract.git;a=commit;h=refs/heads/0.4.0-incubating *Build verification steps can be found at: * Refer 'README.md' in apache-fineract-0.4.0-incubating-src.tar.gz *KEYS file containing PGP Keys we use to sign the release:* https://dist.apache.org/repos/dist/dev/incubator/fineract/KEYS *Note: * - This is a source only release with no binaries, with instructions on how to build/test the application. - We have removed hibernate dependency from running integration tests. Now Fineract is integrated with OpenJPA. To help in tallying the vote, members please be sure to indicate "(binding)" with your vote. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thank you, Nazeer
Re: [VOTE] [FINERACT] 0.4.0-incubating for release
+1
