Dan Funk 7b21b78987 Workflow Processor will deserialize workflows using the version of the BPMN files used during creation, but allows for both a soft and hard reset - soft resets will use the new workflow without a restart and will retain full history. A hard-reset will restart the workflow from scratch, but will retain the data from the last completed task. Workflows have a complex version number associated with them that is used during the deserialization to find the correct files.

2020-03-05 15:38:30 -05:00

..

__init__.py

Refactor models into seperate directories

2019-12-31 16:32:47 -05:00

api_models.py

Adding the version of the specification used to create a workflow to the workflow api endpoint. Though the exact content of this version is likely to change.

2020-03-05 11:18:20 -05:00

file.py

Improve version handling of files. Consolidate more of this logic in FileService. Place the version on the actual data model, not the file model, so the file model remains the same, and we just version the data associated with it.

2020-03-04 13:40:25 -05:00

protocol_builder.py

Adds Protocol Builder models and schemas. Reorganizes and cleans up some files.

2020-02-27 09:54:46 -05:00

study.py

Updates study model to better match Protocol Builder. Deletes all migrations and starts over, since Alembic has problems migrating changes to existing column constraints.

2020-02-28 11:14:30 -05:00

user.py

Adds SSO header attributes

2020-02-20 15:43:29 -05:00

workflow.py

Workflow Processor will deserialize workflows using the version of the BPMN files used during creation, but allows for both a soft and hard reset - soft resets will use the new workflow without a restart and will retain full history. A hard-reset will restart the workflow from scratch, but will retain the data from the last completed task. Workflows have a complex version number associated with them that is used during the deserialization to find the correct files.

2020-03-05 15:38:30 -05:00