This commit is contained in:
2020-11-27 20:09:33 +00:00
parent 4be10252d2
commit 2eb4d697f9
2 changed files with 1 additions and 29 deletions

View File

@@ -36,34 +36,6 @@ To REMOVE: apt-get remove dotnet-runtime-3.0 (replace 3.0 with whatever version
MISC ITEMS THAT CAME UP
todo: import items triggers notification checks since they are going through the regular create process
e.g. this throws up all the time during v8 migrate: throw new System.NotImplementedException("Awaiting workorder object completion");
I'm leaning towards no import should ever trigger notification checks but then again maybe sometimes they should? confusing
I'm thinking there needs to be a skip notification check for import objects somehow, but how and where to set that
maybe a non persisted field for skip_notify_check or something on objects?
Need to consider normal usage vs import etc
also import export code, should it trigger notification?
If a user imports a bunch of clients from a json file and they happen to have a notification set for create client then could get thousands of notifications
TRICKY, possible resolution:
something flagged on the login session only and must be superuser for mass import
so maybe an extra flag during auth indicating mass change session, i.e. user logs in with special route or parameter
server provides jwt for session that contains a flag to not do notifications?
Or, a skip_notify header that only the superuser can add to their api calls, server sees it and sets it for that specific op only?
can a header be seen at the level of process notifyevent?
todo: network error should not show on NEW COUNT for notifications because it's looping over and over and keeps showing that error
That particular code should just show the error once maybe then go about it's business quietly?
or maybe it's kosher as is, a dev environment is not the same as production after all
todo: v8migrate should check if user's have a translation being used before exporting it
exporting translations is slow and should be sped up
todo: on all hide password option forms need one central button to hide passwords because it's the reveal button is a tab stop stuck on when entering data
quick check to see if can make it not be a tab stop before doing this
todo: RESET User edit docs
suggest loginname be email address in docs
todo: User grids, cursor changed to indicate a clickable entire line for each item and replicate that to all other stock openable grids

View File

@@ -963,7 +963,7 @@ function generateMenu(vm) {
isMain: false,
icon: "$ayiUser",
title: "Contact",
helpUrl: "form-adm-user",
helpUrl: "form-cust-contact",
formData: {
ayaType: window.$gz.type.User,
recordId: vm.$route.params.recordid,