Use Cases and Requirements. (living document will add as I think of things)

[crazedVic]

Use Cases

• Executive has a task due in 24 hours - monitor the task table and send reminder notification to executive
• Document has been submitted but 2 weeks have passed without approval, send reminder notification to accountants to approve Document.
• Someone has just flagged @bob in a note, send notification to bob with link to the note, and that note is a note on an executive.
• If a user has more than 0 unread notifications, send a weekly summary of all unread notifications to that user.
• User can mark notification as read or delete it outright.
• A Document has been submitted for approval, send notification to accountants to let them know.

Requirements

• No email or SMS is sent directly, everything is put into a queue and handled by a queue manager.
• Messages in the queue are generally handled as FIFO, unless marked as high priority then they skip the line (forgot password)
• Probably use jetstream with teams enabled?
• Every message processed by queue manager should be logged to a monthly rotating text file in storage/logs/messaging
• Not entirely certain but might need two long running php processes, one to handle scanning of tables to look for records needing reminders and one to process the queue. Main reason is that the queue manager would have to scan pretty much all the time but the scan manager could just run once nightly.
• The queue manager should be application agnostic, it reads a table, sends emails or sms, and logs to file. The scan manager would be super tied to the application. - we might be able to create a trait for models that need to be scanned, and then in the trait we would create a static function that would encapsulate the logic behind reminders, which fields, what conditions, etc. Then maybe the master scan class can just have an array of model classes that should be scanned (they would need to USE this trait.
• EDIT: implement an interface in all possible models and run this interface
• nice to have if you have time: Add mobile number input field and communication prefs checkbox group, Email, SMS where user can choose either or both, to user profile. Then have queue manager actually use these preferences to send. Also at least one must be required.

[Frenchtoast0]

https://laravel.com/docs/8.x/scheduling#scheduling-artisan-commands https://laravel.com/docs/8.x/queues https://thecodelearners.com/laravel-jobs-and-queues-configuring-sending-mail-dispatching-jobs/

[Frenchtoast0]

Add a processes -> fields name, last_run, last_count, status = "Active"/"Disabled",

[Frenchtoast0]

When you create a record, triggers an event. Event will call a function that initializes the thing. ie. make employee record, generates three tasks on employee creation. Asynchronously set up. Make a listener to fire. (look into user creation)