2021-05-05 15:30:08 +00:00
|
|
|
import urllib
|
2020-07-07 21:16:33 +00:00
|
|
|
from copy import copy
|
2020-05-04 14:57:09 +00:00
|
|
|
from datetime import datetime
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
from typing import List
|
|
|
|
|
2021-05-05 15:30:08 +00:00
|
|
|
import flask
|
2020-05-11 21:04:05 +00:00
|
|
|
import requests
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
from SpiffWorkflow import WorkflowException
|
2021-05-14 19:52:25 +00:00
|
|
|
from SpiffWorkflow.bpmn.PythonScriptEngine import Box
|
2020-05-30 19:37:04 +00:00
|
|
|
from SpiffWorkflow.exceptions import WorkflowTaskExecException
|
2020-05-07 17:57:24 +00:00
|
|
|
from ldap3.core.exceptions import LDAPSocketOpenError
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
|
2020-05-07 17:57:24 +00:00
|
|
|
from crc import db, session, app
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
from crc.api.common import ApiError
|
2021-05-14 19:52:25 +00:00
|
|
|
from crc.models.data_store import DataStoreModel
|
2021-03-09 18:31:26 +00:00
|
|
|
from crc.models.email import EmailModel
|
2021-07-12 14:00:39 +00:00
|
|
|
from crc.models.file import FileModel, File
|
2020-06-02 22:17:00 +00:00
|
|
|
from crc.models.ldap import LdapSchema
|
2021-07-20 15:44:11 +00:00
|
|
|
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
from crc.models.protocol_builder import ProtocolBuilderStudy, ProtocolBuilderStatus
|
2020-08-17 18:56:00 +00:00
|
|
|
from crc.models.study import StudyModel, Study, StudyStatus, Category, WorkflowMetadata, StudyEventType, StudyEvent, \
|
2021-03-22 21:30:49 +00:00
|
|
|
IrbStatus, StudyAssociated, StudyAssociatedSchema
|
2020-07-27 21:05:01 +00:00
|
|
|
from crc.models.task_event import TaskEventModel, TaskEvent
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
from crc.models.workflow import WorkflowSpecCategoryModel, WorkflowModel, WorkflowSpecModel, WorkflowState, \
|
2020-08-10 13:42:56 +00:00
|
|
|
WorkflowStatus, WorkflowSpecDependencyFile
|
2021-07-06 17:10:20 +00:00
|
|
|
from crc.services.document_service import DocumentService
|
2020-04-23 23:25:01 +00:00
|
|
|
from crc.services.file_service import FileService
|
2020-05-07 17:57:24 +00:00
|
|
|
from crc.services.ldap_service import LdapService
|
2021-07-06 17:10:20 +00:00
|
|
|
from crc.services.lookup_service import LookupService
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
from crc.services.protocol_builder import ProtocolBuilderService
|
|
|
|
from crc.services.workflow_processor import WorkflowProcessor
|
|
|
|
|
|
|
|
|
|
|
|
class StudyService(object):
|
|
|
|
"""Provides common tools for working with a Study"""
|
2021-07-06 18:40:20 +00:00
|
|
|
INVESTIGATOR_LIST = "investigators.xlsx" # A reference document containing details about what investigators to show, and when.
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
|
|
|
|
@staticmethod
|
2021-07-09 14:37:25 +00:00
|
|
|
def _is_valid_study(study_id):
|
|
|
|
study_info = ProtocolBuilderService().get_study_details(study_id)
|
|
|
|
if 'REVIEW_TYPE' in study_info.keys() and study_info['REVIEW_TYPE'] in [2, 3, 23, 24]:
|
|
|
|
return True
|
|
|
|
return False
|
|
|
|
|
|
|
|
def get_studies_for_user(self, user):
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
"""Returns a list of all studies for the given user."""
|
2021-02-25 17:20:43 +00:00
|
|
|
associated = session.query(StudyAssociated).filter_by(uid=user.uid,access=True).all()
|
2021-02-25 16:08:06 +00:00
|
|
|
associated_studies = [x.study_id for x in associated]
|
|
|
|
db_studies = session.query(StudyModel).filter((StudyModel.user_uid==user.uid)|
|
|
|
|
(StudyModel.id.in_(associated_studies))).all()
|
|
|
|
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
studies = []
|
|
|
|
for study_model in db_studies:
|
2021-07-09 14:37:25 +00:00
|
|
|
if self._is_valid_study(study_model.id):
|
|
|
|
studies.append(StudyService.get_study(study_model.id, study_model,do_status=False))
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
return studies
|
|
|
|
|
2020-05-22 15:46:03 +00:00
|
|
|
@staticmethod
|
A major refactor of how we search and store files, as there was a lot of confusing bits in here.
From an API point of view you can do the following (and only the following)
/files?workflow_spec_id=x
* You can find all files associated with a workflow_spec_id, and add a file with a workflow_spec_id
/files?workflow_id=x
* You can find all files associated with a workflow_id, and add a file that is directly associated with the workflow
/files?workflow_id=x&form_field_key=y
* You can find all files associated with a form element on a running workflow, and add a new file.
Note: you can add multiple files to the same form_field_key, IF they have different file names. If the same name, the original file is archived,
and the new file takes its place.
The study endpoints always return a list of the file metadata associated with the study. Removed /studies-files, but there is an
endpoint called
/studies/all - that returns all the studies in the system, and does include their files.
On a deeper level:
The File model no longer contains:
- study_id,
- task_id,
- form_field_key
Instead, if the file is associated with workflow - then that is the one way it is connected to the study, and we use this relationship to find files for a study.
A file is never associated with a task_id, as these change when the workflow is reloaded.
The form_field_key must match the irb_doc_code, so when requesting files for a form field, we just look up the irb_doc_code.
2020-05-28 12:27:26 +00:00
|
|
|
def get_all_studies_with_files():
|
2020-05-22 15:46:03 +00:00
|
|
|
"""Returns a list of all studies"""
|
|
|
|
db_studies = session.query(StudyModel).all()
|
A major refactor of how we search and store files, as there was a lot of confusing bits in here.
From an API point of view you can do the following (and only the following)
/files?workflow_spec_id=x
* You can find all files associated with a workflow_spec_id, and add a file with a workflow_spec_id
/files?workflow_id=x
* You can find all files associated with a workflow_id, and add a file that is directly associated with the workflow
/files?workflow_id=x&form_field_key=y
* You can find all files associated with a form element on a running workflow, and add a new file.
Note: you can add multiple files to the same form_field_key, IF they have different file names. If the same name, the original file is archived,
and the new file takes its place.
The study endpoints always return a list of the file metadata associated with the study. Removed /studies-files, but there is an
endpoint called
/studies/all - that returns all the studies in the system, and does include their files.
On a deeper level:
The File model no longer contains:
- study_id,
- task_id,
- form_field_key
Instead, if the file is associated with workflow - then that is the one way it is connected to the study, and we use this relationship to find files for a study.
A file is never associated with a task_id, as these change when the workflow is reloaded.
The form_field_key must match the irb_doc_code, so when requesting files for a form field, we just look up the irb_doc_code.
2020-05-28 12:27:26 +00:00
|
|
|
studies = []
|
|
|
|
for s in db_studies:
|
|
|
|
study = Study.from_model(s)
|
|
|
|
study.files = FileService.get_files_for_study(study.id)
|
|
|
|
studies.append(study)
|
|
|
|
return studies
|
2020-05-22 15:46:03 +00:00
|
|
|
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
@staticmethod
|
2021-04-30 15:55:12 +00:00
|
|
|
def get_study(study_id, study_model: StudyModel = None, do_status=False):
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
"""Returns a study model that contains all the workflows organized by category.
|
|
|
|
IMPORTANT: This is intended to be a lightweight call, it should never involve
|
|
|
|
loading up and executing all the workflows in a study to calculate information."""
|
|
|
|
if not study_model:
|
|
|
|
study_model = session.query(StudyModel).filter_by(id=study_id).first()
|
2020-08-09 00:25:01 +00:00
|
|
|
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
study = Study.from_model(study_model)
|
2021-02-10 16:58:19 +00:00
|
|
|
study.create_user_display = LdapService.user_info(study.user_uid).display_name
|
|
|
|
last_event: TaskEventModel = session.query(TaskEventModel)\
|
|
|
|
.filter_by(study_id=study_id,action='COMPLETE')\
|
|
|
|
.order_by(TaskEventModel.date.desc()).first()
|
2021-02-16 16:10:40 +00:00
|
|
|
if last_event is None:
|
|
|
|
study.last_activity_user = 'Not Started'
|
|
|
|
study.last_activity_date = ""
|
|
|
|
else:
|
|
|
|
study.last_activity_user = LdapService.user_info(last_event.user_uid).display_name
|
|
|
|
study.last_activity_date = last_event.date
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
study.categories = StudyService.get_categories()
|
2021-03-22 21:46:39 +00:00
|
|
|
workflow_metas = StudyService._get_workflow_metas(study_id)
|
2020-06-01 01:15:40 +00:00
|
|
|
files = FileService.get_files_for_study(study.id)
|
|
|
|
files = (File.from_models(model, FileService.get_file_data(model.id),
|
2021-07-06 17:10:20 +00:00
|
|
|
DocumentService.get_dictionary()) for model in files)
|
2020-06-01 01:15:40 +00:00
|
|
|
study.files = list(files)
|
Refactor the document details scripts. Now there is one script, it returns data in a consistent format, and has all the details required. The script is located in StudyInfo, with the argument documents. Make note that it returns a dictionary of ALL the documents, with a field to mark which ones are required according to the protocol builder. Others may become required if a workflow determines such, in which case the workflow will enforce this, and the document will have a count > 0, and additional details in a list of files within the document. I modified the XLS file to use lower case variable names, because it disturbed me, and we have to reference them frequently. Removed devious "as_object" variable on get_required_docs, so it behaves like the other methods all the time, and returns a dictionary. All the core business logic for finding the documents list now resides in the StudyService.
Because this changes the endpoint for all existing document details, I've modified all the test and static bpmn files to use the new format.
Shorting up the SponsorsList.xls file makes for slightly faster tests. seems senseless to load 5000 everytime we reset the data.
Tried to test all of this carefully in the test_study_details_documents.py test.
2020-04-29 19:08:11 +00:00
|
|
|
# Calling this line repeatedly is very very slow. It creates the
|
2020-07-06 20:01:43 +00:00
|
|
|
# master spec and runs it. Don't execute this for Abandoned studies, as
|
|
|
|
# we don't have the information to process them.
|
2020-07-31 03:03:11 +00:00
|
|
|
if study.status != StudyStatus.abandoned:
|
2021-02-16 13:44:41 +00:00
|
|
|
# this line is taking 99% of the time that is used in get_study.
|
|
|
|
# see ticket #196
|
2021-03-02 15:03:53 +00:00
|
|
|
if do_status:
|
2021-03-22 21:46:39 +00:00
|
|
|
# __get_study_status() runs the master workflow to generate the status dictionary
|
|
|
|
status = StudyService._get_study_status(study_model)
|
|
|
|
study.warnings = StudyService._update_status_of_workflow_meta(workflow_metas, status)
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
|
2020-07-06 20:01:43 +00:00
|
|
|
# Group the workflows into their categories.
|
|
|
|
for category in study.categories:
|
|
|
|
category.workflows = {w for w in workflow_metas if w.category_id == category.id}
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
|
|
|
|
return study
|
|
|
|
|
2021-02-24 17:05:06 +00:00
|
|
|
@staticmethod
|
|
|
|
def get_study_associate(study_id = None, uid=None):
|
|
|
|
"""
|
|
|
|
gets all associated people for a study from the database
|
|
|
|
"""
|
|
|
|
study = db.session.query(StudyModel).filter(StudyModel.id == study_id).first()
|
|
|
|
|
|
|
|
if study is None:
|
|
|
|
raise ApiError('study_not_found', 'No study found with id = %d' % study_id)
|
|
|
|
|
|
|
|
if uid is None:
|
|
|
|
raise ApiError('uid not specified','A valid uva uid is required for this function')
|
|
|
|
|
|
|
|
if uid == study.user_uid:
|
2021-07-22 19:08:28 +00:00
|
|
|
return {'uid': uid, 'role': 'owner', 'send_email': True, 'access': True}
|
2021-02-24 17:05:06 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
person = db.session.query(StudyAssociated).filter((StudyAssociated.study_id == study_id)&(
|
2021-02-25 14:07:46 +00:00
|
|
|
StudyAssociated.uid == uid)).first()
|
2021-02-24 17:05:06 +00:00
|
|
|
if person:
|
2021-07-22 19:08:28 +00:00
|
|
|
newAssociate = {'uid': person.uid}
|
|
|
|
newAssociate['role'] = person.role
|
|
|
|
newAssociate['send_email'] = person.send_email
|
|
|
|
newAssociate['access'] = person.access
|
|
|
|
return newAssociate
|
2021-02-25 14:07:46 +00:00
|
|
|
raise ApiError('uid_not_associated_with_study',"user id %s was not associated with study number %d"%(uid,
|
2021-02-24 17:05:06 +00:00
|
|
|
study_id))
|
|
|
|
|
|
|
|
@staticmethod
|
|
|
|
def get_study_associates(study_id):
|
|
|
|
"""
|
|
|
|
gets all associated people for a study from the database
|
|
|
|
"""
|
|
|
|
study = db.session.query(StudyModel).filter(StudyModel.id == study_id).first()
|
|
|
|
|
|
|
|
if study is None:
|
|
|
|
raise ApiError('study_not_found','No study found with id = %d'%study_id)
|
|
|
|
|
|
|
|
ownerid = study.user_uid
|
2021-07-20 15:44:11 +00:00
|
|
|
|
2021-02-24 17:05:06 +00:00
|
|
|
people = db.session.query(StudyAssociated).filter(StudyAssociated.study_id == study_id)
|
2021-07-20 15:44:11 +00:00
|
|
|
|
2021-03-22 21:30:49 +00:00
|
|
|
people_list = [{'uid':ownerid,'role':'owner','send_email':True,'access':True}]
|
2021-07-22 19:08:28 +00:00
|
|
|
|
|
|
|
for person in people:
|
|
|
|
newAssociate = {'uid': person.uid}
|
|
|
|
newAssociate['role'] = person.role
|
|
|
|
newAssociate['send_email'] = person.send_email
|
|
|
|
newAssociate['access'] = person.access
|
|
|
|
people_list.append(newAssociate)
|
2021-02-24 17:05:06 +00:00
|
|
|
return people_list
|
|
|
|
|
|
|
|
|
|
|
|
@staticmethod
|
2021-03-22 21:30:49 +00:00
|
|
|
def update_study_associates(study_id, associates):
|
2021-02-24 17:05:06 +00:00
|
|
|
"""
|
|
|
|
updates the list of associates in the database for a study_id and a list
|
|
|
|
of dicts that contains associates
|
|
|
|
"""
|
|
|
|
if study_id is None:
|
|
|
|
raise ApiError('study_id not specified', "This function requires the study_id parameter")
|
|
|
|
|
|
|
|
for person in associates:
|
|
|
|
if not LdapService.user_exists(person.get('uid','impossible_uid')):
|
|
|
|
if person.get('uid','impossible_uid') == 'impossible_uid':
|
|
|
|
raise ApiError('associate with no uid','One of the associates passed as a parameter doesnt have '
|
|
|
|
'a uid specified')
|
|
|
|
raise ApiError('trying_to_grant_access_to_user_not_found_in_ldap',"You are trying to grant access to "
|
|
|
|
"%s, but that user was not found in "
|
|
|
|
"ldap "
|
|
|
|
"- please check to ensure it is a "
|
|
|
|
"valid uva uid"%person.get('uid'))
|
|
|
|
|
|
|
|
study = db.session.query(StudyModel).filter(StudyModel.id == study_id).first()
|
|
|
|
if study is None:
|
|
|
|
raise ApiError('study_id not found', "A study with id# %d was not found"%study_id)
|
|
|
|
|
|
|
|
|
|
|
|
db.session.query(StudyAssociated).filter(StudyAssociated.study_id == study_id).delete()
|
|
|
|
for person in associates:
|
|
|
|
newAssociate = StudyAssociated()
|
2021-02-24 17:55:23 +00:00
|
|
|
newAssociate.study_id = study_id
|
2021-02-24 17:05:06 +00:00
|
|
|
newAssociate.uid = person['uid']
|
|
|
|
newAssociate.role = person.get('role', None)
|
|
|
|
newAssociate.send_email = person.get('send_email', False)
|
|
|
|
newAssociate.access = person.get('access',False)
|
2021-02-24 17:55:23 +00:00
|
|
|
session.add(newAssociate)
|
|
|
|
session.commit()
|
2021-02-24 17:05:06 +00:00
|
|
|
|
|
|
|
@staticmethod
|
|
|
|
def update_study_associate(study_id=None,uid=None,role="",send_email=False,access=False):
|
|
|
|
if study_id is None:
|
|
|
|
raise ApiError('study_id not specified', "This function requires the study_id parameter")
|
|
|
|
if uid is None:
|
|
|
|
raise ApiError('uid not specified', "This function requires a uva uid parameter")
|
|
|
|
|
|
|
|
if not LdapService.user_exists(uid):
|
|
|
|
raise ApiError('trying_to_grant_access_to_user_not_found_in_ldap',"You are trying to grant access to "
|
|
|
|
"%s but they were not found in ldap "
|
|
|
|
"- please check to ensure it is a "
|
|
|
|
"valid uva uid"%uid)
|
|
|
|
study = db.session.query(StudyModel).filter(StudyModel.id == study_id).first()
|
|
|
|
if study is None:
|
|
|
|
raise ApiError('study_id not found', "A study with id# %d was not found"%study_id)
|
|
|
|
db.session.query(StudyAssociated).filter((StudyAssociated.study_id == study_id)&(StudyAssociated.uid ==
|
|
|
|
uid) ).delete()
|
|
|
|
|
|
|
|
newAssociate = StudyAssociated()
|
2021-02-24 17:55:23 +00:00
|
|
|
newAssociate.study_id = study_id
|
2021-02-24 17:05:06 +00:00
|
|
|
newAssociate.uid = uid
|
|
|
|
newAssociate.role = role
|
|
|
|
newAssociate.send_email = send_email
|
|
|
|
newAssociate.access = access
|
2021-02-24 17:55:23 +00:00
|
|
|
session.add(newAssociate)
|
|
|
|
session.commit()
|
|
|
|
return True
|
2021-02-24 17:05:06 +00:00
|
|
|
|
|
|
|
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
@staticmethod
|
|
|
|
def delete_study(study_id):
|
2020-04-06 17:08:17 +00:00
|
|
|
session.query(TaskEventModel).filter_by(study_id=study_id).delete()
|
2021-03-09 18:31:26 +00:00
|
|
|
session.query(StudyAssociated).filter_by(study_id=study_id).delete()
|
|
|
|
session.query(EmailModel).filter_by(study_id=study_id).delete()
|
|
|
|
session.query(StudyEvent).filter_by(study_id=study_id).delete()
|
|
|
|
|
2020-04-29 20:07:39 +00:00
|
|
|
for workflow in session.query(WorkflowModel).filter_by(study_id=study_id):
|
2020-08-10 17:51:05 +00:00
|
|
|
StudyService.delete_workflow(workflow.id)
|
2020-08-12 14:13:23 +00:00
|
|
|
study = session.query(StudyModel).filter_by(id=study_id).first()
|
|
|
|
session.delete(study)
|
2020-04-08 17:28:43 +00:00
|
|
|
session.commit()
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
|
2020-04-29 20:07:39 +00:00
|
|
|
@staticmethod
|
2020-08-10 13:42:56 +00:00
|
|
|
def delete_workflow(workflow_id):
|
|
|
|
workflow = session.query(WorkflowModel).get(workflow_id)
|
2020-08-10 18:56:33 +00:00
|
|
|
if not workflow:
|
|
|
|
return
|
2020-08-10 13:42:56 +00:00
|
|
|
|
2020-08-10 18:56:33 +00:00
|
|
|
session.query(TaskEventModel).filter_by(workflow_id=workflow.id).delete()
|
2020-08-10 19:16:53 +00:00
|
|
|
session.query(WorkflowSpecDependencyFile).filter_by(workflow_id=workflow_id).delete(synchronize_session='fetch')
|
2020-08-11 04:23:20 +00:00
|
|
|
session.query(FileModel).filter_by(workflow_id=workflow_id).update({'archived': True, 'workflow_id': None})
|
2020-08-10 13:42:56 +00:00
|
|
|
|
|
|
|
session.delete(workflow)
|
2020-08-04 19:50:29 +00:00
|
|
|
session.commit()
|
2020-04-29 20:07:39 +00:00
|
|
|
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
@staticmethod
|
|
|
|
def get_categories():
|
|
|
|
"""Returns a list of category objects, in the correct order."""
|
|
|
|
cat_models = db.session.query(WorkflowSpecCategoryModel) \
|
|
|
|
.order_by(WorkflowSpecCategoryModel.display_order).all()
|
|
|
|
categories = []
|
|
|
|
for cat_model in cat_models:
|
|
|
|
categories.append(Category(cat_model))
|
|
|
|
return categories
|
|
|
|
|
2020-04-23 23:25:01 +00:00
|
|
|
@staticmethod
|
|
|
|
def get_documents_status(study_id):
|
2020-05-06 15:25:50 +00:00
|
|
|
"""Returns a list of documents related to the study, and any file information
|
Refactor the document details scripts. Now there is one script, it returns data in a consistent format, and has all the details required. The script is located in StudyInfo, with the argument documents. Make note that it returns a dictionary of ALL the documents, with a field to mark which ones are required according to the protocol builder. Others may become required if a workflow determines such, in which case the workflow will enforce this, and the document will have a count > 0, and additional details in a list of files within the document. I modified the XLS file to use lower case variable names, because it disturbed me, and we have to reference them frequently. Removed devious "as_object" variable on get_required_docs, so it behaves like the other methods all the time, and returns a dictionary. All the core business logic for finding the documents list now resides in the StudyService.
Because this changes the endpoint for all existing document details, I've modified all the test and static bpmn files to use the new format.
Shorting up the SponsorsList.xls file makes for slightly faster tests. seems senseless to load 5000 everytime we reset the data.
Tried to test all of this carefully in the test_study_details_documents.py test.
2020-04-29 19:08:11 +00:00
|
|
|
that is available.."""
|
2020-04-23 23:25:01 +00:00
|
|
|
|
2020-05-22 18:37:49 +00:00
|
|
|
# Get PB required docs, if Protocol Builder Service is enabled.
|
2020-06-15 15:27:28 +00:00
|
|
|
if ProtocolBuilderService.is_enabled() and study_id is not None:
|
2020-05-22 18:37:49 +00:00
|
|
|
try:
|
|
|
|
pb_docs = ProtocolBuilderService.get_required_docs(study_id=study_id)
|
|
|
|
except requests.exceptions.ConnectionError as ce:
|
2020-07-02 22:10:33 +00:00
|
|
|
app.logger.error(f'Failed to connect to the Protocol Builder - {str(ce)}', exc_info=True)
|
2020-05-22 18:37:49 +00:00
|
|
|
pb_docs = []
|
|
|
|
else:
|
2020-05-11 21:04:05 +00:00
|
|
|
pb_docs = []
|
2020-04-23 23:25:01 +00:00
|
|
|
|
2020-05-22 18:37:49 +00:00
|
|
|
# Loop through all known document types, get the counts for those files,
|
|
|
|
# and use pb_docs to mark those as required.
|
2021-07-06 17:10:20 +00:00
|
|
|
doc_dictionary = DocumentService.get_dictionary()
|
2020-05-07 17:57:24 +00:00
|
|
|
|
Refactor the document details scripts. Now there is one script, it returns data in a consistent format, and has all the details required. The script is located in StudyInfo, with the argument documents. Make note that it returns a dictionary of ALL the documents, with a field to mark which ones are required according to the protocol builder. Others may become required if a workflow determines such, in which case the workflow will enforce this, and the document will have a count > 0, and additional details in a list of files within the document. I modified the XLS file to use lower case variable names, because it disturbed me, and we have to reference them frequently. Removed devious "as_object" variable on get_required_docs, so it behaves like the other methods all the time, and returns a dictionary. All the core business logic for finding the documents list now resides in the StudyService.
Because this changes the endpoint for all existing document details, I've modified all the test and static bpmn files to use the new format.
Shorting up the SponsorsList.xls file makes for slightly faster tests. seems senseless to load 5000 everytime we reset the data.
Tried to test all of this carefully in the test_study_details_documents.py test.
2020-04-29 19:08:11 +00:00
|
|
|
documents = {}
|
|
|
|
for code, doc in doc_dictionary.items():
|
2020-04-24 03:32:20 +00:00
|
|
|
|
2021-07-06 17:10:20 +00:00
|
|
|
doc['required'] = False
|
|
|
|
if ProtocolBuilderService.is_enabled() and doc['id']:
|
2020-05-22 18:37:49 +00:00
|
|
|
pb_data = next((item for item in pb_docs if int(item['AUXDOCID']) == int(doc['id'])), None)
|
|
|
|
if pb_data:
|
|
|
|
doc['required'] = True
|
|
|
|
|
2020-04-23 23:25:01 +00:00
|
|
|
doc['study_id'] = study_id
|
|
|
|
doc['code'] = code
|
2020-04-24 03:32:20 +00:00
|
|
|
|
Refactor the document details scripts. Now there is one script, it returns data in a consistent format, and has all the details required. The script is located in StudyInfo, with the argument documents. Make note that it returns a dictionary of ALL the documents, with a field to mark which ones are required according to the protocol builder. Others may become required if a workflow determines such, in which case the workflow will enforce this, and the document will have a count > 0, and additional details in a list of files within the document. I modified the XLS file to use lower case variable names, because it disturbed me, and we have to reference them frequently. Removed devious "as_object" variable on get_required_docs, so it behaves like the other methods all the time, and returns a dictionary. All the core business logic for finding the documents list now resides in the StudyService.
Because this changes the endpoint for all existing document details, I've modified all the test and static bpmn files to use the new format.
Shorting up the SponsorsList.xls file makes for slightly faster tests. seems senseless to load 5000 everytime we reset the data.
Tried to test all of this carefully in the test_study_details_documents.py test.
2020-04-29 19:08:11 +00:00
|
|
|
# Make a display name out of categories
|
|
|
|
name_list = []
|
|
|
|
for cat_key in ['category1', 'category2', 'category3']:
|
2021-07-06 17:10:20 +00:00
|
|
|
if doc[cat_key] not in ['', 'NULL', None]:
|
Refactor the document details scripts. Now there is one script, it returns data in a consistent format, and has all the details required. The script is located in StudyInfo, with the argument documents. Make note that it returns a dictionary of ALL the documents, with a field to mark which ones are required according to the protocol builder. Others may become required if a workflow determines such, in which case the workflow will enforce this, and the document will have a count > 0, and additional details in a list of files within the document. I modified the XLS file to use lower case variable names, because it disturbed me, and we have to reference them frequently. Removed devious "as_object" variable on get_required_docs, so it behaves like the other methods all the time, and returns a dictionary. All the core business logic for finding the documents list now resides in the StudyService.
Because this changes the endpoint for all existing document details, I've modified all the test and static bpmn files to use the new format.
Shorting up the SponsorsList.xls file makes for slightly faster tests. seems senseless to load 5000 everytime we reset the data.
Tried to test all of this carefully in the test_study_details_documents.py test.
2020-04-29 19:08:11 +00:00
|
|
|
name_list.append(doc[cat_key])
|
|
|
|
doc['display_name'] = ' / '.join(name_list)
|
2020-04-23 23:25:01 +00:00
|
|
|
|
|
|
|
# For each file, get associated workflow status
|
A major refactor of how we search and store files, as there was a lot of confusing bits in here.
From an API point of view you can do the following (and only the following)
/files?workflow_spec_id=x
* You can find all files associated with a workflow_spec_id, and add a file with a workflow_spec_id
/files?workflow_id=x
* You can find all files associated with a workflow_id, and add a file that is directly associated with the workflow
/files?workflow_id=x&form_field_key=y
* You can find all files associated with a form element on a running workflow, and add a new file.
Note: you can add multiple files to the same form_field_key, IF they have different file names. If the same name, the original file is archived,
and the new file takes its place.
The study endpoints always return a list of the file metadata associated with the study. Removed /studies-files, but there is an
endpoint called
/studies/all - that returns all the studies in the system, and does include their files.
On a deeper level:
The File model no longer contains:
- study_id,
- task_id,
- form_field_key
Instead, if the file is associated with workflow - then that is the one way it is connected to the study, and we use this relationship to find files for a study.
A file is never associated with a task_id, as these change when the workflow is reloaded.
The form_field_key must match the irb_doc_code, so when requesting files for a form field, we just look up the irb_doc_code.
2020-05-28 12:27:26 +00:00
|
|
|
doc_files = FileService.get_files_for_study(study_id=study_id, irb_doc_code=code)
|
Refactor the document details scripts. Now there is one script, it returns data in a consistent format, and has all the details required. The script is located in StudyInfo, with the argument documents. Make note that it returns a dictionary of ALL the documents, with a field to mark which ones are required according to the protocol builder. Others may become required if a workflow determines such, in which case the workflow will enforce this, and the document will have a count > 0, and additional details in a list of files within the document. I modified the XLS file to use lower case variable names, because it disturbed me, and we have to reference them frequently. Removed devious "as_object" variable on get_required_docs, so it behaves like the other methods all the time, and returns a dictionary. All the core business logic for finding the documents list now resides in the StudyService.
Because this changes the endpoint for all existing document details, I've modified all the test and static bpmn files to use the new format.
Shorting up the SponsorsList.xls file makes for slightly faster tests. seems senseless to load 5000 everytime we reset the data.
Tried to test all of this carefully in the test_study_details_documents.py test.
2020-04-29 19:08:11 +00:00
|
|
|
doc['count'] = len(doc_files)
|
|
|
|
doc['files'] = []
|
2020-04-23 23:25:01 +00:00
|
|
|
|
2021-05-05 15:30:08 +00:00
|
|
|
# when we run tests - it doesn't look like the user is available
|
|
|
|
# so we return a bogus token
|
|
|
|
token = 'not_available'
|
|
|
|
if hasattr(flask.g,'user'):
|
|
|
|
token = flask.g.user.encode_auth_token()
|
2020-04-23 23:25:01 +00:00
|
|
|
for file in doc_files:
|
2021-05-14 19:52:25 +00:00
|
|
|
file_data = {'file_id': file.id,
|
|
|
|
'name': file.name,
|
|
|
|
'url': app.config['APPLICATION_ROOT']+
|
|
|
|
'file/' + str(file.id) +
|
|
|
|
'/download?auth_token='+
|
|
|
|
urllib.parse.quote_plus(token),
|
|
|
|
'workflow_id': file.workflow_id
|
|
|
|
}
|
|
|
|
data = db.session.query(DataStoreModel).filter(DataStoreModel.file_id==file.id).all()
|
|
|
|
data_store_data = {}
|
|
|
|
for d in data:
|
|
|
|
data_store_data[d.key] = d.value
|
|
|
|
file_data["data_store"] = data_store_data
|
|
|
|
doc['files'].append(Box(file_data))
|
Refactor the document details scripts. Now there is one script, it returns data in a consistent format, and has all the details required. The script is located in StudyInfo, with the argument documents. Make note that it returns a dictionary of ALL the documents, with a field to mark which ones are required according to the protocol builder. Others may become required if a workflow determines such, in which case the workflow will enforce this, and the document will have a count > 0, and additional details in a list of files within the document. I modified the XLS file to use lower case variable names, because it disturbed me, and we have to reference them frequently. Removed devious "as_object" variable on get_required_docs, so it behaves like the other methods all the time, and returns a dictionary. All the core business logic for finding the documents list now resides in the StudyService.
Because this changes the endpoint for all existing document details, I've modified all the test and static bpmn files to use the new format.
Shorting up the SponsorsList.xls file makes for slightly faster tests. seems senseless to load 5000 everytime we reset the data.
Tried to test all of this carefully in the test_study_details_documents.py test.
2020-04-29 19:08:11 +00:00
|
|
|
# update the document status to match the status of the workflow it is in.
|
A major refactor of how we search and store files, as there was a lot of confusing bits in here.
From an API point of view you can do the following (and only the following)
/files?workflow_spec_id=x
* You can find all files associated with a workflow_spec_id, and add a file with a workflow_spec_id
/files?workflow_id=x
* You can find all files associated with a workflow_id, and add a file that is directly associated with the workflow
/files?workflow_id=x&form_field_key=y
* You can find all files associated with a form element on a running workflow, and add a new file.
Note: you can add multiple files to the same form_field_key, IF they have different file names. If the same name, the original file is archived,
and the new file takes its place.
The study endpoints always return a list of the file metadata associated with the study. Removed /studies-files, but there is an
endpoint called
/studies/all - that returns all the studies in the system, and does include their files.
On a deeper level:
The File model no longer contains:
- study_id,
- task_id,
- form_field_key
Instead, if the file is associated with workflow - then that is the one way it is connected to the study, and we use this relationship to find files for a study.
A file is never associated with a task_id, as these change when the workflow is reloaded.
The form_field_key must match the irb_doc_code, so when requesting files for a form field, we just look up the irb_doc_code.
2020-05-28 12:27:26 +00:00
|
|
|
if 'status' not in doc or doc['status'] is None:
|
2020-04-23 23:25:01 +00:00
|
|
|
workflow: WorkflowModel = session.query(WorkflowModel).filter_by(id=file.workflow_id).first()
|
|
|
|
doc['status'] = workflow.status.value
|
|
|
|
|
Refactor the document details scripts. Now there is one script, it returns data in a consistent format, and has all the details required. The script is located in StudyInfo, with the argument documents. Make note that it returns a dictionary of ALL the documents, with a field to mark which ones are required according to the protocol builder. Others may become required if a workflow determines such, in which case the workflow will enforce this, and the document will have a count > 0, and additional details in a list of files within the document. I modified the XLS file to use lower case variable names, because it disturbed me, and we have to reference them frequently. Removed devious "as_object" variable on get_required_docs, so it behaves like the other methods all the time, and returns a dictionary. All the core business logic for finding the documents list now resides in the StudyService.
Because this changes the endpoint for all existing document details, I've modified all the test and static bpmn files to use the new format.
Shorting up the SponsorsList.xls file makes for slightly faster tests. seems senseless to load 5000 everytime we reset the data.
Tried to test all of this carefully in the test_study_details_documents.py test.
2020-04-29 19:08:11 +00:00
|
|
|
documents[code] = doc
|
2021-05-14 19:52:25 +00:00
|
|
|
return Box(documents)
|
2020-04-23 23:25:01 +00:00
|
|
|
|
2021-07-06 17:10:20 +00:00
|
|
|
@staticmethod
|
|
|
|
def get_investigator_dictionary():
|
|
|
|
"""Returns a dictionary of document details keyed on the doc_code."""
|
|
|
|
file_data = FileService.get_reference_file_data(StudyService.INVESTIGATOR_LIST)
|
|
|
|
lookup_model = LookupService.get_lookup_model_for_file_data(file_data, 'code', 'label')
|
|
|
|
doc_dict = {}
|
|
|
|
for lookup_data in lookup_model.dependencies:
|
|
|
|
doc_dict[lookup_data.value] = lookup_data.data
|
|
|
|
return doc_dict
|
2020-04-23 23:25:01 +00:00
|
|
|
|
2020-05-07 17:57:24 +00:00
|
|
|
@staticmethod
|
2020-07-06 16:09:21 +00:00
|
|
|
def get_investigators(study_id, all=False):
|
2020-07-07 21:16:33 +00:00
|
|
|
"""Convert array of investigators from protocol builder into a dictionary keyed on the type. """
|
2020-05-07 17:57:24 +00:00
|
|
|
|
|
|
|
# Loop through all known investigator types as set in the reference file
|
2021-07-06 17:10:20 +00:00
|
|
|
inv_dictionary = StudyService.get_investigator_dictionary()
|
2020-05-07 17:57:24 +00:00
|
|
|
|
|
|
|
# Get PB required docs
|
|
|
|
pb_investigators = ProtocolBuilderService.get_investigators(study_id=study_id)
|
|
|
|
|
2020-07-07 21:16:33 +00:00
|
|
|
# It is possible for the same type to show up more than once in some circumstances, in those events
|
|
|
|
# append a counter to the name.
|
|
|
|
investigators = {}
|
2020-05-07 17:57:24 +00:00
|
|
|
for i_type in inv_dictionary:
|
2020-07-07 21:16:33 +00:00
|
|
|
pb_data_entries = list(item for item in pb_investigators if item['INVESTIGATORTYPE'] == i_type)
|
|
|
|
entry_count = 0
|
|
|
|
investigators[i_type] = copy(inv_dictionary[i_type])
|
|
|
|
investigators[i_type]['user_id'] = None
|
|
|
|
for pb_data in pb_data_entries:
|
|
|
|
entry_count += 1
|
|
|
|
if entry_count == 1:
|
|
|
|
t = i_type
|
|
|
|
else:
|
|
|
|
t = i_type + "_" + str(entry_count)
|
|
|
|
investigators[t] = copy(inv_dictionary[i_type])
|
|
|
|
investigators[t]['user_id'] = pb_data["NETBADGEID"]
|
|
|
|
investigators[t].update(StudyService.get_ldap_dict_if_available(pb_data["NETBADGEID"]))
|
2020-07-06 16:09:21 +00:00
|
|
|
if not all:
|
2020-07-07 21:16:33 +00:00
|
|
|
investigators = dict(filter(lambda elem: elem[1]['user_id'] is not None, investigators.items()))
|
|
|
|
return investigators
|
2020-05-07 17:57:24 +00:00
|
|
|
|
|
|
|
@staticmethod
|
|
|
|
def get_ldap_dict_if_available(user_id):
|
|
|
|
try:
|
2020-06-04 18:59:36 +00:00
|
|
|
return LdapSchema().dump(LdapService().user_info(user_id))
|
2020-05-07 17:57:24 +00:00
|
|
|
except ApiError as ae:
|
|
|
|
app.logger.info(str(ae))
|
|
|
|
return {"error": str(ae)}
|
|
|
|
except LDAPSocketOpenError:
|
|
|
|
app.logger.info("Failed to connect to LDAP Server.")
|
|
|
|
return {}
|
Refactor the document details scripts. Now there is one script, it returns data in a consistent format, and has all the details required. The script is located in StudyInfo, with the argument documents. Make note that it returns a dictionary of ALL the documents, with a field to mark which ones are required according to the protocol builder. Others may become required if a workflow determines such, in which case the workflow will enforce this, and the document will have a count > 0, and additional details in a list of files within the document. I modified the XLS file to use lower case variable names, because it disturbed me, and we have to reference them frequently. Removed devious "as_object" variable on get_required_docs, so it behaves like the other methods all the time, and returns a dictionary. All the core business logic for finding the documents list now resides in the StudyService.
Because this changes the endpoint for all existing document details, I've modified all the test and static bpmn files to use the new format.
Shorting up the SponsorsList.xls file makes for slightly faster tests. seems senseless to load 5000 everytime we reset the data.
Tried to test all of this carefully in the test_study_details_documents.py test.
2020-04-29 19:08:11 +00:00
|
|
|
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
@staticmethod
|
2020-05-22 18:37:49 +00:00
|
|
|
def synch_with_protocol_builder_if_enabled(user):
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
"""Assures that the studies we have locally for the given user are
|
|
|
|
in sync with the studies available in protocol builder. """
|
2020-05-22 18:37:49 +00:00
|
|
|
|
2020-05-27 03:18:14 +00:00
|
|
|
if ProtocolBuilderService.is_enabled():
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
|
2020-05-27 03:18:14 +00:00
|
|
|
app.logger.info("The Protocol Builder is enabled. app.config['PB_ENABLED'] = " +
|
|
|
|
str(app.config['PB_ENABLED']))
|
|
|
|
|
|
|
|
# Get studies matching this user from Protocol Builder
|
|
|
|
pb_studies: List[ProtocolBuilderStudy] = ProtocolBuilderService.get_studies(user.uid)
|
|
|
|
|
|
|
|
# Get studies from the database
|
|
|
|
db_studies = session.query(StudyModel).filter_by(user_uid=user.uid).all()
|
|
|
|
|
|
|
|
# Update all studies from the protocol builder, create new studies as needed.
|
2020-08-17 18:56:00 +00:00
|
|
|
# Further assures that every active study (that does exist in the protocol builder)
|
2020-05-27 03:18:14 +00:00
|
|
|
# has a reference to every available workflow (though some may not have started yet)
|
|
|
|
for pb_study in pb_studies:
|
2020-08-17 18:56:00 +00:00
|
|
|
new_status = None
|
2020-05-27 03:18:14 +00:00
|
|
|
db_study = next((s for s in db_studies if s.id == pb_study.STUDYID), None)
|
|
|
|
if not db_study:
|
|
|
|
db_study = StudyModel(id=pb_study.STUDYID)
|
2020-08-17 18:56:00 +00:00
|
|
|
db_study.status = None # Force a new sa
|
|
|
|
new_status = StudyStatus.in_progress
|
2020-05-27 03:18:14 +00:00
|
|
|
session.add(db_study)
|
|
|
|
db_studies.append(db_study)
|
2020-08-17 18:56:00 +00:00
|
|
|
|
|
|
|
if pb_study.HSRNUMBER:
|
|
|
|
db_study.irb_status = IrbStatus.hsr_assigned
|
|
|
|
if db_study.status != StudyStatus.open_for_enrollment:
|
|
|
|
new_status = StudyStatus.open_for_enrollment
|
|
|
|
|
2020-05-27 03:18:14 +00:00
|
|
|
db_study.update_from_protocol_builder(pb_study)
|
|
|
|
StudyService._add_all_workflow_specs_to_study(db_study)
|
|
|
|
|
2020-08-17 18:56:00 +00:00
|
|
|
# If there is a new automatic status change and there isn't a manual change in place, record it.
|
|
|
|
if new_status and db_study.status != StudyStatus.hold:
|
|
|
|
db_study.status = new_status
|
|
|
|
StudyService.add_study_update_event(db_study,
|
|
|
|
status=new_status,
|
|
|
|
event_type=StudyEventType.automatic)
|
|
|
|
|
2020-05-27 03:18:14 +00:00
|
|
|
# Mark studies as inactive that are no longer in Protocol Builder
|
|
|
|
for study in db_studies:
|
|
|
|
pb_study = next((pbs for pbs in pb_studies if pbs.STUDYID == study.id), None)
|
2020-08-17 18:56:00 +00:00
|
|
|
if not pb_study and study.status != StudyStatus.abandoned:
|
2020-07-31 03:03:11 +00:00
|
|
|
study.status = StudyStatus.abandoned
|
2020-08-17 18:56:00 +00:00
|
|
|
StudyService.add_study_update_event(study,
|
|
|
|
status=StudyStatus.abandoned,
|
|
|
|
event_type=StudyEventType.automatic)
|
2020-05-27 03:18:14 +00:00
|
|
|
|
|
|
|
db.session.commit()
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
|
2020-08-17 18:56:00 +00:00
|
|
|
@staticmethod
|
|
|
|
def add_study_update_event(study, status, event_type, user_uid=None, comment=''):
|
|
|
|
study_event = StudyEvent(study=study,
|
|
|
|
status=status,
|
|
|
|
event_type=event_type,
|
|
|
|
user_uid=user_uid,
|
|
|
|
comment=comment)
|
|
|
|
db.session.add(study_event)
|
|
|
|
db.session.commit()
|
|
|
|
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
@staticmethod
|
2021-03-22 21:46:39 +00:00
|
|
|
def _update_status_of_workflow_meta(workflow_metas, status):
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
# Update the status on each workflow
|
|
|
|
warnings = []
|
|
|
|
for wfm in workflow_metas:
|
2021-03-27 00:25:34 +00:00
|
|
|
wfm.state_message = ''
|
2021-03-22 21:46:39 +00:00
|
|
|
# do we have a status for you
|
2021-03-27 00:25:34 +00:00
|
|
|
if wfm.name not in status.keys():
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
warnings.append(ApiError("missing_status", "No status specified for workflow %s" % wfm.name))
|
2021-03-27 00:25:34 +00:00
|
|
|
continue
|
|
|
|
if not isinstance(status[wfm.name], dict):
|
|
|
|
warnings.append(ApiError(code='invalid_status',
|
|
|
|
message=f'Status must be a dictionary with "status" and "message" keys. Name is {wfm.name}. Status is {status[wfm.name]}'))
|
|
|
|
continue
|
|
|
|
if 'status' not in status[wfm.name].keys():
|
|
|
|
warnings.append(ApiError("missing_status",
|
|
|
|
"Workflow '%s' does not have a status setting" % wfm.name))
|
|
|
|
continue
|
|
|
|
if not WorkflowState.has_value(status[wfm.name]['status']):
|
|
|
|
warnings.append(ApiError("invalid_state",
|
|
|
|
"Workflow '%s' can not be set to '%s', should be one of %s" % (
|
|
|
|
wfm.name, status[wfm.name]['status'], ",".join(WorkflowState.list())
|
|
|
|
)))
|
|
|
|
continue
|
|
|
|
wfm.state = WorkflowState[status[wfm.name]['status']]
|
|
|
|
if 'message' in status[wfm.name].keys():
|
|
|
|
wfm.state_message = status[wfm.name]['message']
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
return warnings
|
|
|
|
|
|
|
|
@staticmethod
|
2021-03-22 21:46:39 +00:00
|
|
|
def _get_workflow_metas(study_id):
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
# Add in the Workflows for each category
|
2020-04-23 23:25:01 +00:00
|
|
|
workflow_models = db.session.query(WorkflowModel). \
|
|
|
|
join(WorkflowSpecModel). \
|
|
|
|
filter(WorkflowSpecModel.is_master_spec == False). \
|
|
|
|
filter(WorkflowModel.study_id == study_id). \
|
2020-03-30 18:01:57 +00:00
|
|
|
all()
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
workflow_metas = []
|
|
|
|
for workflow in workflow_models:
|
|
|
|
workflow_metas.append(WorkflowMetadata.from_workflow(workflow))
|
|
|
|
return workflow_metas
|
|
|
|
|
|
|
|
@staticmethod
|
2021-03-22 21:46:39 +00:00
|
|
|
def _get_study_status(study_model):
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
"""Uses the Top Level Workflow to calculate the status of the study, and it's
|
|
|
|
workflow models."""
|
|
|
|
master_specs = db.session.query(WorkflowSpecModel). \
|
|
|
|
filter_by(is_master_spec=True).all()
|
|
|
|
if len(master_specs) < 1:
|
|
|
|
raise ApiError("missing_master_spec", "No specifications are currently marked as the master spec.")
|
|
|
|
if len(master_specs) > 1:
|
|
|
|
raise ApiError("multiple_master_specs",
|
|
|
|
"There is more than one master specification, and I don't know what to do.")
|
|
|
|
|
2020-03-30 18:01:57 +00:00
|
|
|
return WorkflowProcessor.run_master_spec(master_specs[0], study_model)
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
|
|
|
|
@staticmethod
|
2020-08-10 18:56:33 +00:00
|
|
|
def _add_all_workflow_specs_to_study(study_model: StudyModel):
|
2020-05-25 16:29:05 +00:00
|
|
|
existing_models = session.query(WorkflowModel).filter(WorkflowModel.study == study_model).all()
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
existing_specs = list(m.workflow_spec_id for m in existing_models)
|
|
|
|
new_specs = session.query(WorkflowSpecModel). \
|
|
|
|
filter(WorkflowSpecModel.is_master_spec == False). \
|
|
|
|
filter(WorkflowSpecModel.id.notin_(existing_specs)). \
|
|
|
|
all()
|
|
|
|
errors = []
|
|
|
|
for workflow_spec in new_specs:
|
|
|
|
try:
|
2020-05-25 16:29:05 +00:00
|
|
|
StudyService._create_workflow_model(study_model, workflow_spec)
|
2020-05-30 19:37:04 +00:00
|
|
|
except WorkflowTaskExecException as wtee:
|
2020-06-03 19:03:22 +00:00
|
|
|
errors.append(ApiError.from_task("workflow_startup_exception", str(wtee), wtee.task))
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
except WorkflowException as we:
|
2020-06-03 19:03:22 +00:00
|
|
|
errors.append(ApiError.from_task_spec("workflow_startup_exception", str(we), we.sender))
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
return errors
|
|
|
|
|
|
|
|
@staticmethod
|
2020-05-25 16:29:05 +00:00
|
|
|
def _create_workflow_model(study: StudyModel, spec):
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
workflow_model = WorkflowModel(status=WorkflowStatus.not_started,
|
2020-05-25 16:29:05 +00:00
|
|
|
study=study,
|
2021-04-26 12:46:19 +00:00
|
|
|
user_id=None,
|
2020-05-04 14:57:09 +00:00
|
|
|
workflow_spec_id=spec.id,
|
2021-04-29 14:25:28 +00:00
|
|
|
last_updated=datetime.utcnow())
|
Created a "StudyService" and moved all complex logic around study manipulation out of the study api, and this service, as things were getting complicated. The Workflow Processor no longer creates the WorkflowModel, the study object handles that, and only passes the model into the workflow processor when it is ready to start the workflow.
Created a Study object (seperate from the StudyModel) that can cronstructed on request, and contains a different data structure than we store in the DB. This allows us to return underlying Categories and Workflows in a clean way.
Added a new status to workflows called "not_started", meaning we have not yet instantiated a processor or created a BPMN, they have no version yet and no stored data, just the possiblity of being started.
The Top Level Workflow or "Master" workflow is now a part of the sample data, and loaded at all times.
Removed the ability to "add a workflow to a study" and "remove a workflow from a study", a study contains all possible workflows by definition.
Example data no longer creates users or studies, it just creates the specs.
2020-03-30 12:00:16 +00:00
|
|
|
session.add(workflow_model)
|
|
|
|
session.commit()
|
|
|
|
return workflow_model
|