action_trigger - support immediate event processing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hello, while discussing a possible new feature of having a way for staff to fire off test messages to customers to test their notification settings, it was brought up that it would be nice if the test message happened as close to instantly as possible.
http://
I think that the feature would use the action_trigger system to send the test messages. Which uses cron to run action_
If a customer is standing in front of you, or is on the phone with you, it would be nice for the test messages to happen quickly consistently to save staff time and customer time.
Another use case would be for the customer welcome emails to get sent off as soon as a new patron record is created, so any bounce backs get to staff asap, so staff can talk to the customer immediately about why their email didn't work.
And yet one more use case is for the password reset emails. It would be good customer service to get those sent asap so that the reset message is in the customers inbox as soon as they go from the catalog login form to their email.
One method of making this happen may be to use the postgres listen/notify feature which allows one process to listen for an event notification fired off by another process. There could be a trigger setup on action_
Postgres LISTEN docs - https:/
Postgres NOTIFY docs - https:/
Perl script example for waiting for events - https://<email address hidden>
More examples and discussion - https:/
Changed in evergreen: | |
status: | New → Invalid |
I agree with a more immediate response from the action triggers for password resets and other uses of notifying the patron or staff.