cr-connect-workflow/crc
Dan Funk c7484267e1 For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals".
We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r.

Added "date_approved" to the approval model.

And moved the approver and primary investigator into real associated models to make it easier to dump.

Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields.  But it was mainly to do with always returning all the data with each form submission.
2020-06-02 18:17:00 -04:00
..
api For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". 2020-06-02 18:17:00 -04:00
models For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". 2020-06-02 18:17:00 -04:00
scripts Don't add an empty approval record. 2020-06-02 08:35:19 -04:00
services For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". 2020-06-02 18:17:00 -04:00
static For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". 2020-06-02 18:17:00 -04:00
__init__.py Enabling Sentry for boxes with the flag set 2020-06-01 19:59:55 -06:00
api.yml Tweaks to approvals 2020-06-01 21:49:30 -04:00