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
2021-06-07 19:25:54 +00:00
parent 136ecc69fb
commit 672ccd0730
2 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
ayanova/devdocs/todo.txt
View File

@@ -367,6 +367,19 @@ todo: many biz objects are not using new PUT methodology
CURRENTLY DOING: workorder round two electric boogaloo CURRENTLY DOING: workorder round two electric boogaloo
basics first then increasingly esoteric features basics first then increasingly esoteric features
todo: a mixup between "not finished" wording and code and actual "Close by date" on work order header
Seems as though some areas are coded / planned based on creation date of workorder rather than on closeby date
in fact close by date isn't even factored into any planned v8 notification which is just wrong
Creation is factored into not finished but created means nothing on it's own or should be a separate notification like age or somethign
so change everythingn related to "finished" to be worded as "close by" to eliminate confusion e.g.:
"NotifyEventWorkorderFinishStatusOverdue": "Work order not finished in time",
Go over code and plans and enums and make sure it all lines up with close by.
Also, close by is a bit out of sync with the wo status wording of "Completed" which is what I decided was a better term, so maybe the workorder field should not be "close by" but
"complete by"
Then after above can implement the notification properly which currently is using creation date for calcs
todo 3: notification todo 3: notification
Go through all notification types and pick out relevant ones, paste here in a list then implement one by one and test each Go through all notification types and pick out relevant ones, paste here in a list then implement one by one and test each

1
ayanova/src/views/home-notify-subscription.vue
View File

@@ -335,7 +335,6 @@ export default {
switch (this.obj.eventType) { switch (this.obj.eventType) {
case 24: case 24:
case 10: case 10:
case 15:
case 32: case 32:
return true; return true;
default: default: