From f6bea2b8bf97043623d066aee0cfc66020a21f3d Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Mon, 7 Dec 2020 18:11:16 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 4 ++-- ayanova/src/views/cust-user.vue | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 54514e19..9e90b7a5 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -15,10 +15,10 @@ todo: Cust-User requires User rights 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 + Xrights 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 - No changing user type after the fact for customer and ho type Users unless rights to full user + XNo changing user type after the fact for customer and ho type Users unless rights to full user todo: TWEAK Init menu code tweaked but not quite right, need to go through as each user role and make sure it's correct diff --git a/ayanova/src/views/cust-user.vue b/ayanova/src/views/cust-user.vue index 53189447..ea24b734 100644 --- a/ayanova/src/views/cust-user.vue +++ b/ayanova/src/views/cust-user.vue @@ -397,9 +397,9 @@ // //////////////////////////////////////////////////////////////////////////////////////////////////////////// // -const FORM_KEY = "cust-user-edit"; +const FORM_KEY = "contact-edit"; const API_BASE_URL = "user/"; -const FORM_CUSTOM_TEMPLATE_KEY = "User"; +const FORM_CUSTOM_TEMPLATE_KEY = "Contact"; //<--- deliberately not 'User' as is customary as this is it's own form but also edit's User type objects so needs it's own customization key export default { async created() {