> QUESTION 1 > ========== > The following rule exists in the file: > FiscalCalendarRules.ScheduleTypeForMeetingOnHoliday=same_day > > Is this setting needed given that holiday handling is now done via > the UI and the user can specify the repayment rule for each holiday?
I don't see any non-test usage of the FiscalCalendarRules.getScheduleTypeForMeetingOnHoliday method which returns this config value. So at least as a first pass it does not look like this is being used any more. > QUESTION 2 > =========== > The following rule exists in the file: > FiscalCalendarRules.DaysForCalendarDefinition=30 > > The FS gave this description for this configuration setting: " The > number of days after which the calendar definition for the next year > can be specified." > > Can anyone describe in more detail what this setting does > functionally in Mifos in more detail than the FS? I don't really > understand what it does. I also don't see any non-test usage of this config value in the current code. > QUESTION 3 > ========== > In v1.0 of Mifos, there was a method to set the day of the week that > was considered the start of the working week in the DB. > > According the v1.0 FS " Starting day of the fiscal week should also > be specified. This can be any working/non-working day of the week. > This will be used by reports module to generate weekly reports. By > default, starting day will be Monday" > > I do not see this setting in the default configuration file. Is > there a way to specify this still? Was it explicitly removed because > it doesn't have any impact on Mifos functionality in practice and was > an unused setting? Perhaps there is a disconnect here between the FS and the current config implementation. In the current implementation the first day listed in the FiscalCalendarRules.WorkingDays config entry is used as the starting day of the fiscal week. However, this usage does not allow for the start of the fiscal week to be a non-working day. In order to support non-working days, this would need to be separated out into a new configuration entry. We'll do a little more investigation into #1 & #2 and let us know if we need a new config value for the start of the fiscal week. --Van ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
