Project Resources

Mentor

Nick Gochiashvili

Assigned Contributor

Tengiz Merabishvili

Project Overview

Overview

 

An end-user/administrator should be able to define their own reports (using drag-and-drop/clicks etc.) and without having to understand the internals of the Mifos database tables and columns. The Pentaho report designer cannot be used by end users. So the idea is to give a simpler custom interface for defining “ad-hoc” reports and to run them like any other report.

Background and Business Need

To run any business successfully, one needs insight into the business and that is made easier when one can drill down to the exact information, summarized at the required level and presented in the required format. This will assist in taking the right decisions. And as market scenarios changes very rapidly, Mifos needs to have an Ad-hoc report builder that will help end-users to intuitively build their own reports, rather than work off a set of pre-defined reports.

The Ad-hoc Report Builder will be easy-to-use and will allow user to define reports using UI controls rather than tables and column names.

Deliverables

Project Supporters(s)

Binny Gopinath Sreevas (Conflux Technologies)

Project Details

Assigned contributor for the project will include details of how they plan to implement the feature.  Feel free to supplement as needed with additional child pages of detail. 

Project Status

TBD

Additional Information

Requirements

Use Cases/User Stories

The following use cases is what I have in mind:

a) As an administrator/manager, manage ad hoc reports (create/update/delete etc.) that can be used by other users in the organization. This will involve specifying:

b) As a business user,

Also, it should be possible for an administrator to see the list of ad-hoc reports created by users and then publish these for access for other user roles too.

Managing of ad-hoc reports will have the following user-stories:

-          As a Business User, I want to select the set or sub-set of Entities that will be displayed in this report

For example: set of customers with “Emergency Loans” (Emergency Loans is the name of a loan product here) – we will need to go through the Mifos database schema and identify “entities” that make sense to end users and define these as queries as mentioned above. If multiple entities are selected, then the join criteria should be more or less automatic (in a way – we could say this is hardcoded).