ayanova/devdocs/todo.txt

@@ -273,9 +273,7 @@ todo: many biz objects are not using new PUT methodology
 CURRENTLY DOING: 
 
 	Model affecting cases:
-		
-		https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3533
-			outside service decision, keep with unit or separate??
+				
 		https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/2052
 			add engineer signature fields / UI		
 		https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1908
@@ -286,9 +284,12 @@ CURRENTLY DOING:
 
 OVERALL	
 
-	- once past this step then second pass at new features **that affect models** (not necessarily UI stuff just fields required etc)
-		Add items below that are just spurious and not tied to a particular case as v.next cases YAGNI/TTM!	
+	- Add items below that are just spurious and not tied to a particular case as v.next cases YAGNI/TTM!	
 	- then full in front end and flow out to back end as required, remove any backend that was a defunct evolutionary path so no cruft left around
+		many UI affecting cases, some bigger than others, almost none though are deal breakers in terms of just putting all the controls on first then refining 
+		so can go whole hog on adding controls and stuff, but make sure that they are all dealt with as hideable wherever possible and in some cases need to add
+		a hideable for entire collection object (i.e. can hide all of outside service so it never shows etc)
+		Don't forget Viz fields as well
 	- Keep working on front and back responds to front needs as I go
 	- load and stress test on client
 		This one really needs a e2e test that works and will hammer it so we can run that from multiple locations