cr-connect-workflow

data

I had to give up and live with the idea that we can only render documentation on the current task, not on the previous or next tasks. I think this is ok. If you want to view a task, you need to make it the active task to assure all the parts and pieces are in place.

2020-05-06 13:01:38 -04:00

__init__.py

Lots and lots of random stuff as I organize code and get things to make sense.

2019-12-18 14:02:17 -05:00

base_test.py

Updated the study status to use a different enumeration. Migration correctly handles modifying the enum.

2020-04-21 17:13:30 -04:00

test_authentication.py

It became impossible to use the Swagger ui when we started adding authentication to all of the calls. I discovered Connexion and Swagger have a default way of handing JTW authentication and this cleans up our code quite a bit, moves the securing of endpoints into the API Definition, which is quite nice, and removes a whole library dependency (I never get to do that!) I added a SWAGGER_AUTH_KEY that can be used in non-production environments to allow users to quickly authenticate from the Swagger ui. I also removed all api calls to simple little happy api services, because that is just mean and pointless.

2020-03-24 14:15:21 -04:00

test_files_api.py

Updates all workflow specs to match staging

2020-04-27 22:54:05 -04:00

test_ldap_service.py

fixing a bunch of stupid mistakes because I am tried.

2020-04-20 20:28:12 -04:00

test_protocol_builder.py

Server isn't erroring out, but can't find the lookup table id in the database, so trying to use the in-memory model instead, to give things time to get to the database. Really unsure what is happening here. Hard to see in the database.

2020-04-24 07:01:32 -04:00

test_study_api.py

Refactor the stats models, and assure they are very correct across all tests with the workflow api.

2020-05-04 10:57:09 -04:00

test_study_details_documents.py

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.

2020-04-29 15:08:11 -04:00

test_study_service.py

Merge branch 'feature/protocol_status' into feature/previous_task

2020-05-04 11:08:36 -04:00

test_tasks_api.py

Updated to use the latest script engine / evaluation engine that creates a single location where all values used in BPMN/DMN are processed. Right now this is a python based interpreter, but we will eventually base this on FEEL expressions.

2020-05-11 17:04:05 -04:00

test_tools_api.py

missed some test errors in the last push. Just fixing the tests.

2020-03-05 11:23:22 -05:00

test_workflow_processor_multi_instance.py

Setting JSON_SORT_KEYS to false, assuring that Flask does not resort all data returned to the front end.

2020-05-06 10:59:49 -04:00

test_workflow_processor.py

Updated to use the latest script engine / evaluation engine that creates a single location where all values used in BPMN/DMN are processed. Right now this is a python based interpreter, but we will eventually base this on FEEL expressions.

2020-05-11 17:04:05 -04:00

test_workflow_service.py

Refactor the stats models, and assure they are very correct across all tests with the workflow api.

2020-05-04 10:57:09 -04:00

test_workflow_spec_api.py

If you name add a file to a workflow that has the exact same name as a Task Spec's ID, and an extension of "md", it wll use that file as the markdown content, and ignore the markdown in the documentation on the task spec.

2020-04-17 13:30:32 -04:00

test_workflow_spec_validation_api.py

Updated to use the latest script engine / evaluation engine that creates a single location where all values used in BPMN/DMN are processed. Right now this is a python based interpreter, but we will eventually base this on FEEL expressions.

2020-05-11 17:04:05 -04:00