cr-connect-workflow/tests/data
Dan Funk 860c475b29 Fill out repeating sections during validation process.
Also, when returning error messages, attempt to include the task data for the task that caused the error.
Also, when attempting to delete any file, respond with an API error explaining the issue, and log the details.
2020-05-30 15:37:04 -04:00
..
decision_table Assure DMN can pick up name rather than label outputs. 2020-04-20 19:26:42 -04:00
docx A major refactor of how we search and store files, as there was a lot of confusing bits in here. 2020-05-28 08:27:26 -04:00
empty_workflow forgot to include the new empty master workflow, which allows the tests to all pass. 2020-05-22 15:31:38 -04:00
enum_options_from_file Lookup Service now raises exact matches to the top. Very hackish, but it works. 2020-05-27 14:36:10 -04:00
enum_options_with_search Faster lookup fields. We were parsing the spec each time to get details about how to search. We're just grabbing the workflow id and task id now and building that straight into the full text search index for faster lookups. Should be peppy. 2020-05-29 01:39:39 -04:00
exclusive_gateway massive overhaul of the Workflow API endpoint. 2020-05-15 15:54:53 -04:00
exclusive_gateway_2 Forgot to fix another test and to add the example file used for a previous test. 2020-05-16 15:38:15 -04:00
file_upload_form Renamed the required_docs script to just "documents", and it returns all documented in the irb_documents look up table indexed on the "Code" - so details become available in the task data like "documents.IRB_INFOSEC_DOC.required". 2020-04-06 16:56:00 -04:00
invalid_expression Vastly more informative ApiError model that provides details on the underlying task where the error occured. 2020-03-27 08:29:31 -04:00
invalid_script Vastly more informative ApiError model that provides details on the underlying task where the error occured. 2020-03-27 08:29:31 -04:00
invalid_spec Fixes #12: Catching some specific common errors and re-raising as APIErrors with detailed codes and descriptions to improve debugging. In doing so, improving the error handling in the event a soft-reset causes an immediate error - and resetting to the original version of the specification in these events, to allow users the chance to try a hard reset instead. 2020-03-11 16:33:18 -04:00
ldap_lookup ldap lookup. 2020-05-19 16:11:43 -04:00
manual_task_with_external_documentation We can now collect, and provide "extension properties" on a task as set in the camunda modeler. 2020-04-21 12:07:59 -04:00
multi_instance Fixing some failing tests. Moved the task properties into a dictionary, but moving the form field properties to a dictionary will be a larger effort that we don't want to get into on either the back or front end right this moment. 2020-05-14 14:39:14 -04:00
multi_instance_parallel 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
parallel_tasks Standardizing the script tasks that can be executed on the server, adding tons of error messages for when things go wrong. All scripts must exist in side of the crc/scripts directory. 2020-03-03 13:52:45 -05:00
pb_responses Updates all workflow specs to match staging 2020-04-27 22:54:05 -04:00
random_fact Standardizing the script tasks that can be executed on the server, adding tons of error messages for when things go wrong. All scripts must exist in side of the crc/scripts directory. 2020-03-03 13:52:45 -05:00
repeat_form Fill out repeating sections during validation process. 2020-05-30 15:37:04 -04:00
study_details Standardizing the script tasks that can be executed on the server, adding tons of error messages for when things go wrong. All scripts must exist in side of the crc/scripts directory. 2020-03-03 13:52:45 -05:00
subprocess Verifying Sub-Process works, and adding a field to expose a hint as to the sub-process in which the task occurs. 2020-04-28 13:48:44 -04:00
top_level_workflow 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
two_forms throw a sensible error when study is not found on get_study (don't 500) 2020-04-08 13:28:43 -04:00
ldap_response.json Adding a new reference file that provides greater details about the investigators related to a study. 2020-05-07 13:57:24 -04:00
table.docx New set of "Tools" api endpoints, that provides a way to quickly render markdown or word documents by uploading json data and a template to populate. 2020-02-29 17:22:38 -05:00