ayanova/devdocs/todo.txt

@@ -5,9 +5,20 @@
 
 MISC ITEMS THAT CAME UP
 
-todo: Cust-User requires User rights but that's a big thing because it exposes 
+todo: Cust-User requires User rights 
-	inside user to edit possibly
+	but that's a big thing because it exposes inside user to edit possibly
 	Need to carve a workaround I guess in the User route and objects
+	I've thought about it and it still doesn't make sense to have paralel Contact type object because of the notification and auth and on and on at the server
+	and this is only a problem really at the UI for a couple of forms so better to work around from that end than to re-do a bunch of shit and have to have workarounds all 
+	over the notification code and auth etc etc
+	also see next item
+todo: cust-user form customization would affect adm-user form customization and vice versa
+	Need a workaround for this, maybe alternate form key would be best, if it's by type then whatever
+TODO FOR ABOVE:
+	rights workaround at the server where a user with Customer rights can modify a Contact but not a regular User
+	form customization workaround with parallel key system
+	Change to a DataList for all User lists
+	
 
 todo: No roles defined Users can login
 	Customer user with no roles can login and gets a CSR list screen

ayanova/src/views/cust-user.vue

@@ -397,7 +397,7 @@
 //
 ////////////////////////////////////////////////////////////////////////////////////////////////////////////
 //
-const FORM_KEY = "user-edit";
+const FORM_KEY = "cust-user-edit";
 const API_BASE_URL = "user/";
 const FORM_CUSTOM_TEMPLATE_KEY = "User";
 

ayanova/src/views/cust-users.vue

@@ -23,7 +23,7 @@
 </template>
 
 <script>
-const FORM_KEY = "adm-users";
+const FORM_KEY = "cust-users";
 export default {
   async created() {
     let vm = this;