ayanova/devdocs/todo.txt

@@ -3,17 +3,14 @@
 PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route changes etc then back here in order lowest level first as affects the most stuff exponentially so best to do it early
 =-=-=-=-
 
-todo: notification
-	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3783	
-	notifications list UI as per case
-	back end at server
-		whole internal system and JOB
-			Automatic processing
-			other delivery methods besides client UI
-		Client related routes at server
-			Seen, fetch, delete etc
 
 
+BACKEND
+
+
+
+todo: BAckend server routes for App notification fetch and clear etc
+
 todo: Back end notification related settings
 	GlobalBizSettings
 		Add Notification system ACTIVE bool value
@@ -36,27 +33,6 @@ todo: notifysubscriptionbiz
 todo: notificationbiz
 todo: notifyeventbiz
 todo: notifydeliverylogbiz
-
-
-todo: create notifications at server for ops stuff in todos once back end is coded
-
-todo: client global settings notification systemactive
-	Needs to get data from api as well as UI to control it and translation key for NotificationSystemActive
-
-todo: ui area where admin can see all notifyevent and remove any that they deem as stuck or won't deliver
-	Can trigger deliver there maybe?
-
-todo: Customer User UI area accessed from Customer form for CRUD User accounts tied to customers and also for setting up Notifications for those users
-	See below there's a todo block about this
-
-todo: ops UI for settings
-todo: biz admin UI for turning on and off notification system "Active"
-
-todo: send test notification from both ops and admin pages
-	also from any user form and will troubleshoot as a matter of course before it sends
-	also from client users form
-	Will then issue warning if either OPS smtp notification is turned off (Active=false) or Admin NotificationSystemActive is turned off
-
 todo: COREBIZ (Start with Widget first as a test to prototype this chunk of code)
 	Need CRUD check for notification events
 	Need to handle check of new tags vs existing tags (delta of tags) for any notification type
@@ -65,6 +41,28 @@ todo: COREBIZ (Start with Widget first as a test to prototype this chunk of code
 			subscriptions code has either cached or on db lookup to see all that apply, returns an array of notifyeventtypes to be processed
 		Processes each notifyeventtype that it handles or passes off to central one maybe in some cases if common code
 
+todo: create notifications at server for ops stuff in todos once back end is coded
+
+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	
+	notifications list UI as per case
+	
+todo: ui area where admin can see all notifyevent and remove any that they deem as stuck or won't deliver
+	Can trigger deliver there maybe?
+todo: Customer User UI area accessed from Customer form for CRUD User accounts tied to customers and also for setting up Notifications for those users
+	See below there's a todo block about this
+todo: ops UI for settings
+todo: biz admin UI for turning on and off notification system "Active"
+
+todo: send test notification from both ops and admin pages
+	also from any user form and will troubleshoot as a matter of course before it sends
+	also from client users form
+	Will then issue warning if either OPS smtp notification is turned off (Active=false) or Admin NotificationSystemActive is turned off
+