cr-connect-workflow/crc/api
Dan e5a38874f6 A hard or soft reset should also cause a 'cancel_notify' which will kick off any CANCEL events. If this happens during
a hard or soft reset, and an error is thrown trying to fulfil a cancel event, the reset should still fire.
Sending emails still had a number of issues correctly parsing it's arguments.  This is corrected.
2020-12-29 18:05:13 -05:00
..
__init__.py Adding file management. Files are stored in the database along with basic meta data. 2019-12-27 13:50:03 -05:00
admin.py Adding missing import 2020-07-17 17:08:44 -06:00
approval.py Refactoring shared code 2020-06-22 14:07:57 -06:00
common.py Added user.uid to ApiError and Sentry logging 2020-12-11 16:26:03 -05:00
data_store.py Move data store base into its own file. 2020-11-18 15:34:50 -05:00
file.py Make sure we get the file we intended 2020-12-07 08:50:20 -05:00
study.py Some minor cleanup on the study status and automatic events. I wanted to avoid having one database model automatically generating other database models as a side effect. The study service now has full responsiblity to recording study events. 2020-08-17 14:56:00 -04:00
tools.py Adds a test for string manipulation 2020-08-21 13:46:10 -04:00
user.py Make it easer to start things up. 2020-12-01 11:17:07 -05:00
workflow.py A hard or soft reset should also cause a 'cancel_notify' which will kick off any CANCEL events. If this happens during 2020-12-29 18:05:13 -05:00
workflow_sync.py Validation now assures that we won't encounter errors when generating navigation lists. 2020-12-28 17:33:38 -05:00