ayanova/devdocs/todo.txt

@@ -225,17 +225,10 @@ todo: many biz objects are not using new PUT methodology
 
 
 
-CURRENTLY DOING: make from new
-	current issues:
-	
-
-	islockedatserver may be wonky in some cases, before it assumed that an edit could take place if islockedatserver but not anymore
-	however the new plan is only op possible when islockedatserver is to change status so need to check schedusers and woitems for that bit
-	i think there is some funkiness there.
+CURRENTLY DOING: 
 
 BIG PICTURE STUFF	
-	- ability to create from nothing implement whatever is minimally necessary to get it to work and do full crud test at all layers
-	- test out, confirm can CRUD as planned independantly and all at once	
+	- Duplicate test
 	- Test out role rights, login as various roles and ensure it works as expected
 	- once pass this step then second pass at new features that affect models (not necessarily UI stuff just fields required etc)
 		shouldn't be too much as already did that when recently fleshed out models but no doubt missed much
@@ -245,17 +238,15 @@ BIG PICTURE STUFF
 
 
 CURRENT ACTIONABLE TODOS
-todo: if islockedatserver is true I am still attempting to support editing, but it's a bit mixed up as the user would need to set the status to an unlocked state as well
-	current plan sucks.  Instead it should be treated entirely as readonly if islocked at server with the sole exception of the state so the user is forced to 
-	set an unlocked status, SAVE, *THEN* then can edit at will.
-	Trying to support both at once would be a mess.
 
-todo: need to add a popup error if attempting to save from locked to locked state and there are other changes that need to be saved 
-	(or let error from server handle it?? Not a first class UI experience though and might be a quite common mistake)
+todo: status control should require click to open dialog which shows list of all status prior and allows to add then close to view
+	this way it's clear how to change, less confusing than now and easy to get at the list
+
 todo: can I turn control labels into hyperlinks for getting to feeder records?  If not then need to find a way to accomplish it        
 		e.g. can workorder status title be changed to a hyper link to status list
 		e.g. can projects title be turned to a hyper link to projects list
-		ideally not in menu because it would be a lot on a workorder and need space for wo graph subitem links       
+		ideally not in menu because it would be a lot on a workorder and need space for wo graph subitem links   
+		### I ALREADY have an affordance for this with the pick lists, JUST replicate that!!
 
 todo: failed saved on a grandchild item shouldn't preclude the rest saving
 e.g. if there is a concurrency error on a child that shouldn't block the rest but a fatal error probably should