This commit is contained in:
2020-07-23 19:56:08 +00:00
parent 1261116f1e
commit 8c6ad1e61b
2 changed files with 10 additions and 22 deletions

View File

@@ -12,26 +12,24 @@ ____________
## CURRENT STAGE:
todo: subscription form should autofill in user's personal email address when they pick a new email subscription but still let them change it
todo: subscription form still not completed, needs to be coded for when to show tags (for example) and other stuff
todo: Localize this message or get rid of it, it's annoying and possibly useless
"Error checking for notifications, see about->log for details; log out and back in again to reset "
todo: Back end notification related settings
GlobalOpsNotificationSettings (copy from backup settings)
SMTP creds, return address
todo: back end email subject could use the object type in addition to the name of the object i.e. AY:Object changed:User:Christina Shanahan 25
todo: notifysubscriptionbiz
Check for duplicate before accepting new / edit in validator
todo: notifiation sent when object deleted and link to open sb what?
todo: client global settings notification systemactive
Needs to get data from api as well as UI to control it and translation key for NotificationSystemActive
UI
TODO: home-notify-subscription needs to also have ability to subscribe to DefaultNotification type via email
This one is a bit tricky because it will always be able to deliver via in app but user can also opt for email delivery
so it should either always show a default inapp for DefaultNotification or it should not allow them to make one for inapp
Not sure what is best but it should be braindead simple
Make this a UserOption and checkbox on the user options form right beside the email address and only can be set to true if an email is entered
title: "Copy general notifications to email"
todo: rename "Default" notifications to "General" notifications, i.e. non-specific
todo: ui area where admin can see all notifyevent and remove any that they deem as stuck or won't deliver
@@ -51,21 +49,10 @@ todo: notification system docs
While it's fresh write a quick overview in docs so can flesh it out more later but get the main points even if in shorthand
Big overview then drill down
todo: Roles / roles change
Needs to re-examine notification subscriptions and events if no longer has access to them
Delivery and event code need to take roles into account and silently ignore no access things
todo: WorkorderStatus types and QuoteStatusTypes FINISHED STATUS or END STATUS
There needs to be a way to flag a quote or wo status as being the END status of the process
This is required so that things like wostatusage notifications know to ignore the END status as it's not going to change after that
and also so it knows which are considered "Finished" or "Finalized" or whatever is the best term
probably going to need it for a bunch of other stuff as well since there is no separate Closed flag
todo: notifyeventthype WorkorderClosed needs to be renamed or maybe removed in light of directlyu above regarding some status are now the equivalen to closed state in v7
todo: wo, quote and any other AgeValue notify objects are going to need to be able to record and compare age of event happening
For things like wostatusAge etc. Or, maybe they will need a separate datetime field to record the last time the status was changed
todo: As biz objects are fleshed out need to also code their notification event stuff as well
todo: Localize this message or get rid of it, it's annoying and possibly useless
"Error checking for notifications, see about->log for details; log out and back in again to reset "
##########################
todo: add method to continue on to requested url when a login needs to happen
(like capture the requested url and if found after login go to it)
@@ -415,7 +402,9 @@ todo: First of all triage the features to port over in the sanest order so not s
todo: Schedule form
- This one is big but requires the data to be there so as soon as implement enough things that are scheduleable then do this
todo: Notifications
Many are on hold until there are real objects to code against, now is the time to code them as the objects are added
todo: can beta test at this point
post installer, enlist trial users get feedback, don't get too down when they shit all over it as they will undoubtedly :)

View File

@@ -6,7 +6,6 @@
<v-row>
<gz-error :errorBoxMessage="formState.errorBoxMessage"></gz-error>
{{ obj }}
TODO: Default notification via email as an option
<v-col cols="12" sm="6" lg="4" xl="3">
<v-select
v-model="obj.eventType"