cr-connect-workflow/crc
mike cullerton 80f1fc276f Modify api.tools.send_email to accommodate the changes to the api endpoint in api.yml
We now accept subject, address, body (the email message), and possible data.
We now use email_service to send the message, and wrap it with the CR Connect html formatting.

**** We import DEFAULT_SENDER from config.default. Will this be a problem on testing and production? ****
2021-03-11 11:19:02 -05:00
..
api Modify api.tools.send_email to accommodate the changes to the api endpoint in api.yml 2021-03-11 11:19:02 -05:00
models Merge branch 'dev' into bug/225_enum_lookup_same_field_name 2021-03-02 14:15:58 -05:00
scripts removed unused import 2021-03-09 07:00:20 -05:00
services Merge branch 'dev' into bug/225_enum_lookup_same_field_name 2021-03-02 14:15:58 -05:00
static Jinja templates and svg file for pretty emails 2021-01-26 09:20:16 -05:00
templates Changes for ticket 215 - Change email header and footer to say CR Connect 2021-02-23 12:13:21 -05:00
__init__.py Allow for synch to work even if the local set of workflow specifications are completely empty. 2021-01-08 13:23:01 -05:00
api.yml Modify the send_email api endpoint (in Configurator Tools section) to accept subject, message, and data. 2021-03-11 11:10:10 -05:00