-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
A. For client registration, we can make use of a table "notification" which will have columns as :
user, clientName, seen(default false) and also an extra field "notified"(default false) in the client detail table.
Control Flow:
- After successful registration, an entry will be added in the notification table with the required information.
- Add notifications in the admin dashboard of the table entries which have seen as false.
- Once admin clicks on the bell icon then make seen of the entries as true.
- Check registered client details before loading user dashboard, if client credentials are not null and notified field is false then add notification in the user dashboard that client is verified.
- Once the user clicks on the bell icon then make the notified field as true & delete the entry from the notification table also.
B. For tickets notification, we can make use of "tickets" table which will have columns as:
user, email, message, seen(default false), resolved(default false)
- Whenever the user creates a ticket from the user dashboard then add an entry in the tickets table with all the details.
- Add a table view in the admin dashboard page for the tickets table too as we have right now for user and client. Make the last column resolved as the button to resolve the issue like verify button in the client table.
- Add notification in the admin dashboard for the tickets which have seen as false.
- Change seen value to true once admin clicks on the ticket icon.
- Admin can then send mail to the user regarding the issue and once the issue is resolved then click on the resolved button of the issue in tickets table.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels