ayanova/devdocs/todo.txt

@@ -149,7 +149,15 @@ PURCHASE ORDER:
 			Also, if it was used on a workorder or something you really can't back out of that after the fact
 		
 		Maximum flexibility would be to allow any edit any time regardless and the only thing locked is things that are sold already or used on a workorder already which can't be reversed easily?
-		Though there is nothing to control here except inventory, the idea of locking the PO was just to ensure there was no changes from what was ordered to what will be received however that seems to be not reality and changes after order happen all the time
+		Though there is nothing to control here except inventory, the idea of locking the PO was just to ensure there was no changes from what was ordered to what will be received however 
+		that seems to be not reality and changes after order happen all the time
+
+		WHAT IF: status was entirely user controlled and they can set it to what they want and we never lock the UI for it?  it's just a flag for convenience
+		WHAT IF: we also add a Closed / Open button which prevents casual editing?
+		WHAT IF: the po list was based off a view and the view calculated if a po should be considered fully received or not and flagged that in the UI list
+		WHAT IF: Ordered or not Ordered as a separate checkbox they select that they can set at any time?
+		WHAT IF: Fully received is calculated from ordered-received from all line items in list view query of PO's?
+		WHAT IF: any changes to line items taht are tied to part request would just reverse or fixup whatever they type in if not received yet
 
 
 	#QUESTION: why do wokorders care about po's and vice versa, completely seperate operations / things?  Can they be completely disconnected?