Holidays - Postpone Schedule

Holidays - Postpone Schedule

Release x.x

Current Owners:

Status (Draft, In Review, Stable, Approved): Draft
:depth: 1


Many MFI's need the ability to postpone entire loan repayment schedules for a period of time, due to inclement weather, etc. Mifos will use the existing Add Holidays feature to provide this ability.

User Stories (Epics)

List high level user stories - these will be broken down later into small user stories / user tasks.
csv-table:: Epics:header: "Priority", "Epic Stories", "Section in FR"
:widths: 10, 30, 10

"1", "As an administrator, I want to be able to add a new holiday period and set repayment to postpone entire loan repayment schedule, so that clients will not have repayment during the holiday period", "link to relevant section" "1", "As a loan officer, I want to be able to view a loan repayment schedule for a client, and see that the dates of the repayment schedule do not exist during a holiday period set to postponing to next repayment day", "link to relevant section"


List Goals of feature

  • New repayment rule in Holidays to postpone to next repayment day
  • Postponement applies to any schedule that might be affected (loan repayment, savings deposits, and fees)
  • Specify these holiday periods for either the whole organization or specific branches
  • Original requirements for a similar feature is located here Moratorium Requirements


The following items will not be addressed in this feature:

  • Center-based or group-based holiday periods


Definitions and Terminology

list-table:::widths: 20 40
:header-rows: 1

  • - Term - Definitions
  • - User - User of system

  • Mandatory fields will be preceded by *
  • Links are italicized
  • Buttons are Button

Related Documents

*insert links to related specs here

Sub-Feature Name


Use Cases

Use Case Name





Basic Flow




Alternative Flows

User Stories

Smaller user stories
csv-table:::header: "Priority", "Size", "User Stories"
:widths: 10, 10, 30

"1", "Small", "As a User, I can ... "


Functional Requirements

csv-table:::header: "FR #", "Description", "Comments/Mockups"
:widths: 10, 30, 30

"1.1", "Ex: Add Label ... ", ""


Standard Considerations


csv-table:::header: "Security (Permissions, Roles, and Data Scope)", "Yes/No", "Comments"
:widths: 60, 10, 20

"Does the user need to be in a particular user hierarchy to use this feature?", "", "" "Does the office hierarchy affect use of this feature?", "", "" "Are you using any existing permissions to control this feature?", "", "" "Are you adding any new permissions or changing existing permission to control this feature?", "", "" "Are you using any existing activities to control this feature?" "Are you adding any new activities or changing existing activities to control this feature?" "Are there any special considerations for upgrade scenarios? What will be the default value for new permissions?"

"What will be the default values for default roles in a new installation?"

Impacts to System

csv-table:::header: "Impacts to System", "Yes/No", "Comments"
:widths: 60, 10, 20

"Does this feature affect Bulk Loan Creation? How?" "Does this feature affect Bulk Entry? How?" "Does this feature affect Redo Loans?" "Does this feature affect Undo Loans?"


csv-table:::header: "Globalization/Localization", "Yes/No", "Comments"
:widths: 60, 10, 20

"Will this feature support users localizing data that they enter?" "Does this feature involve any date/time related data, and if so how should conversions be handled?" "Is there currency or other numeric data ? If so does it require any special handling or validation?"


Change Log

csv-table:::header: "Change Log", "Yes/No", "Comments"
:widths: 60, 10, 20

"Do changes to the data that is collected or stored by the new feature have to be fully logged by the system?" "Does the administrator configuring the system need the ability to turn on or off logging for this feature?" "Is the feature currently logged but the structure of the logged records changing?"



Provide any relevant information about reporting requirements for the new features and answer the questions below, providing detail to explain any particular area when necessary.
csv-table:::header: "Reporting", "Yes/No", "Comments"
:widths: 60, 10, 20

"Does the feature affect any existing reports?" "Does the feature require adding any new reports? "



csv-table:::header: "Performance", "Yes/No", "Comments"
:widths: 60, 10, 20

"Will the feature be a high use-case scenario?" "Will the feature have potential for high concurrency?" "Does the feature include complex UI or data gathering logic that will be used by a significant portion of the user base?" "Does the feature contain risks of database connection timeout or ASP page timeout?" "Will the feature contain any bulk insert/update/delete transactions?" "Will the feature contain any caching mechanisms or cache refreshing mechanisms?" "Could the feature result in a large amount of data being sent to the client or between the database and web server?" "Would users on a low bandwidth connection likely face issues with a part of this feature?" "Does the feature affect existing batch jobs or require adding any new batch jobs?"

Setup and Installation


New Installations

csv-table:::header: "New Installations", "Yes/No", "Comments"
:widths: 60, 10, 20

"Will the feature include demo data?" "Does the feature require any data to be gathered at setup runtime?"


Backward Compatibility and Upgrades

csv-table:::header: "Backward Compatibility and Upgrades", "Yes/No", "Comments"
:widths: 60, 10, 20

"Is there any data conversion that needs to be done as part of an upgrade?" "Will customers lose data or will the way existing data is stored change significantly?" "Will another feature, workflow or portion of the data model be deprecated as a result of this new feature?" "Will existing role permissions be changed or impacted by this feature? If so provide details in the security section." "Will existing customers need to learn a new UI process or change the way they use the system as a result of this new feature?"


Hosting Support

csv-table:::header: "Hosting Support", "Yes/No", "Comments"
:widths: 60, 10, 20

"If different user groups are using the same database, are there concerns over the sharing of data related to the feature?" "Are there expected to be performance related issues with having many customers sharing the same hardware in support of this feature?"



csv-table:::header: "Configuration", "Yes/No", "Comments"
:widths: 60, 10, 20

"Does this feature require changes to configuration files?" "If so, is this feature enabled or disabled by default?"

Open Issues


Review and Approvals