ayanova/devdocs/todo.txt

@@ -226,6 +226,41 @@ todo: workorder global setting of which roles can change a workorder status??
 
 todo: Workorder -> WorkorderService now can combine tables all together under workorder
 	
+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
+	Fetchable as an entire graph for reporting and initial loading of UI form but updateable and fetchable separately
+	Viz stuff needs to be split out considerably to handle seperately 
+		calcing totals for entire wo
+		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
+	
+	ROUTES: actually, probably should code these as required rather than pre-deciding on them, let the client drive the design
+		need to handle all at once ops for entire wo as that saves traffic and it would be crazy to fetch a workorder in bits and pieces when you first open it and multiple requests when can just one trip it
+		But also need to be able to update down to a single grand child record
+		
+		Theoretical routes:
+			workorder/{wonumber}
+			workorder/{wonumber}/{woitem}
+			workorder/{wonumber}/{woitem}/{labors}
+			workorder/{wonumber}/items/parts/{WorkOrderItemPartId}
+			But, let the client drive it or it will make more work than necessary
+			if the client has what it needs then it will work for any API usage
+
+			FETCH
+				Entire wo graph
+				Sub or top part only right down to a specific grandchild record with viz fields set etc
+				I guess it's not a case of woitem and down but more a case of wo and all down or just a single item or collection of items at a single level
+			POST
+				Single item only either one of:
+				Entire wo graph
+				Descendant collection (if a collection)
+					can contain just one if that's all there is or a bunch if they were all added
+			PUT
+				Entire wo graph or 
+					descendant collections with one or more records
+			DELETE
+				same same??
+
+
 
 todo: CONCURRENCY decision / research - updating, in bits seperately, entirely at once? [## DECIDED, BITS MAKES MOST SENSE AND DIRTY TRACKING AT CLIENT ##]
 	Considering we are looking at a system where some users won't see or even get the data for some parts of teh workorder then it's important that they be able to just save their piece of it separately