admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2020-12-07 18:11:16 +00:00
parent 2d38862003
commit f6bea2b8bf
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ayanova/devdocs/todo.txt
View File

@@ -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

4
ayanova/src/views/cust-user.vue
View File

@@ -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() {