From bfef6a8ffd7a24f5baa0c89e9b96507c46f1486b Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 14 Jul 2021 18:54:24 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index ea893ed4..7e3c2893 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -425,21 +425,27 @@ CURRENTLY DOING: tasks: - prevent sending items not permitted - prevent modification of items not permitted (also create and delete) - hide header and woitem fields not applicable to restricted + Test client end against server code before modifying client to prevent restricted acts + easier to test when can actually try it + Test each of the three restricted roles and one full role + + 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 + 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 + Subcontractor / tech limited modifications - -- Server Controller workorder* routes add blocking code so can't fetch things they aren't allowed etc - level one blocking - - At client have code to set restricted user restricted fields to read-only or hide as necessary per below - Remove sections from work order for low rights users as per below - Test login as each low rights type and confirm works as planned below + DO THIS CAREFULLY, IT"S COMPLEX AND DEFINITELY WILL HAVE BUGS HYPOTHETICAL SCHEDULEABLE USER ROLE RIGHTS