This commit is contained in:
2020-07-10 00:12:23 +00:00
parent f197ee4896
commit 52d849f975

View File

@@ -20,6 +20,35 @@
###########################################################
BACKEND TODO / SYSTEM FOR RAVEN
IMPLEMENTATION PATH / PLAN - code as minimal a route as possible to get to working notifications end to end with minimal subset
first is test notification which is done as an implementation of the DefaultNotification Event type and is delivered to the current use running the test
This will go through all potential problems or maybe trigger a troubleshoot route at teh server that checks all and reports back with any issues found
Also needs to be localized (do the test route thing, that just makes the most sense. The test route should accept the type of notification i.e. inapp or smtp, act accordingly if it's a customer user vs regular if there is any difference)
Should report to user exactly any issues found at any level preventing it from happening
Should submit as a job and await running in place like other ones so that its actually working end to end with the generator
OR
should it submit and send immediately bypassing generator as just an immediate test.
OR
maybe it's an option for the user to choose.
widget / user crud ops and tag filtered in both App and in smtp
Then viewed in UI and worked with, properly shows count waiting etc
Examine system, bulletproof it as much as possible from first impressions
Make sure all controls work for
Once have that then can flesh out all the rest afterwards
todo: Make the notification subscription front end page
At least enough to subscription to widget biz notifications
with translation keys
todo: make the ops notification front end page
todo: make the biz notification page
todo: implement the Widget and User crud notification systems as per spec with an eye to replicating everywhere and allowing for specialty other types in system
i.e. not just crud but future stuff like workorder status change etc
also this is where the tags come into play
todo: make the job objects
todo: should be able to send a test notification to any user from user form (or user list via Customer form) as a means of ensuring the system works
TODO: check before any thing that might create a dupe
todo: have removed the old v7 SMTP retry deliveries for simplification