ayanova/devdocs/todo.txt

@@ -426,22 +426,23 @@ CURRENTLY DOING:
 
 tasks:
 	
-	Modify client to now show and / or prevent restricted actions
-		Maybe just mirror the UserIs* flags from server at client (or bring them with the work order for reporting dual usage as well??)
-			that way can consult the same basic fields and it's easier to remember and grok down the road
+	Modify client to not show and / or prevent restricted actions	
 		Hide sections / fields as required
 	
 	Test again and ensure it looks correct and works correct for each role
 		Test each of the three restricted roles and one full role 
 
 
-	UserIsRestrictedType
-	UserIsTechRestricted
-	UserIsSubContractorFull
-	UserIsSubContractorRestricted
-	UserCanViewPartCosts
-	UserCanViewLaborOrTravelRateCosts
-	UserCanViewLoanerCosts
+	value.userIsRestrictedType
+	value.userIsTechRestricted
+	value.userIsSubContractorFull
+	value.userIsSubContractorRestricted
+	value.userCanViewPartCosts
+	value.userCanViewLaborOrTravelRateCosts
+	value.userCanViewLoanerCosts
+
+	value.userIsSubContractorFull ||
+	value.userIsSubContractorRestricted
 
 
 
@@ -461,6 +462,17 @@ Subcontractor / tech limited modifications
 
 todo: units on work order are not limited to customer on work order??
 
+todo: Status on work order doesn't seem to be preventing "Who can select" by role properly
+	Make it not present status that are not supposed to be available
+	put a back end rule in validation to prevent it as well
+
+	Also, the seeded data roles are really fucked up and include some dubious roles and needs to also have some for tech - restricted specfically
+	i.e. they need to be logically correct as to what roles can select
+
+
+
+
+
 TODO 1: Test address / units select alternate when have units working
 
 TODO 2: //MIGRATE_OUTSTANDING comment tag