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-07-24 00:03:44 +00:00
parent 2d6b72783e
commit 1c077f5d93
1 changed files with 25 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
ayanova/devdocs/todo.txt
View File

@@ -12,49 +12,46 @@ ____________
## CURRENT STAGE: ## CURRENT STAGE:
todo: test bad creds what happens to delivery
todo: send test message sb displaying return result from server as popup
UI
TODO: home-notify-subscription needs to also have ability to subscribe to GeneralNotification type via email
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 todo: "NotifyEvent QUEUE" ui area where admin can see all notifyevent and remove any that they deem as stuck or won't deliver
Can trigger deliver there maybe? Can delete and also, is this an OPS thing or a BIZ thing or a both thing?
todo: Customer User UI area accessed from Customer form for CRUD User accounts tied to customers and also for setting up Notifications for those users if can't actually view the contents then it's an ops thing but if can view contents then it's a biz thing
See below there's a todo block about this Two views depending on rights maybe?
todo: ops UI for settings
todo: biz admin UI for turning on and off notification system "Active"
todo: notifysubscriptionbiz must delete notifyevent records with that sub id todo: notifysubscriptionbiz DELETE must CASCADE delete notifyevent records with that sub id
is this a DDL configuration of the table thing? Is it already actually done?
No need to log the notifevent part deletion, just remove those fuckers
todo: send test notification from both ops and admin pages todo: send test notification from both ops and admin pages
also from any user form and will troubleshoot as a matter of course before it sends also from any user form and will troubleshoot as a matter of course before it sends
also from client users form also from client users form
Will then issue warning if either OPS smtp notification is turned off (Active=false) or Admin NotificationSystemActive is turned off Will then issue warning if OPS smtp notification is turned off (Active=false) or other problem, mirror of the code in the OPS notification setup form
todo: notification system docs todo: notification system docs
It's complex and needs a clear documentation about how it all works It's complex and needs a clear documentation about how it all works
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 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 Big overview then drill down
todo: need a place to send a General (old "quick") notification directly to a user and test it works via email delivery as well when user subscribes to general via email todo: UI QUICK NOTIFY need a place to send a General (old "quick") notification directly to a user and test it works via email delivery as well when user subscribes to general via email
Maybe from the IN APP notification form itself as a link in the menu?
todo: As biz objects are fleshed out need to also code their notification event stuff as well 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 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 " "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 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) (like capture the requested url and if found after login go to it)
todo: clean out leftover openurl stuff from old system todo: clean out leftover openurl stuff from old system
todo: Evaluate form generate sample data sb inside a dialog, it's only done once or twice at most and takes focus away from the other buttons and future stuff
todo: for some reason getting error about checking for notifications logout and back in again even after clean reboot todo: for some reason getting error about checking for notifications logout and back in again even after clean reboot
Not sure why or how the notification check is starting but it's not right at the moment Not sure why or how the notification check is starting but it's not right at the moment
At most sb one message saying server is unreachable and one more saying it's ok if it comes back but nothing in between At most sb one message saying server is unreachable and one more saying it's ok if it comes back but nothing in between
todo: Evaluate form generate sample data sb inside a dialog, it's only done once or twice at most and takes focus away from the other buttons and future stuff
todo: PMBIZ AND QUOTEBIZ AND QUOTETEMPLATEBIZ objects are fucked, seems to be an outdated version todo: PMBIZ AND QUOTEBIZ AND QUOTETEMPLATEBIZ objects are fucked, seems to be an outdated version
redo it from current best practices (PM TEMPLATE BIZ?). Note that it is missing many new methods like notifidation etc because of being fucked redo it from current best practices (PM TEMPLATE BIZ?). Note that it is missing many new methods like notifidation etc because of being fucked
todo: UserBiz is partway there but needs also to be standardized like the rest todo: UserBiz is partway there but needs also to be standardized like the rest
@@ -63,6 +60,12 @@ todo: userbiz delete, add notification subs and events to the delete related cod
todo: workorderbiz::putworkordergraphitem no longer requires ayatype parameter since the corebizobject has it already now built in todo: workorderbiz::putworkordergraphitem no longer requires ayatype parameter since the corebizobject has it already now built in
todo: workordertemplatebiz has inconsistent naming etc todo: workordertemplatebiz has inconsistent naming etc
todo: CUSTOMER UI FORM AND USERS OFF OF THAT
Customer User UI area accessed from Customer form for CRUD User accounts tied to customers and also for setting up Notifications for those users
this is big and needs it's own NOTIFICATION area as well
can customer control this or does the biz admin control this?
See below there's a todo block about this
todo: Customer User list form side track but relevant to this todo: Customer User list form side track but relevant to this
Have to decide, do I list all users in the Existing users list form including customers? Have to decide, do I list all users in the Existing users list form including customers?
Or, is it done via the Customer themselves? Or, is it done via the Customer themselves?