From 5d14d0ac0a8371f3e932c6ef843813f78a51db8e Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 16 May 2019 20:12:55 +0000 Subject: [PATCH] --- devdocs/specs/core-roles.txt | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/devdocs/specs/core-roles.txt b/devdocs/specs/core-roles.txt index 00dc1a34..e4669570 100644 --- a/devdocs/specs/core-roles.txt +++ b/devdocs/specs/core-roles.txt @@ -134,6 +134,13 @@ nothing to do with business stuff or actual business data ************************************************************************************************************************************************************ =-=-=-=- HOW TO HANDLE EDIT OWN PLANNING =-=-=-=-=- +- EditOwn is really not about editown it's about supporting a user who is not supposed to see any data other than the bare minimum in order to fill out workorders + - Make it a business rule(s) instead in the areas of workorders and anything specific + - Get rid of edit own rights code entirely + - this might mean can clean up ownerID stuff in objects? + + +### DELETE THIS WORKING STUFF ABOUT EDIT OWN BELOW - EDIT_OWN: HOW TO HANDLE PROPERLY?? - PROPOSED SOLUTION: 5/16 @@ -141,7 +148,7 @@ nothing to do with business stuff or actual business data - NOTES FROM 5/14/2019 - Here are the most important characteristics to consider: - - EditOwn is really not about editown it's about supporting a user who is not supposed to see any data other than the bare minimum in order to fill out workorders + - EditOwn is originally intended to deal with limited rights users who are not supposed to see other workorders but the ones they are supposed to work on. - Original intention is they can create items necessary to fill out their own workorders - It means a workaround on every single object and list coming from the server to check if they own an object in addition to their basic rights.