| Page Properties | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- 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)
- 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)
- All emergency requisitions are not consolidated, but sent as the status is changed (this is current behavior)
- 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)
Example for authorizer
Header: Requisition Status update
Dear divo1:
This email is informing you that 20 Regular requisitions for EPI at Depósito Distritial Cuamba have been authorized.
Please login to see the requisitions.
Hyperlink to OpenLMIS requisitions here
Example for approver that needs to take action
Header: Action Required
Dear psupervisor:
This email is informing you that 20 Regular requisitions for EPI at Depósito Distrital Cuamba are ready for review.
Please login to see the requisitions.
Hyperlink to OpenLMIS requisitions approve here
Option B: Consolidate requisition notifications by facility
- All requisitions are consolidated by facility once daily (user sees facility and list of requisitions that have been changed)
- All requisitions for my supervised facility are consolidated by supervised facility (supervisory node) once daily (user sees supervised facility and list of all requisitions In_approval status)
- Admin can configure Requisitions service to select a facility to consolidate notifications (either by supervised facility or by facility)
Example for approver that needs to take action
Header: Action Required
Dear divo1:
This email is informing you that Regular requisitions at Depósito Distrital Cuamba are ready for review.
Facility A Requisition Status
Facility B Requisition Status
Facility C Requisition Status
Facility D Requisition Status
Please login to see the requisitions.
Hyperlink to OpenLMIS Requisitions approve here
Notifications Service configuration for Requirement #1:
...
- 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)
...