Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties


Target release3.6
Epic
Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-1094
Document status
Status
titleDRAFT
Document owner
Technical LeadWesley Brown


...

  • Enable consolidation of notification messages so the user doesn't receive multiple unwanted multiple notifications that are not time-sensitive
  • Daily digest of notifications

User Scenarios:

...

  • 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 facilityReceiving summarized notifications for # of requisitions per facility (instead of an individual email notification for each requisition status change at each facility they supervise)

Sulu or Chappie (monitors health of supply chain or views status across multiple facilities): a user who logs in occasionally 

...

  • 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 

...