juzershakir / fmb

An application for the FMB (NPO), helping them streamline their day-to-day activities and improve efficiency.

Faiz al-Mawaid al-Burhaniyah (FMB)

A Dawoodi Bohra NPO with one overarching objective: to provide at least one wholesome & nutritious meal a day to every community household.

---

Hosting

This application is hosted here.

Login Credentials (Role: Viewer):
ITS ID:

12345678

Password

12345678

---

Bugs

List of all the bugs that needs to be fixed.

---

Additional Features

List of all upcoming features.

fmb's Issues

Generate Takhmeen Form

A takhmeen PDF form will be generated after a new takhmeen is created of a sabeel with the help of ActiveJob Class.

The form will have the following fields:

1. Name.
2. ITS number.
3. Total Takhmeen amount.
4. Signature (which will be left blank)
5. and some information should default for all forms.

Additional gems redis & sidekiq will be required to accomplish the following task.

An additional attribute will have to be created to the thaali model to store this form in the database.

Email Transaction Receipt

Scenario

After successfully creating a transaction of a thaali, the receipt PDF form is generated and emailed to the corresponding sabeels' email address.

The form will have the following details:

1. Name
2. ITS Number
3. Transaction Amount (in written form)
4. Digital Sign

redis & sidekiq will be required to accomplish the following task.

An additional attribute will have to be created to the transaction model to store this form in the database.

Increment CURR_YR value by an Admin

Currently, no user has access to manually increment the value of constant, CURR_YR. This means if the organization wants to start creating takhmeen for next year, they would have to contact the developer to update the value of it.

Possible Solutions

1. One of the solutions is that we could add a button, after clicking it, the value would increment by 1.

The issue with the 1st solution

The problem with this approach is that if the user clicks on it multiple times then the value would increment multiple times too. So we would need some restrictions to this so that it's only able to increment once and not after it.

Clicking back doesn't work after clicking on Edit for visitor

Scenario

1. A visitor visits the show page of any model of the 3 models: sabeel, thaali_takhmeenor transaction.
2. The visitor clicks on Edit button but it redirects them to the same show page with a flash message.
3. Then the visitor clicks on Back button but nothing happens.
4. Then the visitor has to click the Back button again in order for the user to go back in history.

So basically a visitor has to click Back button twice if they click on Edit button once. But then let's say they click the Edit button twice then they have to click the Back button thrice and so on. Do you get the point?

Expected behaviour

The user must be able to go back in history after clicking on the Back button once regardless of how many times the user (visitor) clicks on Edit button.