Page Comparison

...

1. All requisitions for my supervised facility are consolidated by status once daily (user sees # of requisitions in In_approval status for each of their supervised facilities)All emergency requisitions are not consolidated, but
   1. Admin can configure Requisitions service to select which requisition statuses will be consolidated (this can be through API and does not require admin UI yet)
   2. 1. As an authorizer, I want to see the # of requisitions that have been submitted for my supervised facility, once a day. 
      2. As an approver, I want to see the # of requisitions that are ready to approve for my supervised facility, once a day.
   3. Admin can configure Requisitions service to select which requisition statuses will be consolidated (this can be through API and does not require admin UI yet)
      1. As an administrator I want the flexibility to select one or many requisition statuses to send in one daily digest notification.
   4. All emergency requisitions are not consolidated, but sent as the status is changed (this is current behavior)
   5. All requisitions for my facility are consolidated by status once daily (user sees # of requisitions in each status for their facility instead of individual emails for each status change - lower priority)

   ...

   • Configuring which/how notifications can be consolidated  
   • Configuring time that notifications will be sent (once daily)
   • 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?
   • Manual Resend notifications (future release - out of scope for 3.6)
   • Timebound notifications (future release - out of scope for 3.6)
   • 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?

   • Jira Legacy
     server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5589

   User Scenarios:

   Adam the administrator: an administrator or implementer that needs to configure notifications to send via SMS or email depending on the type or importance of the notification

   ...

   • Ability to configure and change the text used on email or SMS notifications template.
   • Research using RapidPro or another existing service (Team Ona uses RapidPro)
   • Support a more digest-like notification rather than a facility-specific notification (as shown in the example below
   • Must be able to put values from the database (support tokens) when editing text 
   • Admin has ability to view history of notifications (question #2 below)

   ...