7 Commits

Author	SHA1	Message	Date
Dan	2009a794ea	We were depending on an active http request existing in order to fire emails, using that request to determine the front end url. We have the frontend url in our config file, and we don't have a request object when running scheduled tasks, so I just use our configuration setting instead.	2021-07-22 13:25:06 -04:00
mike cullerton	67697b5076	Lots of changes! ... Email Script: - The email script now accepts 3 keyword arguments; subject, recipients, and cc. - Subject and recipients are required. - Recipients (and cc) can be an email address or list of addresses. - You can use the string 'associated' in place of an email address, in which case we look up the users associated with a study that have send_email set to True. - Moved some helper methods to email_service. Email Service: - Added cc argument - Added helper methods previously in email script. - Modified get_rendered_content to accept message and data directly. Previously, we passed in the task and grabbed them from there. Now we can use the method outside a task.	2021-03-11 11:32:21 -05:00
Carlos Lopez	c7b864f9c7	Cleaning up old notes	2020-07-07 08:32:20 -06:00
Carlos Lopez	817333f26e	Adding proper exception information	2020-07-02 16:10:33 -06:00
Carlos Lopez	665faaa175	Send emails from service	2020-06-25 16:18:42 -06:00
Carlos Lopez	896ba6b377	Email relies now on markdown content	2020-06-17 17:00:16 -06:00
Carlos Lopez	e9e805b2c9	Storing emails in database	2020-06-09 22:57:56 -06:00