ayanova/devdocs/todo.txt

@@ -5,6 +5,23 @@ PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route chang
 
 
 
+
+NOTIFICATION
+____________
+
+todo: //Open question - do we need a priority level for notifications, i.e. if system is having backup issue slightly more important than something run of the mill?
+                        //or, maybe it's an option to popup if this occurs so user can decide if they want to see a red notice or not
+
+todo: //Open question: what to do with failed deliveries?
+                        //we dont' want them piling up but we don't want to just dump them do we?
+                        //it should be only mail ones that fail, not app ones, there's no way for an app delivery to fail as it's just put in a table
+                        //### PLAN if it's an smtp delivery that fails and it's to someone who can be delivered in app then it should send an inapp notification of 
+                            //delivery failure and still delete the smtp delivery
+                            //If it's not possible to notify the person via in app of the failed smtp then perhaps it notifies OPS personnel and biz admin personnel
+todo: //NEW NOTIFICATION SUBSCRIPTION EVENT TYPE:
+			//OPERATIONS_PROBLEMS - backup, notifications, out of memory, what have you, anyone can subscribe to it regardless of rights
+				//this is just to let people know there is a problem
+
 BACKEND
 
 
@@ -45,7 +62,7 @@ todo: create notifications at server for ops stuff in todos once back end is cod
 
 todo: client global settings notification systemactive
 	Needs to get data from api as well as UI to control it and translation key for NotificationSystemActive
-	
+
 UI
 todo: UI area for viewing App notifications	
 	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3783