...
...
...
...
...
...
| Table of Contents |
|---|
Identify
| Document Owner | |
|---|---|
| Document Status | Draft |
| Intern Working on this Project | |
| Mentors | |
| Source Code | https://github.com/ad-os/incubator-fineract |
| Documentation | Notification API user Guide |
...
- Enable generic way of sending notifications - these notifications should be capable of being delivered via the Community App, via the Android app for field officers or Android self-service app.
Goal
- To allow the user to directly act upon the alert directly from the notification (i.e. approve a client). This is what actionable means.
Approach for designing a generic notification system
...
2. notification_mapper :- The table maps the id of generated notification with the id of an a user for whom it was generated.
| id | notification_id | user_id | is_read | created_at |
|---|
id :- The id of mapped notification.
notification_id :- It contains the id of a notification which has to be mapped to an a user. This is comes coming from the notification_generator table.
user_id :- It contains the id of an a user for whom the notification is mapped.
...
created_at :- It contains the date and time of the mapped notification.
Notification Delivery
- For each REST request which the UI makes the server will send back a response header for e.g 'X-Notification-Refresh' with each response containing the value of either true or false depending upon whether new notifications are present on the server or not.
- If no REST request has been made for certain time interval then a new REST request is made to check whether there are new notifications on the server or not.
JIRA Tasks
- The JIRA task corresponding to the first part in designing of notification module is present at this link.
| Table of Contents |
|---|