[
http://mifosforge.jira.com/browse/MIFOS-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58550#action_58550
]
jbrewster commented on MIFOS-2956:
----------------------------------
have tested this while verifying MIFOS-3117
> RegenerateSchedule batch job ignores closed clients
> ----------------------------------------------------
>
> Key: MIFOS-2956
> URL: http://mifosforge.jira.com/browse/MIFOS-2956
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs
> Affects Versions: Release 1.5
> Reporter: jbrewster
> Assignee: johnwoodlock
> Priority: Major
> Fix For: Shamim D
>
>
> When a client is closed/blacklisted and is part of a center that has its
> meeting day moved, the RegenerateMeeting batch job ignores the closed client.
> The fallout from that is the closed client stays with the previous meeting
> ID, which causes the batch job to fail to delete the old meeting since one or
> more clients still have that meeting ID.
> As Adam noted, the workaround was: "We manually changed the meeting ids for
> customer meetings for the two closed/blacklisted customers to the meeting ids
> in customer_meeting.UPDATED_MEETING_ID."
> This issue was identified while troubleshooting SECDEP customer issue where
> center was not being updated with new schedules - (see MIFOSADMIN-31)
--
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
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
