Introduction

Some MFI's span large regions where different branch offices might observe different holidays.  They need the ability to define holidays for specific branch offices in Mifos and be able to set the repayment rule to follow during those holidays.

User Stories

Goals

• Ability to define a holiday for branch offices, all the way up to head office level in the office hierarchy.
• Ability to set a repayment rule for those holidays for schedules to follow, will only apply to the offices that are affected

Non-Goals

The following items will not be addressed in this release:

• Editing the branches or any other details that apply to a holiday that has already been created.
• Deleting holidays already created in Mifos

Definitions and Terminology

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

Related Documents

• Business Requirements - Main:KMBI - Mifos Business Requirements (update link)

Branch Level Holidays

This feature will allow holidays to be defined at the branch level.

Use Cases

Administrator creates a holiday for specific branches.

Actors

•  Administrator

Preconditions

•  None

Basic Flow

1. Administrator navigates to Define new holidays. 
2. Administrator creates a new holiday with a period from one date to another, name of holiday, and repayment rule.
3. Administrator selects branch offices the holiday applies to. 
4. Administrator hits Preview.
5. System displays new holiday with details of the holiday including the branches the holiday applies to 
6. Administrator chooses to Submit.

Post-conditions

• Mifos has new holiday defined for the branches selected.  Only schedules in those branches are affected by the holiday.  They are updated the following day with the repayment rule selected.

Alternative Flows

Administrator edits branches of new holiday during holiday creation.

1. At step 5 of basic flow, Administrator clicks on Edit Holiday to edit details of the holiday and adds or removes branches, and hits Preview again.  Use case continues at step 3 of Basic Flow.

Post-conditions

• Mifos has new holiday defined.
• Schedules only in those branches are affected.

Validations

• Holidays periods cannot be created in the past (either To or From dates must be before current date) - following error message is displayed - Holiday can't be added for current date or dates in the past.

Administrator creates a holiday for an area office.

Preconditions

•  Mifos has been set up with the following office hierarchy - HO > AO > BO

Flow

1. At step 3 of basic flow, Administrator selects an area office to apply a holiday to.  Use case continues at step 4 of Basic Flow.

Post-conditions

• Mifos has new holiday defined for that area office.
• All schedules under the area office are updated the next day with the new holiday change.  This includes all branch offices under the area office.

Validations

• Holidays periods cannot be created in the past (either To or From dates must be before current date) - following error message is displayed - Holiday can't be added for current date or dates in the past.

Administrator creates a new branch office in Area Office 1.

Actors

•  Administrator

Preconditions

•  A holiday has been defined that applies to Area Office 1.

Basic Flow

1. Administrator navigates to Define offices and creates a new branch office with parent Area Office 1. 
2. Administrator chooses to Submit.

Post-conditions

• Any schedules created under the new branch office inherit holidays of its parents.  This would include both holidays defined for the HO, and holidays defined for Area Office 1. 

Administrator moves Branch Office 1 from Area Office 1 to Area Office 2

Actors

•  Administrator

Preconditions

• Branch Office 1 is under Area Office 1 in Mifos office hierarchy.
• There are different holidays defined for Area Office 1 and Area Office 2.
• Branch Office 1 also has a holiday defined just for that office.

Basic Flow

1. Administrator navigates to View offices and edits Branch Office 1. Administrator changes the parent of Branch Office 1 from Area Office 1 to Area Office 2.
2. Administrator chooses to Submit.

Post-conditions

• The next day, all schedules under Branch Office 1 are updated so that changes to schedules due to holidays from Area Office 1 are removed, and new updates are made to schedules based on holidays defined for Area Office 2.
• The holiday changes that stem from holiday attached to Branch Office 1 are still on the schedules in Branch Office 1.

User Stories

Branch Level Holidays Functional Requirements

Updates Across all parts of workflow

New selection of branches in holiday creation

New preview of holiday

New View Holidays

Other Assumptions

QA Considerations

• Existing holidays in the system should automatically apply to Head Office.

Standard Considerations

Security (Permissions, Roles, and Data Scope)

Impacts to System

Globalization/Localization

Logging

Change Log

Reporting

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.

Performance

Setup and Installation

New Installations

Backward Compatibility and Upgrades

Hosting Support

Configuration

Customers

Open Questions and Notes

Review and Approvals