ayanova/devdocs/todo.txt

@@ -23,10 +23,24 @@ todo: client global settings notification systemactive
 
 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: 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: Customer User list form side track but relevant to this
+	Have to decide, do I list all users in the Existing users list form including customers?
+	Or, is it done via the Customer themselves?
+	Or is it both maybe, shit have to pick one
+	I can see a case for wanting to just see every user together regardless of type and another case for wanting to simplify it down to just going via the customer themselves
+		have to imagine the use cases and go accordingly.
+		My gut feeling is people would rather go via Customer page since they are likely in there via interacting with the customer in the first place, i.e. we fired Bob so take him off or we hired shirly so put her on or why am I not getting notifications can you test it etc
+		Case for the full list including customer users is really just a "it woudl be nice to see them all in one place" but they aren't like normal users and will need an alternative editing UI anyway
+		So My gut feeling is to do it via the Customer as a limited list, not via the regular Users page
+		it would have it's own edit form and own list as it would not need the full datalist treatment in theory
+		Plus there also needs to be a way to do subscriptions for the customer users as well which would be easier with it's own UI area completely
+
 todo: Test server down while polling in release mode, does it recover when server starts again or...?