[
http://mifosforge.jira.com/browse/MIFOS-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56870#action_56870
]
jbrewster commented on MIFOS-1488:
----------------------------------
Here is a comment from Ingrid K. on this issue:
I agree that it's not a good practice to keep changing the system time. Like a
timesheet, for record-keeping purposes, any entry should reflect actual, and
not ideal time.
My suggestion is to add 2 fields to the table (if they are not already in
place) -
1. add a field to the table that records the real system time (i.e. date()).
Then, if the actual input time is outside the parameter of the validation rule,
the GUI should still display the message "Please specify a valid date -- Date
of transaction must be between the last meeting date and today.", but this
could be done in a dialogue box with the option to Continue or Cancel. If the
user clicks on Continue,
2. the record must be flagged (possibly by adding a boolean value into a field
called e.g. 'late_entry').
This way exception reports can be printed to find these flagged records.
Unfortunately I don't think much can be done about
"1/ If bulk entry data for the previous meeting is not entered before the next
meeting date-- then the collection sheet information will be incorrect for the
next meeting (ie, the collection sheet will say that customers owe both *last*
payment amount and the current payment amount).",
except for maybe adding a message to the GUI, or any reports, indicating that
the account reflects the information available at (last date of entry)." If
user is given the choice to continue, the record could be flagged (possibly by
adding a boolean value into a field called e.g. 'late_entry').
> Allow bulk entry prior to the last meeting
> ------------------------------------------
>
> Key: MIFOS-1488
> URL: http://mifosforge.jira.com/browse/MIFOS-1488
> Project: mifos
> Issue Type: New Feature
> Components: Collection Sheet Entry
> Affects Versions: Release 1.0
> Environment: Platform: All, OS: All
> Reporter: bberning
> Assignee: pmqueue
> Priority: Major
> Fix For: Unscheduled
>
>
> Bulk Entry page doesn't allow late collection sheets to be entered easily. If
> the user enters the date for a sheet more than six days old, Mifos gives an
> error - 'must select date between last meeting and today.' To enter the sheet
> Mifos and MySQL have to be stopped, the system date reset and Mifos & MySQL
> restarted.
> For any MFI doing manual data migration, the need to constantly change the
> system date is the BIGGEST impediment to smooth progress. And even after in
> production, loan officers will sometimes bring in sheets older than six days.
> So we have to have a way to relax this requirement. Either extend the
> 'window',
> say to 30 days, or relax it entirely, defaulting to the last meeting, but
> allowing earlier meeting days. This requirement is similar to the Out of
> Scope
> section "Bulk entry Vs Loan schedule independent of meeting schedule"
> http://www.mifos.org/developers/wiki/LoanIndependentOfMeeting/
--
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
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
