ayanova/devdocs/todo.txt

@@ -14,26 +14,27 @@ todo: v8 MIGRATE do not export empty strings, do null instead
 	confirm whatever method I use works for certain
 
 
-todo: now that have name fetcher in stored procedure can the c# version be ditched for more efficient fetches for stuff that calls it?
-
 todo: Help for list / editor form combo should be combined into list help alone
 	no reason to have separate
 	grid part can just say what's unique and link to standard grid help
 	form part below with all the deets
 
-todo: biz rule like validatecansave and validatecandelete but validatecanFetch for things like own memos and conditional biz rules like subcontractor seeing only own shit etc?
 
-todo: actual customer reports so can figure out datalist for bringing other names in
+
-	I'm thinking an alternate mode for reporting where there are more defined links in the list to fetch names?
+
+
 todo: double check - inactive user should not be involved in notifications at all, it should screen them out automatically and not create or deliver to them
+
+
+
 TODO: //MIGRATE_OUTSTANDING comment tag
 	search for this comment tag as it will contain items that could not be done until other items were migrated first
 	The tag will contain the description for each
 	
-todo: Consider adding latitude / longitude to wo, quote, pm objects
+todo: biz rule like validatecansave and validatecandelete but validatecanFetch for things like own memos and conditional biz rules like subcontractor seeing only own shit etc?	
-	can copy over from the unit or customer or set themselves
+	
-	and can always hide
+todo: actual customer reports so can figure out datalist for bringing other names in
-	means wo could be scheduled for ad-hoc locations and serviced that way, i.e. a truck parked on the side of the highway etc
+	I'm thinking an alternate mode for reporting where there are more defined links in the list to fetch names?
 ............................................................
 
 
@@ -100,6 +101,10 @@ Preliminary order to get the ball rolling, these are the easiest starting point:
 	Workorder
 		When do this need to go back and do a bunch of //MIGRATE_OUTSTANDING
 			i.e. show all
+			todo: Consider adding latitude / longitude to wo, quote, pm objects
+	can copy over from the unit or customer or set themselves
+	and can always hide
+	means wo could be scheduled for ad-hoc locations and serviced that way, i.e. a truck parked on the side of the highway etc
 
 	INVENTORY AND BALANCE STUFF
 		Best implemented as a stored procedure?