...
- Consolidated notifications
- Customizable rules for consolidation
- Role-based notification rules
- SMS and email notification support
- Administrator customization of notification messages
- Notification messages support tokens(?)
- View history of sent notifications, maybe as an adhoc report (this is a future goal - what is the value of this?)
...
Requirement #1: Consolidated (Meaningful?) notificationsNotifications are email notifications sent to users when requisition statuses are changed or an action is required by the user.
- Enable consolidation of notification messages so the user doesn't receive multiple unwanted notifications
User Scenarios:
Roy or Sophie (the storeroom manager): a user who needs to receive notifications for their facility only - the current notifications are acceptable for this user (email notifications by a status update) this user probably doesn't need consolidated emails
- Problem: the user would prefer SMS or high-level notification for rejection type notifications
- Value: user knows to act on notification immediately
...
- Problem: receive a lot of notifications and can't filter through them to determine what to act on, doesn't help them do their job, ignore notifications because there are so many, they don't receive notifications when it would be helpful for them to receive one - when a requisition hasn't been approved for # of days, hasn't been submitted for # of days
- Value: The user is notified when they have work to do, assists them with their job and prioritizing tasks
- Value: Ability to watch a facility that the user is concerned about, receiving targeted notifications on a facility
...
- Problem: What is the problem this user has with current notifications , if any?
- Value: What is the value we want to provide to for this user?
Question: Does this type of user need to receive notifications?
Requirement #1a: Configurability
- configuring important notification types
- whether to send an SMS or email notification based on the importance of notificationConfiguring which notifications can be consolidated
- Enable selection of which channel to use to send a notification (SMS or email)
- For the first iteration, is it acceptable to have a default configuration for each notification class (listed in Open Question 7 below), and then allow for configurability in a future phase?
- disable Disable notifications for unused services (example: Malawi has stock management but does not use it and could potentially receive stock management notifications that are not used)
- Is this really needed? Can this be customized by roles?
...
- Problem: What is the problem this user has with current notifications, any? What is the problem that we want to solve for this user?
- Value: What is the value we want to provide to this user?
Requirement #2: Role-Based notification rules
Ensure users receive the correct notifications based on their role. User can customize notifications text based on their roles.
User Scenarios:
Roy or Sophie (the storeroom manager): a user who needs to receive notifications for their facility only - the current notifications are acceptable for this user (email notifications by status update) this user probably doesn't need consolidated emails
- Problem: What is the problem this user has with current notifications, any? What is the problem that we want to solve
- for
- Value: What is the value we want to provide to this user?
Raquel or Apu (District Supervisor or has responsibilities for multiple facilities): a user who needs to receive notifications for facilities they supervise - this user receives many notifications and desires consolidation, this user only needs to receive an email notification when an action is required by them (Example: District supervisor who supervises 50 facilities, only wants to see ONE email notification instead of 50, or actually 50*3 for every status change)
- Problem: What is the problem this user has with current notifications, any? What is the problem that we want to solve for this user?
- Value: What is the value we want to provide to this user?
Sulu or Chappie (monitors health of supply chain or views status across multiple facilities): a user who logs in occasionally
- Problem: What is the problem this user has with current notifications, any? What is the problem that we want to solve for this user?
- Value: What is the value we want to provide to this user?
Requirement #3: Support SMS
...
channel as an option for notifications
Configuring SMS and categorizing notifications to be sent via SMS.
Requiring a phone number for a user, and if a phone number doesn't exist then the user would receive an email instead.
...
Requirement #4: Administrator customization of notification messages
- Ability to configure and change the text used on email or SMS notifications template.
Background:
- Notification message text were was drafted in consultation with program managers
- The system is connected to a third party SMS gateway or Email system
Status in eLMIS: Implemented.
Status in OpenLMIS: Partially Implemented. Implementers can change by editing the strings in each service. Values can come from the database.
Priority: High priority for Tanzania, Zanzibar, Zambia
- Must be able to put values from the database (support tokens) when editing text
...