ayanova/devdocs/todo.txt

@@ -210,10 +210,7 @@ todo: many biz objects are not using new PUT methodology
 
 
 
-CURRENTLY DOING: workorder back end
+CURRENTLY DOING: workorder front POC
-	- first pass at back end to modernize the techniques used (asnotracking etc)
-	- ensure all objects are represented
-	- code rudimentary routes for all
 	- make minimal front end enough for POC wokorder->woitem->one granchild collection
 		- test out, confirm can CRUD as planned independantly and all at once
 		- will need some dirty fields and viz fields likely added to models so go minimal route as possible to POC it
@@ -223,8 +220,7 @@ CURRENTLY DOING: workorder back end
 	- Keep working on front and back responds to front needs as I go
 	- load and stress test on client
 
-todo: should webPackCHunkNames be subdivided for service section because some people do quotes might not do service wo etc??
+
-	it's going to be large, maybe it would need breakdown??  Just an idea
 
 
 
@@ -241,6 +237,7 @@ todo: how far to extend down tags, custom fields , wiki
 	Main thing is to be able to print the custom fields and tags which is there by default now
 	Cons: huge form, maybe too much on it??
 	Just doing units for now, will consider others later
+	## See how units turn out in UI and go from there ##
 
 todo: in UI the workorder state should show current state but be expandable to view list of all state changes
 	Most of time will want to only see the current state, not all state history
@@ -250,10 +247,14 @@ todo: in UI the workorder state should show current state but be expandable to v
 
 
 
-todo: UI big unresolved question: am I going to expose the workorder children as separate lists in the UI??
+todo: UI wo descendants data table exposure (old v7 wo tree nav pane ui)
 	people probably want them / it's an easy way to see certain things you can't see any other way
 	I don't want to put them into the main menu, however I could expose them as menu options from the workorderlist itself
-		so user goes to workorders select items list from menu -> Workorderitems -> select parts list from menu -> Parts
+		so user goes to Main Workorders DataTable and in there with the extensions etc is an option to
+		 select items list from menu -> Workorderitems -> select parts list from menu -> Parts
+		 So at wo list level you can switch to items level
+		 at items level you can select any grandhild level and see a datalist for that level
+		 but only top level exposed in navigation pane menu
 
 todo: WorkorderBiz "modernize" follow the norms of other objects
 	explicitly decouple the graph from each other, currently I think it's set to force transaction for all graph but in reality it should just be separate objects loosely coupled
@@ -263,6 +264,10 @@ todo: WorkorderBiz "modernize" follow the norms of other objects
 		setting viz fields for a sub item that is saved and comes back to the client with viz fields set e.g. a workorderitemlabor record with somethign filled in from server
 				
 todo: Viz fields - calculate totals etc
+	This is a bit fucky becuase it means every item added needs to update the entire workorder even though they are decoupled
+	maybe an on demand recalc total or it separately does it at the back end and just provides an update or...???
+	But because of notification issues we do need to know it on every update (the andy)
+	if this is the only reason then the andy needs a re-think, no one has asked for it but one site and it would affect a lot of shit
 	Because of "The Andy" notification and also because it makes reporting far easier, we need viz fields to calculate all manner of totals 
 	perhaps the total calc should be split out from the regular Viz field processing to make the notification easier and less work on every save
 	or maybe even a separate function to calc the only number needed for the Andy and leave the Viz to be as it is