ayanova/devdocs/todo.txt

@@ -307,6 +307,14 @@ todo: many biz objects are not using new PUT methodology
 CURRENTLY DOING: labors
 todo: taxes, line totals etc
 todo: contract in effect at server to set discounts etc
+	This is a bit of an issue due to contract id changes along with grandchild item changes stepping on each other.  
+		What if the workorder saved top down when new but header last when not new??
+			This way the pricing would get set on the final save
+			Would need to have a system to indicate a total refresh was necessary to reflect all pricing properly after contract applied
+			plus other things might need that as well, maybe if a full workorder is returned on save then it uses it otherwise just the
+			concurrency token is updated??
+			
+		
 
 
 ORDER: Travel, tasks, parts, loans, units, outside service