From 36aee7744848448a51810102d03259a338ead16c Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Tue, 7 May 2019 19:32:25 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 7bdcb8d1..56e4c060 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -59,28 +59,38 @@ TODO: - Maybe it's as simple as adding an automatic filter to the getmany routes in bizobjects that add if editown and filters on ownerid=currentuserID - Plan calls for limited users to be able to create a client for example to fill out a workorder even if they are a subcontractor with limited client rights but this seems bogus, the requested feature is probably more to do with they can fill it out but not create major new objects, only select from them. - POTENTIAL SOLUTIONS + - NAIVE SOLUTION + - Just add more code to show the editown able stuff in addition to the full or limited rights + - Add more code for all getmany lists to auto-filter on own if that's the only right. + - A new right for does the user have ANY access to an object for the client to quickly check and show sections / lists? - GetMany list object checks if only right to that list is editown and then adds a filter automatically to only show ownerID=currentuserID - Client checks not only full and limited but also edit own and if there is any editown then allows to continue - Potential issue here: do we show all of inventory if user only has editown rights to widgets and not parts (for hypothetical example) - Re-think the editown system, what exactly is it solving and is there another way to accomplish that? - For example if it's only about workorders then - Can we stick to the Change and Modify rights and just have the ability to assign workorders to lesser rights users user by user? - - + - Does edit own even work? - - For example, this means that a user needs to OWN a workorder to be able to edit it if they are subcontractor, that's BS + - For example, this means that a user needs to OWN a workorder to be able to edit it if they are subcontractor, that's NOT how it would happen in reality dispatcher would make it - The roles source docs say the user must appear on the workorder to see it. - Maybe it's more of a right thing that has nothing to do with editown and more to do with relevancy, so... - A service workorder is relevant to a non roled user if they appear on it even if they are a subcontractor - However they only see the bare minimum they need and nothing else. - Limited rights user can only select existing items to fill out a workorder? Not create new? - STEPS TO RESOLVE THIS: + - PLAN: Is this an impedence mismatch between roles and sections in the UI? + - For example a role can have the ability to see a section of the UI but in that section some might not appear + - I.E. Widget is under Inventory section which is nebulous and not defined anywhere formally so cant' check in code + - But also parts are inventory but user may have no rights to parts so that's a sub part of the inventory section to be checked + - UI needs to know does user have *any* rights to this area and then show it and then each sub item checks the roles to see if a list of parts (for example) should show? + - So need a quick checker to see if any part of a section is showable maybe that is a separate system from roles - READ: Go through plans and docs and look for roles related stuff and also subcontractor stuff to get a feel for what needs to be supported first before getting any deeper into this - Maybe I don't have the full idea of what this is about - Is this mostly subcontractors or is this also limited techs with limited rights? - Maybe I can have full techs do anything and limited techs only fill out forms, not create? - REQUEST: What is actually being requested by users to fulfil this feature that is different from v7? - SCOPE: Figure out what objects this would even affect, maybe it's only the workorder - - TTM: We don't want to hold up all of AyaNova 8 over this, the default mode is to do what was there before in v7, is this worth holding everythign up? + - TTM: We don't want to hold up all of AyaNova 8 over this, the default mode is to do what was there before in v7, is this worth holding everything up? - Can it be a future feature or does it need to be in v8? Probably needs to be in v8 - Can this be worked without any editown features? - Why does a user with limited rights get to "own" anything? @@ -118,6 +128,8 @@ TODO: End to end action +TODO: LOGIN navigate back to prior request when it triggers a login? + - Or would this cause a loop at times and fuck shit up? TODO UNDER CONSTRUCTION - show under construction page in every item that has no current view so it's clear it's not just buggy and blank but purposefully so TODO: Form dirty indicator on the form and easy to see, maybe the background tinges or something