ayanova/devdocs/todo.txt

@@ -7,51 +7,16 @@ PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route chang
 
 ## CURRENT STAGE: 
 
-MODIFY USERS LIST FORM PER BELOW
-MODIFY USER EDIT FORM PER BELOW
-
-Copy and replicate to Customer users centric UI (list and edit form) within customers area of UI
-
-todo: USER redux
-	
-
-	# EXISTING USERS UI to be staff / contractor centric, no customer users
-	Change current Users list data-table to use the regular data-table
-	Add a User controller List route to get all non customer Users 
-	Modify User edit form to restrict the types of Users so you can't pick customer or head office, they will be separate
-
-	#Add customer centric users in customer tree area
-		Copy from regular users and modify the list and edit form
-		Consider adding an OutsideUser controller and associated biz object copied from User but then modified for customer / ho editing listing instead
-			Then all the role checking shit will be easier, though the regular User needs to be modified to NOT allow "Outside" type users to be edited etc
-			(Validation rule actually would make this work and special GET checking to prevent fetching cross roles type of user)
-		Add a dedicated list object at the User controller for "Outside" users
-			Rights are same as Customer object so anyone who can edit customers can edit their users
-		Edit form with Customer / headoffice picklist that shows depending on type of User
-			Edit form also must have the various options taht are on UserOptions form so they can be set up for the user and we don't need a useroptions form for them
-			Edit form Roles control absent, instead defaults
-			Notification subscriptions set here as well on behalf of customer user
-		Can only pick user type of headoffice or Customer (radio button?)
-		Edit User Route / Biz to allow rights to Customer to work instead of rights to User *IF* the User in question is an Outside user
+todo: Customer user, needs fields or form to set up translation, notify subscriptions etc
+	determine if can just re-use existing stuff for useroptions and notification with tweaks or...?
+	would be best of all if can just re-use then saves a separate UI to fuck with
+	Users might want to set up things for customer user, but they can do that by just logging in as that customer user so not really limited from doing that
+	maybe don't want customer users fucking with their settings?
+	TTM!!!
+
+
 
 
-	
-	Customer User UI area accessed from Customer form for CRUD User accounts tied to customers and also for setting up Notifications for those users
-	this is big and needs it's own NOTIFICATION area as well
-	can customer control this or does the biz admin control this?
-	See below there's a todo block about this
-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...?
 
@@ -271,6 +236,12 @@ todo: REPORTS v8 MIGRATE / EXPORT (CUSTOMIZED NOT STOCK) FROM v7? Try to see if
 	Be nice to see field list with translation for equivalent new.
 
 
+TODO: Reporting datasources
+	Needs to be able to handle getting data from different types of sources and be cool with it
+	e.g. Some datatables with selections are directly off a server list, not the regular datalist 
+	others are datalist
+	yet others may just be an array at client with no tie to server at all
+
 todo: REPORTING wiki Download, open as pdf, email?
 	- is this a reporting issue?  I think it is, moving to reporting