ayanova/devdocs/todo.txt

@@ -304,26 +304,16 @@ 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??
-		What if setting contract is only available as a dialog when the record is clean?
-			Displays as text with a change button, when you click on it, if the record is dirty it prompts to save first before proceeding
-			otherwise it pops up a dialog to select a new contract then immediately saves it
-			This avoids the whole issue because nothing else can be saved at the same time
-			Children don't need to think about changing contract it has one place to do it, maybe as it's own route entirely!!!
+CURRENTLY DOING: labors (but involves contract change below)
+
+todo: contract changes
+	update woform to show contractviz as static text with change button beside it
+	when you click on change, if the record is dirty it prompts to save first before proceeding
+			otherwise it pops up a dialog to select a new contract then immediately saves it			
 			On success it will force a navigate to the same record to cleanly update.
 			Also this way people know it's a big deal to do it and it could also be wrapped in role restrictions easier too!!
-			
-			
-		
 
+todo: test contract changing, application on new etc and fully works with labor before getting too carried away carrying over to other things
 
 ORDER: Travel, tasks, parts, loans, units, outside service