sartography
/
cr-connect-workflow
mirror of https://github.com/sartography/cr-connect-workflow.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
cr-connect-workflow/crc/static/bpmn/research_rampup/research_rampup.bpmn

999 lines
65 KiB
Plaintext
Raw Normal View History

Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<?xml version="1.0" encoding="UTF-8"?>
Process scripts with no shebang (#!) as a regular python script. If there is a shebang, we look up the class as we did before. I've also made it so that it falls back if we accidentally forget to add a shebang to a study as this would be a breaking change. With the fallback feature, it should work with unmodified bpmn documents.
2020-07-17 14:56:04 +00:00
<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:camunda="http://camunda.org/schema/1.0/bpmn" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" id="Definitions_1oogn9j" targetNamespace="http://bpmn.io/schema/bpmn" exporter="Camunda Modeler" exporterVersion="3.7.0">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:process id="Process_0ssahs9" isExecutable="true">
<bpmn:startEvent id="StartEvent_1">
<bpmn:outgoing>SequenceFlow_05ja25w</bpmn:outgoing>
</bpmn:startEvent>
<bpmn:manualTask id="ManualTask_Instructions" name="Read RRP Instructions">
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<bpmn:documentation>### UNIVERSITY OF VIRGINIA RESEARCH
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
[From Research Ramp-up Guidance](https://research.virginia.edu/research-ramp-guidance)
#### Support
Report problems and/or submit questions to: askresearch@virginia.edu
#### Research Guidance
Our general principle is that only research activities requiring on-Grounds presence would be conducted on-Grounds. All other research-related work would continue to be performed by telework until restrictions are lifted. Separate school, department and building specific plans should supplement these guidelines.
For research that needs to be on Grounds, the plan is to ramp up in phases with emphasis on safety. The goal of this document is to provide a central framework for resuming activities while allowing for coordinated school specific implementation strategies.
The success of the ramp up depends on each researcher placing the safety of themselves and the people around them first, while conducting their research. In order to reduce our risks as much as possible, this must be a partnership between the researchers and the administration.
Schools are developing a process for the approval of ramp up requests and enforcement of safety guidelines described in this document. The VPR office is working with the schools to provide the necessary support for business process infrastructure, and working with the COO’s office to coordinate the acquisition of supplies necessary including face coverings and sanitizing supplies.
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
**Instructions for Submitting:**
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
1. The Research Ramp-up Plan allows for one request to be entered for a single Principle Investigator. In the form that follows enter the Primary Investigator this request is for and other identifying information. The PI's School and Supervisor will be used as needed for approval routing.
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
2. Provide all available information in the forms that follow to provide an overview of where the research will resume, who will be involved, what supporting resources will be needed and what steps have been taken to assure compliance with [Research Ramp-up Guidance](https://research.virginia.edu/research-ramp-guidance).
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
3. After all forms have been completed, you will be presented with the option to create your Research Recovery Plan in Word format. Download the document and review it. If you see any corrections that need to be made, return to the corresponding form and make the correction.
More updates
2020-06-01 04:28:37 +00:00
4. Once the generated Research Recovery Plan is finalized, proceed to the Plan Submission step to submit your plan for approval.</bpmn:documentation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:incoming>SequenceFlow_05ja25w</bpmn:incoming>
<bpmn:outgoing>SequenceFlow_0h50bp3</bpmn:outgoing>
</bpmn:manualTask>
<bpmn:userTask id="Activity-PI_Info" name="Enter PI Info" camunda:formKey="PI Information">
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmn:documentation>#### Primary Investigator Information
Enter the following information for the PI submitting this request</bpmn:documentation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:extensionElements>
<camunda:formData>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:formField id="PIComputingID" label="Primary Investigator" type="autocomplete">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:properties>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:property id="placeholder" value="wxy0z or Smith" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:property id="ldap.lookup" value="true" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="autocomplete_num" value="10" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
<camunda:constraint name="description" config="Find the PI by entering Computing ID or Last Name." />
<camunda:constraint name="ldap.lookup" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="PISchool" label="PI&#39;s School" type="enum">
<camunda:properties>
<camunda:property id="spreadsheet.name" value="SchoolList.xls" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="School Name" />
</camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
<camunda:formField id="PIPrimaryDeptArchitecture" label="PI&#39;s Primary Architecture Department" type="enum">
<camunda:properties>
<camunda:property id="spreadsheet.name" value="DepartmentList-Architecture.xlsx" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Label" />
<camunda:property id="hide_expression" value="(model.PISchool &#38;&#38; model.PISchool !== &#34;Architecture&#34;) || model.PISchool === null" />
</camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
<camunda:formField id="PIPrimaryDeptArtsSciences" label="PI&#39;s Primary Arts &#38; Sciences Department" type="enum">
<camunda:properties>
<camunda:property id="spreadsheet.name" value="DepartmentList-ArtsSciences.xlsx" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Label" />
<camunda:property id="hide_expression" value="(model.PISchool &#38;&#38; model.PISchool !== &#34;Arts &#38; Sciences&#34;) || model.PISchool === null" />
<camunda:property id="description" value="Type key words to find department" />
</camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
<camunda:formField id="PIPrimaryDeptEducation" label="PI&#39;s Primary Education Department" type="enum">
<camunda:properties>
<camunda:property id="spreadsheet.name" value="DepartmentList-Education.xlsx" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Label" />
<camunda:property id="hide_expression" value="(model.PISchool &#38;&#38; model.PISchool !== &#34;Education&#34;) || model.PISchool === null" />
</camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
<camunda:formField id="PIPrimaryDeptEngineering" label="PI&#39;s Primary Engineering Department" type="enum">
<camunda:properties>
<camunda:property id="spreadsheet.name" value="DepartmentList-Engineering.xlsx" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Label" />
<camunda:property id="hide_expression" value="(model.PISchool &#38;&#38; model.PISchool !== &#34;Engineering&#34;) || model.PISchool === null" />
</camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
<camunda:formField id="PIPrimaryDeptMedicine" label="PI&#39;s Primary Medicine Department/Center" type="enum">
<camunda:properties>
<camunda:property id="spreadsheet.name" value="DepartmentList-Medicine.xlsx" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Label" />
<camunda:property id="hide_expression" value="(model.PISchool &#38;&#38; model.PISchool !== &#34;Medicine&#34;) || model.PISchool === null" />
</camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:validation>
<camunda:constraint name="required" config="tr" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
<camunda:formField id="PIPrimaryDeptProvostOffice" label="PI&#39;s Primary Provost Office Department/Center" type="enum">
<camunda:properties>
<camunda:property id="spreadsheet.name" value="DepartmentList-ProvostOffice.xlsx" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Label" />
<camunda:property id="hide_expression" value="(model.PISchool &#38;&#38; model.PISchool !== &#34;Provost Office&#34;) || model.PISchool === null" />
</camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
<camunda:formField id="PIPrimaryDeptOther" label="Primary Department " type="string">
<camunda:properties>
<camunda:property id="hide_expression" value="(model.PIPrimaryDeptArchitecture === null &#38;&#38; model.PIPrimaryDeptArtsSciences === null &#38;&#38; model.PIPrimaryDeptEducation === null &#38;&#38; model.PIPrimaryDeptEngineering === null &#38;&#38; model.PIPrimaryDeptMedicine === null &#38;&#38; model.PIPrimaryDeptProvostOffice === null) || (model.PIPrimaryDeptArchitecture !== &#34;Other&#34; &#38;&#38; model.PIPrimaryDeptArtsSciences !== &#34;Other&#34; &#38;&#38; model.PIPrimaryDeptEducation !== &#34;Other&#34; &#38;&#38; model.PIPrimaryDeptEngineering !== &#34;Other&#34; &#38;&#38; model.PIPrimaryDeptMedicine !== &#34;Other&#34; &#38;&#38; model.PIPrimaryDeptProvostOffice !== &#34;Other&#34;)" />
<camunda:property id="description" value="Enter the PI&#39;s Primary Department " />
</camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
<camunda:formField id="PISupervisor" label="Pi&#39;s Supervisor" type="autocomplete">
<camunda:properties>
<camunda:property id="description" value="Find the PI&#39;s Supervisor by entering Computing I D or Last Name." />
<camunda:property id="ldap.lookup" value="true" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:property id="placeholder" value="wxy0z or Smith" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="autocomplete_num" value="10" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
More updates
2020-06-01 04:28:37 +00:00
<camunda:constraint name="required" config="true" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:validation>
</camunda:formField>
</camunda:formData>
</bpmn:extensionElements>
<bpmn:incoming>SequenceFlow_0h50bp3</bpmn:incoming>
<bpmn:outgoing>Flow_16y8glw</bpmn:outgoing>
</bpmn:userTask>
<bpmn:sequenceFlow id="SequenceFlow_0h50bp3" sourceRef="ManualTask_Instructions" targetRef="Activity-PI_Info" />
<bpmn:sequenceFlow id="SequenceFlow_05ja25w" sourceRef="StartEvent_1" targetRef="ManualTask_Instructions" />
More updates
2020-06-01 04:28:37 +00:00
<bpmn:userTask id="Activity_Personnel" name="Enter Personnel" camunda:formKey="Research Personnel">
<bpmn:documentation>#### Personnel for whom you are requesting access
Provide information on all personnel you are requesting approval for reentry into the previously entered lab, workspace and/or office space(s) for conducting research on-Grounds. (If there are personnel already working in the space, include them).
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
#### Exclusive Space previously entered
More updates
2020-06-01 04:28:37 +00:00
{%+ for es in exclusive %}{{ es.ExclusiveSpaceRoomID + " " + es.ExclusiveSpaceBuilding.label }}{% if loop.last %}{% else %}, {% endif %}{% else %}No exclusive space entered{% endfor %}
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
#### Shared Space previously entered
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
{%+ for ss in shared %}{{ ss.SharedSpaceRoomID + " " + ss.SharedSpaceBuilding.label }}{% if loop.last %}{% else %}, {% endif %}{% else %}No shared space entered.{% endfor %}
**Note: no undergraduates will be allowed to work on-Grounds during Phase I.**</bpmn:documentation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:extensionElements>
<camunda:formData>
More updates
2020-06-01 04:28:37 +00:00
<camunda:formField id="HavePersonnel" label="Select one:" type="enum">
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
<camunda:value id="yes" name="I am requesting approval for personnel, in addition to myself, to return to one or more of the labs, workspaces and/or offices previously entered." />
<camunda:value id="no" name="No additional personnel, just myself, will be returning to the labs, workspaces and/or offices previously entered" />
</camunda:formField>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:formField id="PersonnelComputingID" label="Computer ID" type="autocomplete">
<camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="personnel" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:property id="ldap.lookup" value="true" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:property id="description" value="Find by entering Computing ID or Last Name." />
<camunda:property id="placeholder" value="wxy0z or Smith" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="autocomplete_num" value="10" />
<camunda:property id="repeat_hide_expression" value="model.HavePersonnel === &#39;no&#39; | model.HavePersonnel == null" />
<camunda:property id="repeat_title" value="Enter all Personnel who will be working in the previously entered spaces" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat_button_label" value="Add Personnel" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="PersonnelType" label="Personnel Type" type="enum">
<camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="personnel" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:value id="Faculty" name="Faculty" />
<camunda:value id="AcademicResearcher" name="Academic Researcher" />
<camunda:value id="Staff" name="Staff" />
<camunda:value id="Postdoc" name="Postdoc" />
<camunda:value id="DoctoralStudent" name="Doctoral Student" />
<camunda:value id="UndeGraduate" name="Undergraduate" />
</camunda:formField>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:formField id="PersonnelSpace" label="Space they will work in" type="string">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="description" value="Provide room number/identifier and building for each lab, workspace and/or office space this person will be working. If they will be in more than one space, separate with commas." />
<camunda:property id="repeat" value="personnel" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:formField id="PersonnelJustification" label="Research Justification" type="textarea">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:properties>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:property id="description" value="Provide a brief description of this person’s research and justification why this is critical research." />
<camunda:property id="rows" value="3" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:property id="autosize" value="true" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="personnel" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>Flow_0hc1r8a</bpmn:incoming>
<bpmn:outgoing>Flow_1yxaewj</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:userTask>
<bpmn:userTask id="UserTask_CoreResource" name="Enter Core Resources" camunda:formKey="Core Resources">
More updates
2020-06-01 04:28:37 +00:00
<bpmn:documentation>If applicable, provide a list of any [Core Resources](https://research.virginia.edu/research-core-resources) utilization of space and/or instruments along with the name(s) and email(s) of contact person(s) in the core with whom you have coordinated your plan. (Core facility managers are responsible for developing a plan for their space)</bpmn:documentation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:extensionElements>
<camunda:formData>
<camunda:formField id="isCoreResourcesUse" label="Core Resources Use" type="boolean">
<camunda:properties>
<camunda:property id="description" value="Will you need access to core resources to resume research?" />
<camunda:property id="help" value="[From Research Ramp-up Guidance](https://research.virginia.edu/research-ramp-guidance)\n#### ADDITIONAL CONSIDERATIONS FOR A SUCCESSFUL RAMP-UP:\n##### Lab-based Research\n- (1) Core facilities operational\n\n[EHS Lab Ramp up Checklist for Laboratories](https://research.virginia.edu/sites/vpr/files/2020-05/EHS.LabRampUpChecklistForLaboratories_0_0.pdf)\n##### General\n- Note that shared facilities, such as stockrooms or core labs, may be on different ramp up schedules or in more demand than during normal operation." />
</camunda:properties>
</camunda:formField>
<camunda:formField id="CoreResources" label="Core Resources" type="textarea">
<camunda:properties>
<camunda:property id="rows" value="10" />
<camunda:property id="autosize" value="true" />
<camunda:property id="hide_expression" value="!model.isCoreResourcesUse | model.isCoreResourcesUse == null" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="description" value="Provide a list of any core resources utilization of space and/or instruments along with the name(s) and email(s) of contact person(s) in the core with whom you have coordinated your plan." />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
</camunda:formField>
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>Flow_1n69wsr</bpmn:incoming>
<bpmn:outgoing>Flow_13pusfu</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:userTask>
<bpmn:endEvent id="EndEvent_09wp7av">
More updates
2020-06-01 04:28:37 +00:00
<bpmn:documentation>#### End of Research Ramp-up Plan Workflow
Thank you for participating,</bpmn:documentation>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:incoming>Flow_05w8yd6</bpmn:incoming>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:endEvent>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:sequenceFlow id="Flow_1e2qi9s" sourceRef="Activity_AcknowledgePlanReview" targetRef="Activity_ApprovalInfo" />
<bpmn:manualTask id="Activity_AcknowledgePlanReview" name="Acknowledge Plan Review">
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmn:documentation>Your Research Ramp-up Plan has been generated and is available in the Files pop-out found in the upper right hand corner of this application Click on the file name link to download the MS Word file, open and review. If changes are needed, choose the appropriate menu choice to make your edits, clicking Save when done. Note that you will need to revisit subsequent steps so the application can check to see if your edits impacted future workflow decisions. All your data will be persevered and you will need to click the Save button on each step to proceed.
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
When your Research Ramp-up Plan is complete and ready to submit for review and approval, click the Continue button below.</bpmn:documentation>
<bpmn:incoming>Flow_0aqgwvu</bpmn:incoming>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:outgoing>Flow_1e2qi9s</bpmn:outgoing>
</bpmn:manualTask>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:userTask id="Activity_SharedSpaceInfo" name="Enter Shared Space" camunda:formKey="Space Involved in this Request">
<bpmn:documentation>#### Space used by {{ PIComputingID.label }} and shared with other PIs. If all space is exclusive and not shared with one or more other investigators, Click Save to skip this section and proceed to the next section.</bpmn:documentation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:extensionElements>
<camunda:formData>
<camunda:formField id="SharedSpaceBuilding" label="Building Name" type="autocomplete">
<camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="description" value="Select the building where this shared lab, office or workspace space is housed." />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:property id="spreadsheet.name" value="BuildingList.xls" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Building Name" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="shared" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="repeat_title" value="Add one entry for each Shared Space" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat_button_label" value="Add Shared Spaces" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="SharedSpaceRoomID" label="Shared Space Room ID" type="string">
<camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="shared" />
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:property id="description" value="Enter the room number or other unique identifier" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:property id="hide_expression" value="model.SharedSpaceBuilding === &#34;Other&#34;" />
</camunda:properties>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</camunda:formField>
<camunda:formField id="ShareSpaceRoomIDBuilding" label="Room No, and Building Name" type="string">
<camunda:properties>
<camunda:property id="description" value="Enter the Room No and Building of your shared space." />
<camunda:property id="hide_expression" value="model.SharedSpaceBuilding !== &#34;Other&#34; | model.SharedSpaceBuilding === null" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="shared" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
</camunda:formField>
<camunda:formField id="SharedSpaceAMComputingID" label="Area Monitor" type="autocomplete">
<camunda:properties>
<camunda:property id="ldap.lookup" value="true" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:property id="placeholder" value="wxy0z or Smith" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="description" value="Enter Area Monitor&#39;s Computing ID or last name and select. Leave blank if not known." />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="shared" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="autocomplete_num" value="10" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
</camunda:formField>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:formField id="SharedSpaceSqFt" label="Space square Feet" type="long">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="shared" />
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:property id="description" value="Enter the number of square feet in this space." />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:formField id="SharedSpacePercentUsable" label="Percent of Space Usable By Personnel" type="long" defaultValue="100">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="shared" />
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:property id="description" value="If known, enter a number between 1 &#38; 100 which indicates the approximate percent of the total space personnel will work in and move around in during the workday." />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="min" config="1" />
<camunda:constraint name="max" config="100" />
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:constraint name="required" config="true" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:validation>
</camunda:formField>
<camunda:formField id="SharedSpaceMaxPersonnel" label="Maximum Number of Personnel Occupying Space" type="long">
<camunda:properties>
<camunda:property id="description" value="Enter the maximum number of personnel, including yourself, who will occupy this space." />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="shared" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:constraint name="min" config="1" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:validation>
</camunda:formField>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:formField id="SharedSpacePI" label="Shared Space PI(s)" type="textarea">
<camunda:properties>
<camunda:property id="description" value="For each PI you share this space with, enter their Name, School, Department and Email Address." />
<camunda:property id="rows" value="5" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="shared" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>Flow_0o4tg9g</bpmn:incoming>
<bpmn:outgoing>Flow_1n69wsr</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:userTask>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:sequenceFlow id="Flow_16y8glw" sourceRef="Activity-PI_Info" targetRef="Activity_1u58hox" />
<bpmn:userTask id="Activity_ExclusiveSpace" name="Enter Exclusive Space" camunda:formKey="ExclusiveSpace">
<bpmn:documentation>#### Space managed exclusively by {{ PIComputingID.label }}
More updates
2020-06-01 04:28:37 +00:00
Submit one entry for each space the PI is the exclusive investigator. If all space is shared with one or more other investigators, click Save to skip this section and proceed to the Shared Space section.</bpmn:documentation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:extensionElements>
<camunda:formData>
More updates
2020-06-01 04:28:37 +00:00
<camunda:formField id="ExclusiveSpaceBuilding" label="Building Name" type="autocomplete">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="description" value="Type key word to find the building in which the lab, office or workspace is located." />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:property id="spreadsheet.name" value="BuildingList.xls" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Building Name" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="exclusive" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="repeat_title" value="Add one entry for each Exclusive Space" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat_button_label" value="Add Exclusive Spaces" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:formField id="ExclusiveSpaceRoomID" label="Exclusive Space Room ID" type="string">
<camunda:properties>
<camunda:property id="hide_expression" value="model.ExclusiveSpaceBuilding === &#34;Other&#34;" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="exclusive" />
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:property id="description" value="Enter the room number or other unique identifier" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</camunda:properties>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</camunda:formField>
<camunda:formField id="ExclusiveSpaceRoomIDBuilding" label="Room No, and Building Name" type="string">
<camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="description" value="Enter the Room No and Building of your exclusive lab or workspace." />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:property id="hide_expression" value="model.ExclusiveSpaceBuilding !== &#34;Other&#34; | model.ExclusiveSpaceBuilding === null" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="exclusive" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</camunda:properties>
</camunda:formField>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:formField id="ExclusiveSpaceType" label="Space Room Type" type="enum">
<camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="exclusive" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:property id="enum_type" value="radio" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="markdown_description" value="### Note that return to any lab, office or workspace must be for critical reasons only during Phase I" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
<camunda:value id="Lab" name="Lab" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:value id="Office" name="Office/Workspace" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formField>
<camunda:formField id="ExclusiveSpaceAMComputingID" label="Area Monitor" type="autocomplete">
<camunda:properties>
<camunda:property id="ldap.lookup" value="true" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="description" value="Enter Area Monitor&#39;s Computing ID or last name and select. Leave blank if not known." />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="exclusive" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<camunda:property id="placeholder" value="wxy0z or Smith" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="autocomplete_num" value="10" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
</camunda:formField>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:formField id="ExclusiveSpaceSqFt" label="Space Square Feet" type="long">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="exclusive" />
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:property id="description" value="Enter the number of square feet in this space." />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:formField id="ExclusiveSpacePercentUsable" label="Percent of Space Usable By Personnel" type="long" defaultValue="100">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<camunda:properties>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="exclusive" />
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:property id="description" value="If known, enter a number between 1 &#38; 100 which indicates the approximate percent of the total space personnel will work in and move around in during the workday." />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="min" config="1" />
<camunda:constraint name="max" config="100" />
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:constraint name="required" config="true" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:validation>
</camunda:formField>
<camunda:formField id="ExclusiveSpaceMaxPersonnel" label="Maximum Number of Personnel Occupying Space" type="long">
<camunda:properties>
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="description" value="Enter the maximum number of personnel, including yourself, who will occupy this space." />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat" value="exclusive" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:constraint name="min" config="1" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:validation>
</camunda:formField>
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>Flow_0uc4o6c</bpmn:incoming>
<bpmn:outgoing>Flow_0o4tg9g</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:userTask>
<bpmn:userTask id="Activity_nonUVASpaces" name="Enter non-UVA Spaces" camunda:formKey="nonUVA Spaces">
<bpmn:extensionElements>
<camunda:formData>
<camunda:formField id="isNonUVASpaces" label="non-UVA Spaces?" type="boolean">
<camunda:properties>
<camunda:property id="description" value="Does any of your research occur in non-UVA spaces? (For example, field stations or UVA leased buildings off Grounds) " />
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="NonUVASpaces" label="Where?" type="textarea">
<camunda:properties>
<camunda:property id="description" value="Does any of your research occur in non-UVA spaces? (For example, field stations or UVA leased buildings off Grounds) " />
<camunda:property id="hide_expression" value="!model.isNonUVASpaces | model.isNonUVASpaces == null" />
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>Flow_13pusfu</bpmn:incoming>
<bpmn:outgoing>Flow_0hc1r8a</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:userTask>
<bpmn:userTask id="Activity_DistanceReq" name="Enter Distancing Requirements" camunda:formKey="Distancing Requirements">
<bpmn:documentation>#### Distancing requirements:
Maintain social distancing by designing space between people to be at least 9 feet during prolonged work which will be accomplished by restricting the number of people in the lab to a density of ~250 sq. ft. /person in lab areas. When moving around, a minimum of 6 feet social distancing is required. Ideally only one person per lab bench and not more than one person can work at the same time in the same bay.</bpmn:documentation>
<bpmn:extensionElements>
<camunda:formData>
<camunda:formField id="CIDR_TotalSqFt" label="What is the total square footage of your lab?" type="long">
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="CIDR_MaxPersonnel" label="How many personnel will be using the lab at any one time, at a maximum?" type="long">
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>Flow_1itd8db</bpmn:incoming>
<bpmn:outgoing>Flow_1lo964l</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:userTask>
<bpmn:userTask id="Activity_PWA" name="Enter Physical Work Arrangements" camunda:formKey="Physical Work Arrangements">
More updates
2020-06-01 04:28:37 +00:00
<bpmn:documentation>Describe physical work arrangements for each lab, workspace and/or office space previously entered. Show schematic of the space organization to meet the distancing guidelines (see key safety expectations for ramp-up).
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
- Show gross dimensions, location of desks, and equipment in blocks (not details) that show available space for work and foot traffic.
- Indicate total square footage for every lab/space that you are requesting adding personnel to in this application. If you would like help obtaining a floor plan for your lab, your department or deans office can help. You can also create a hand drawing/block diagram of your space and the location of objects on a graph paper.
- Upload your physical layout and workspace organization in the form of a jpg image or a pdf file. This can be hand-drawn or actual floor plans.
- Show and/or describe designated work location for each member (during their shift) in the lab when multiple members are present at a time to meet the distancing guidelines.
More updates
2020-06-01 04:28:37 +00:00
- Provide a foot traffic plan (on the schematic) to indicate how people can move around while maintaining distancing requirements. This can be a freeform sketch on your floor plan showing where foot traffic can occur in your lab, and conditions, if any, to ensure distancing at all times. (e.g., direction to walk around a lab bench, rules for using shared equipment located in the lab, certain areas of lab prohibited from access, etc.).</bpmn:documentation>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:extensionElements>
<camunda:formData>
<camunda:formField id="PWADescribe" label="Describe" type="textarea">
<camunda:properties>
<camunda:property id="rows" value="10" />
<camunda:property id="autosize" value="true" />
More updates
2020-06-01 04:28:37 +00:00
<camunda:property id="help" value=" [From Research Ramp-up Guidance](https://research.virginia.edu/research-ramp-guidance)\n#### KEY SAFETY EXPECTATIONS WHEN WE RAMP UP ACTIVITIES (APPLIES TO ALL ON-GROUNDS RESEARCH):\n\n- Avoid more than one person on an elevator. No congregation in front of elevators and will need to maintain social distancing while waiting.\n- Maintain social distancing by designing space between people to be at least 9 feet during prolonged work which will be accomplished by restricting the number of people in the lab to a density of ~250 sq. ft. /person in lab areas.\n- When moving around, a minimum of 6 feet social distancing is required. Ideally only one person per lab bench and no one can work at the same time in the same bay." />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="PWAFiles" label="Upload supporting files" type="files" />
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>Flow_1lo964l</bpmn:incoming>
<bpmn:outgoing>Flow_0wgdxa6</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:userTask>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:userTask id="Activity_HSR" name="Enter Health Safety Requirements" camunda:formKey="Lab Safety Plan">
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmn:documentation>#### Health Safety Requirements:
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
Use the EHS [Lab Safety Plan During COVID 19 template](https://www.google.com/url?q=http://ehs.virginia.edu/files/Lab-Safety-Plan-During-COVID-19.docx&amp;source=gmail&amp;ust=1590687968958000&amp;usg=AFQjCNE83uGDFtxGkKaxjuXGhTocu-FDmw) to create and upload a copy of your laboratory policy statement to all members which includes at a minimum the following details:
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
- Laboratory face covering rules, use of other PPE use as required
- Adherence to individual schedules, check-in, check out requirements
- Completion of online EHS safety training requirement
- Health self-attestation requirement
- Sanitizing procedures including frequency and type of disinfectants to use
- Where and how to obtain PPE including face covering</bpmn:documentation>
<bpmn:extensionElements>
<camunda:formData>
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:formField id="LabSafetyPlan" label="Upload Lab Safety Plan" type="file" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>Flow_0wgdxa6</bpmn:incoming>
<bpmn:outgoing>Flow_0judgmp</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:userTask>
<bpmn:userTask id="Activity_OtherReq" name="Enter Other Requirements" camunda:formKey="Other Requirements">
<bpmn:extensionElements>
<camunda:formData>
<camunda:formField id="isAnimalResearch" label="Will you be using animals in your research? " type="boolean">
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="isAnimalResearchCoordinated" label="Have you coordinated with the vivarium manager to meet your needs?" type="boolean">
<camunda:properties>
<camunda:property id="hide_expression" value="!model.isAnimalResearch | model.isAnimalResearch == null" />
</camunda:properties>
</camunda:formField>
<camunda:formField id="isHumanSubjects" label="Does your research involve human subjects? " type="boolean">
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="IRBApprovalRelevantNumbers" label="List IRB Approval Relevant Numbers" type="textarea">
<camunda:properties>
<camunda:property id="rows" value="5" />
<camunda:property id="hide_expression" value="!model.isHumanSubjects | model.isHumanSubjects == null" />
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="isNecessarySupplies" label="Do you have the necessary materials, supplies, cleaning supplies and PPE for your laboratory?" type="boolean">
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="SupplyList" label="List your needs" type="textarea">
<camunda:properties>
<camunda:property id="hide_expression" value="model.isNecessarySupplies | model.isNecessarySupplies == null" />
<camunda:property id="rows" value="5" />
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>Flow_0judgmp</bpmn:incoming>
<bpmn:outgoing>Flow_11uqavk</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:userTask>
<bpmn:manualTask id="Activity_SubmitPlan" name="Acknowledge Plan Submission">
<bpmn:documentation>#### By submitting this request, you understand that every member listed in this form for on Grounds laboratory access will:
More updates
2020-06-01 04:28:37 +00:00
- Complete [online COVID awareness &amp; precaution training module](https://researchcompliance.web.virginia.edu/training_html5/module_content/154/index.cfm)
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
- Complete daily health acknowledgement form signed (electronically) –email generated daily to those listed on your plan for access to on Grounds lab/research space
- Fill out daily work attendance log for all lab members following your school process to check-in and out of work each day.</bpmn:documentation>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:incoming>Flow_08njvvi</bpmn:incoming>
<bpmn:outgoing>Flow_0j4rs82</bpmn:outgoing>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:manualTask>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:scriptTask id="Activity_GenerateRRP" name="Generate RRP">
<bpmn:documentation>#### Script Task
This step is internal to the system and do not require and user interaction</bpmn:documentation>
<bpmn:incoming>Flow_11uqavk</bpmn:incoming>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:outgoing>Flow_0aqgwvu</bpmn:outgoing>
Fix several bugs, most had an issue with the bpmn document
2020-07-27 16:02:34 +00:00
<bpmn:script>complete_template('ResearchRampUpPlan.docx','RESEARCH_RAMPUP')</bpmn:script>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:scriptTask>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:sequenceFlow id="Flow_0aqgwvu" sourceRef="Activity_GenerateRRP" targetRef="Activity_AcknowledgePlanReview" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:sequenceFlow id="Flow_0j4rs82" sourceRef="Activity_SubmitPlan" targetRef="Activity_0absozl" />
More updates
2020-06-01 04:28:37 +00:00
<bpmn:sequenceFlow id="Flow_07ge8uf" sourceRef="Activity_0absozl" targetRef="Activity_1sq56an" />
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmn:userTask id="Activity_RequestStatus" name="Check-on Request Status" camunda:formKey="Rquest Status">
<bpmn:documentation>#### Approval Process
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
The Research Ramp-up Plan and associated documents will be reviewed by{{ " " + ApprvlApprvrName1 }}{{ '.' if ApprvlApprvrName2 == 'n/a' else ' and ' + ApprvlApprvrName2 + '.' }}
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
While waiting for approval, be sure that all required training has been completed and supplies secured. Additionally, if any Area Monitors were not known prior to submission, they will need to be discovered before proceeding.
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
When the approval email notification is received, confirming the three questions below and adding any missing Area Monitors will enable the Save button.
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
If a rejection notification is received, go back to the first step that needs to be addressed and step through each subsequent form from that point.</bpmn:documentation>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:extensionElements>
<camunda:formData>
<camunda:formField id="ApprovalReceived" label="Please Confirm:" type="enum">
<camunda:properties>
<camunda:property id="enum_type" value="checkbox" />
</camunda:properties>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:value id="ApprovalNotificationReceived" name="Approval Notification Received?" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</camunda:formField>
<camunda:formField id="RequiredTraining" label="Please Confirm:" type="enum">
<camunda:properties>
<camunda:property id="enum_type" value="checkbox" />
</camunda:properties>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:value id="AllRequiredTraining" name="All Required Training Completed?" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</camunda:formField>
<camunda:formField id="NeededSupplies" label="Please Confirm&#34;" type="enum">
<camunda:properties>
<camunda:property id="enum_type" value="checkbox" />
</camunda:properties>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<camunda:value id="NeededSupplies" name="All Needed Supplies Secured?" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</camunda:formField>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:formField id="ExclusiveSpaceBuilding" label="Room No. &#38; Building Name" type="autocomplete">
<camunda:properties>
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:property id="repeat" value="exclusive" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:property id="read_only" value="true" />
<camunda:property id="spreadsheet.name" value="Buildinglist.xls" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Building Name" />
<camunda:property id="repeat_title" value="Any missing Area Monitors for Exclusive Spaces must be entered" />
<camunda:property id="repeat_hide_expression" value="model.isAllExclusiveAreaMonitors" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat_edit_only" value="true" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
</camunda:properties>
</camunda:formField>
<camunda:formField id="ExclusiveSpaceRoomID" label="Exclusive Space Room ID" type="string">
<camunda:properties>
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:property id="repeat" value="exclusive" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:property id="read_only" value="true" />
</camunda:properties>
</camunda:formField>
<camunda:formField id="ExclusiveSpaceType" label="Space Room Type" type="enum">
<camunda:properties>
<camunda:property id="read_only" value="true" />
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:property id="repeat" value="exclusive" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
</camunda:properties>
<camunda:value id="Lab" name="Lab" />
<camunda:value id="Office" name="Office" />
</camunda:formField>
<camunda:formField id="ExclusiveSpaceAMComputingID" label="Area Monitor" type="autocomplete">
<camunda:properties>
<camunda:property id="ldap.lookup" value="true" />
<camunda:property id="placeholder" value="wxy0z or Smith" />
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:property id="repeat" value="exclusive" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
<camunda:formField id="SharedSpaceBuilding" label="Building Name" type="autocomplete">
<camunda:properties>
<camunda:property id="spreadsheet.name" value="Buildinglist.xls" />
<camunda:property id="spreadsheet.value.column" value="Value" />
<camunda:property id="spreadsheet.label.column" value="Building Name" />
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:property id="repeat" value="shared" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:property id="repeat_title" value="Any missing Area Monitors for Shared Spaces must be entered" />
<camunda:property id="read_only" value="true" />
<camunda:property id="repeat_hide_expression" value="model.isAllSharedAreaMonitors" />
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
<camunda:property id="repeat_edit_only" value="true" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
</camunda:properties>
</camunda:formField>
<camunda:formField id="SharedSpaceRoomID" label="Shared Space Room ID" type="string">
<camunda:properties>
<camunda:property id="read_only" value="true" />
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:property id="repeat" value="shared" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
</camunda:properties>
</camunda:formField>
<camunda:formField id="SharedSpaceAMComputingID" label="Area Monitor" type="autocomplete">
<camunda:properties>
<camunda:property id="ldap.lookup" value="true" />
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<camunda:property id="repeat" value="shared" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<camunda:property id="placeholder" value="wxy0z or Smith" />
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</camunda:formData>
</bpmn:extensionElements>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:outgoing>SequenceFlow_0qc39tw</bpmn:outgoing>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmn:userTask>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmn:sequenceFlow id="Flow_05w8yd6" sourceRef="Activity_WhatNext" targetRef="EndEvent_09wp7av" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:sequenceFlow id="Flow_08njvvi" sourceRef="Activity_ApprovalInfo" targetRef="Activity_SubmitPlan" />
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmn:businessRuleTask id="Activity_ApprovalInfo" name="Assign Approval Info" camunda:decisionRef="Decision_ApprovalInfo">
More updates
2020-06-01 04:28:37 +00:00
<bpmn:documentation>#### Business Rule Task
This step is internal to the system and do not require and user interaction</bpmn:documentation>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:incoming>Flow_1e2qi9s</bpmn:incoming>
<bpmn:outgoing>Flow_08njvvi</bpmn:outgoing>
</bpmn:businessRuleTask>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmn:manualTask id="Activity_WhatNext" name="Review What&#39;s Next?">
<bpmn:documentation>### Stay Here, In Case Something Changes
If anything changes in the Research Ramp-up Plan submitted, click **Start over** at the top of the menu and step through each form, updating as needed. Data will be preserved, so if no changes are needed on a specific form, click Save and proceed.
If notification is received that the Research Ramp-up Plan approval process is no longer required, click Continue to close out the workflow process.</bpmn:documentation>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:incoming>Flow_0cpmvcw</bpmn:incoming>
<bpmn:outgoing>Flow_05w8yd6</bpmn:outgoing>
</bpmn:manualTask>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmn:sequenceFlow id="Flow_0cpmvcw" sourceRef="Activity_AreaMonitorNotification" targetRef="Activity_WhatNext" />
<bpmn:manualTask id="Activity_AreaMonitorNotification" name="Send Area Monitor Notification">
<bpmn:documentation>#### Ready to Ramp-up Research
Notify the Area Monitor for
More updates
2020-06-01 04:28:37 +00:00
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
#### Exclusive Space
{%+ for es in exclusive %}{{ es.ExclusiveSpaceRoomID + " " + es.ExclusiveSpaceBuilding.label + " - " }}{% if es.ExclusiveSpaceAMComputingID is not defined %}No Area Monitor entered{% else %}{{ es.ExclusiveSpaceAMComputingID.label }}{% endif %}{% if loop.last %}{% else %}, {% endif %}{% else %}No exclusive space entered{% endfor %}
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
More updates
2020-06-01 04:28:37 +00:00
The complete_template script might not grab the correct document when validating, fixed. Updated to latest RRT files, and passing.
2020-06-01 16:33:58 +00:00
#### Shared Space
{%+ for ss in shared %}{{ ss.SharedSpaceRoomID + " " + ss.SharedSpaceBuilding.label + " - " }}{% if ss.SharedSpaceAMComputingID is not defined %}No Area Monitor entered{% else %}{{ ss.SharedSpaceAMComputingID.label }}{% endif %}{% if loop.last %}{% else %}, {% endif %}{% else %}No shared space entered.{% endfor %}</bpmn:documentation>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:incoming>SequenceFlow_0qc39tw</bpmn:incoming>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:outgoing>Flow_0cpmvcw</bpmn:outgoing>
</bpmn:manualTask>
<bpmn:scriptTask id="Activity_0absozl" name="Execute Plan Submission">
More updates
2020-06-01 04:28:37 +00:00
<bpmn:documentation>#### Script Task
This step is internal to the system and do not require and user interaction</bpmn:documentation>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:incoming>Flow_0j4rs82</bpmn:incoming>
<bpmn:outgoing>Flow_07ge8uf</bpmn:outgoing>
Fix several bugs, most had an issue with the bpmn document
2020-07-27 16:02:34 +00:00
<bpmn:script>request_approval('ApprvlApprvr1','ApprvlApprvr2')</bpmn:script>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmn:scriptTask>
<bpmn:scriptTask id="Activity_1u58hox" name="Update Request">
More updates
2020-06-01 04:28:37 +00:00
<bpmn:documentation>#### Script Task
This step is internal to the system and do not require and user interaction</bpmn:documentation>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmn:incoming>Flow_16y8glw</bpmn:incoming>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:outgoing>Flow_0uc4o6c</bpmn:outgoing>
Replace all legacy style calls with new calls. Still having issues where we try to eval an empty definition, not quite sure why there is a difference from what we had before. I may need to revert some of it and determine what is going on.
2020-07-24 18:33:24 +00:00
<bpmn:script>update_study('title:PIComputingID.label','pi:PIComputingID.value')</bpmn:script>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmn:scriptTask>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:userTask id="PersonnelSchedule" name="Upload Weekly Personnel Schedule(s)" camunda:formKey="Personnel Weekly Schedule">
<bpmn:documentation>#### Weekly Personnel Schedule(s)
Provide initial weekly schedule(s) for the PI and all personnel for whom access has been requested, indicating each space they will be working in and all shifts, if applicable.
##### Personnel and spaces they will work in previously entered
{%+ for p in personnel %}{{ p.PersonnelComputingID.label + " - " + p.PersonnelSpace }}{% if loop.last %}{% else %}; {% endif %}{% endfor %}
**Note:** If any schedule changes after approval, please re-submit revised schedule(s) here for re-approval.</bpmn:documentation>
<bpmn:extensionElements>
<camunda:formData>
<camunda:formField id="PersonnelWeeklySchedule" label="Upload Personnel Weekly Schedule(s)" type="files">
<camunda:properties>
<camunda:property id="description" value="Upload a file or files of proposed weekly schedules for the PI and all personnel which were entered and representative of compliance with ramp-up guidance." />
</camunda:properties>
<camunda:validation>
<camunda:constraint name="required" config="true" />
</camunda:validation>
</camunda:formField>
</camunda:formData>
</bpmn:extensionElements>
<bpmn:incoming>Flow_1yxaewj</bpmn:incoming>
<bpmn:outgoing>Flow_1itd8db</bpmn:outgoing>
</bpmn:userTask>
<bpmn:sequenceFlow id="Flow_0uc4o6c" sourceRef="Activity_1u58hox" targetRef="Activity_ExclusiveSpace" />
<bpmn:sequenceFlow id="Flow_0o4tg9g" sourceRef="Activity_ExclusiveSpace" targetRef="Activity_SharedSpaceInfo" />
<bpmn:sequenceFlow id="Flow_1n69wsr" sourceRef="Activity_SharedSpaceInfo" targetRef="UserTask_CoreResource" />
<bpmn:sequenceFlow id="Flow_13pusfu" sourceRef="UserTask_CoreResource" targetRef="Activity_nonUVASpaces" />
<bpmn:sequenceFlow id="Flow_1yxaewj" sourceRef="Activity_Personnel" targetRef="PersonnelSchedule" />
<bpmn:sequenceFlow id="Flow_1itd8db" sourceRef="PersonnelSchedule" targetRef="Activity_DistanceReq" />
<bpmn:sequenceFlow id="Flow_1lo964l" sourceRef="Activity_DistanceReq" targetRef="Activity_PWA" />
<bpmn:sequenceFlow id="Flow_0wgdxa6" sourceRef="Activity_PWA" targetRef="Activity_HSR" />
<bpmn:sequenceFlow id="Flow_0judgmp" sourceRef="Activity_HSR" targetRef="Activity_OtherReq" />
<bpmn:sequenceFlow id="Flow_11uqavk" sourceRef="Activity_OtherReq" targetRef="Activity_GenerateRRP" />
<bpmn:sequenceFlow id="Flow_0peeyne" sourceRef="Activity_1sq56an" targetRef="Activity_14xt8is" />
<bpmn:businessRuleTask id="Activity_1sq56an" name="Check Exclusive Area Monitors" camunda:decisionRef="Decision_ExclusiveAMCheck">
<bpmn:documentation>#### Business Rule Task
This step is internal to the system and do not require and user interaction</bpmn:documentation>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<bpmn:incoming>Flow_07ge8uf</bpmn:incoming>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:outgoing>Flow_0peeyne</bpmn:outgoing>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
</bpmn:businessRuleTask>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:sequenceFlow id="Flow_0tqna2m" sourceRef="Activity_14xt8is" targetRef="Activity_RequestStatus" />
<bpmn:businessRuleTask id="Activity_14xt8is" name="Check Shared Area Monitors" camunda:decisionRef="Decision_SharedAMCheck">
<bpmn:documentation>#### Business Rule Task
This step is internal to the system and do not require and user interaction</bpmn:documentation>
<bpmn:incoming>Flow_0peeyne</bpmn:incoming>
<bpmn:outgoing>Flow_0tqna2m</bpmn:outgoing>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
</bpmn:businessRuleTask>
More updates
2020-06-01 04:28:37 +00:00
<bpmn:sequenceFlow id="Flow_0hc1r8a" sourceRef="Activity_nonUVASpaces" targetRef="Activity_Personnel" />
<bpmn:sequenceFlow id="SequenceFlow_0qc39tw" sourceRef="Activity_RequestStatus" targetRef="Activity_AreaMonitorNotification" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmn:process>
<bpmndi:BPMNDiagram id="BPMNDiagram_1">
<bpmndi:BPMNPlane id="BPMNPlane_1" bpmnElement="Process_0ssahs9">
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="SequenceFlow_0qc39tw_di" bpmnElement="SequenceFlow_0qc39tw">
<di:waypoint x="3290" y="117" />
<di:waypoint x="3330" y="117" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_0hc1r8a_di" bpmnElement="Flow_0hc1r8a">
<di:waypoint x="1260" y="117" />
<di:waypoint x="1310" y="117" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_0tqna2m_di" bpmnElement="Flow_0tqna2m">
<di:waypoint x="3140" y="117" />
<di:waypoint x="3190" y="117" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_0peeyne_di" bpmnElement="Flow_0peeyne">
<di:waypoint x="2990" y="117" />
<di:waypoint x="3040" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_11uqavk_di" bpmnElement="Flow_11uqavk">
<di:waypoint x="2120" y="117" />
<di:waypoint x="2170" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_0judgmp_di" bpmnElement="Flow_0judgmp">
<di:waypoint x="1980" y="117" />
<di:waypoint x="2020" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_0wgdxa6_di" bpmnElement="Flow_0wgdxa6">
<di:waypoint x="1840" y="117" />
<di:waypoint x="1880" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_1lo964l_di" bpmnElement="Flow_1lo964l">
<di:waypoint x="1700" y="117" />
<di:waypoint x="1740" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_1itd8db_di" bpmnElement="Flow_1itd8db">
<di:waypoint x="1550" y="117" />
<di:waypoint x="1600" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_1yxaewj_di" bpmnElement="Flow_1yxaewj">
<di:waypoint x="1410" y="117" />
<di:waypoint x="1450" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_13pusfu_di" bpmnElement="Flow_13pusfu">
<di:waypoint x="1100" y="117" />
<di:waypoint x="1160" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNEdge id="Flow_1n69wsr_di" bpmnElement="Flow_1n69wsr">
<di:waypoint x="950" y="117" />
<di:waypoint x="1000" y="117" />
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="Flow_0o4tg9g_di" bpmnElement="Flow_0o4tg9g">
Updates RRT workflow spec files
2020-06-01 17:29:57 +00:00
<di:waypoint x="790" y="117" />
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="850" y="117" />
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="Flow_0uc4o6c_di" bpmnElement="Flow_0uc4o6c">
<di:waypoint x="630" y="117" />
Updates RRT workflow spec files
2020-06-01 17:29:57 +00:00
<di:waypoint x="690" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<bpmndi:BPMNEdge id="Flow_0cpmvcw_di" bpmnElement="Flow_0cpmvcw">
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="3430" y="117" />
<di:waypoint x="3480" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<bpmndi:BPMNEdge id="Flow_08njvvi_di" bpmnElement="Flow_08njvvi">
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="2560" y="117" />
<di:waypoint x="2610" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<bpmndi:BPMNEdge id="Flow_05w8yd6_di" bpmnElement="Flow_05w8yd6">
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="3580" y="117" />
<di:waypoint x="3652" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<bpmndi:BPMNEdge id="Flow_07ge8uf_di" bpmnElement="Flow_07ge8uf">
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="2850" y="117" />
<di:waypoint x="2890" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<bpmndi:BPMNEdge id="Flow_0j4rs82_di" bpmnElement="Flow_0j4rs82">
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="2710" y="117" />
<di:waypoint x="2750" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
<bpmndi:BPMNEdge id="Flow_0aqgwvu_di" bpmnElement="Flow_0aqgwvu">
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="2270" y="117" />
<di:waypoint x="2310" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="Flow_16y8glw_di" bpmnElement="Flow_16y8glw">
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="480" y="117" />
<di:waypoint x="530" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="Flow_1e2qi9s_di" bpmnElement="Flow_1e2qi9s">
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="2410" y="117" />
<di:waypoint x="2460" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="SequenceFlow_05ja25w_di" bpmnElement="SequenceFlow_05ja25w">
Updates RRT workflow spec files
2020-06-01 17:29:57 +00:00
<di:waypoint x="148" y="117" />
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="230" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
<bpmndi:BPMNEdge id="SequenceFlow_0h50bp3_di" bpmnElement="SequenceFlow_0h50bp3">
More updates
2020-06-01 04:28:37 +00:00
<di:waypoint x="330" y="117" />
<di:waypoint x="380" y="117" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNEdge>
<bpmndi:BPMNShape id="_BPMNShape_StartEvent_2" bpmnElement="StartEvent_1">
Updates RRT workflow spec files
2020-06-01 17:29:57 +00:00
<dc:Bounds x="112" y="99" width="36" height="36" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="ManualTask_1ofy9yz_di" bpmnElement="ManualTask_Instructions">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="230" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="UserTask_0xdpoxl_di" bpmnElement="Activity-PI_Info">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="380" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNShape id="UserTask_0ecab9j_di" bpmnElement="Activity_Personnel">
<dc:Bounds x="1310" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="UserTask_0l8vxty_di" bpmnElement="UserTask_CoreResource">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="1000" y="77" width="100" height="80" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="EndEvent_09wp7av_di" bpmnElement="EndEvent_09wp7av">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="3652" y="99" width="36" height="36" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmndi:BPMNShape id="Activity_1mg5lp9_di" bpmnElement="Activity_AcknowledgePlanReview">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="2310" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
<bpmndi:BPMNShape id="Activity_1xgrlzr_di" bpmnElement="Activity_SharedSpaceInfo">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="850" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
For the main approval endpoints - we now group the approvals by study. So you get one record back for each study, but it may have other approvals along with it as "related_approvals". We now cache the LDAP records - so we look in our own database for the record before calling out to ldap for the details when given a straight up computing id like dhf8r. Added "date_approved" to the approval model. And moved the approver and primary investigator into real associated models to make it easier to dump. Fixed a problem with the validation that was causing it to throw incorrect errors on valid workflows. Getting it to behave a little more like the front end behaves, and respecting the read-only fields. But it was mainly to do with always returning all the data with each form submission.
2020-06-02 22:17:00 +00:00
<bpmndi:BPMNShape id="Activity_1jefdme_di" bpmnElement="Activity_ExclusiveSpace">
<dc:Bounds x="690" y="77" width="100" height="80" />
</bpmndi:BPMNShape>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
<bpmndi:BPMNShape id="Activity_0ysw6zo_di" bpmnElement="Activity_nonUVASpaces">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="1160" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="Activity_1xag6qb_di" bpmnElement="Activity_DistanceReq">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="1600" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="Activity_166b0qq_di" bpmnElement="Activity_PWA">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="1740" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="Activity_0byj9mp_di" bpmnElement="Activity_HSR">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="1880" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="Activity_0j0p13i_di" bpmnElement="Activity_OtherReq">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="2020" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="Activity_1h30fo8_di" bpmnElement="Activity_SubmitPlan">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="2610" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNShape id="Activity_117owwi_di" bpmnElement="Activity_GenerateRRP">
<dc:Bounds x="2170" y="77" width="100" height="80" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmndi:BPMNShape>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmndi:BPMNShape id="Activity_0fxf44t_di" bpmnElement="Activity_RequestStatus">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="3190" y="77" width="100" height="80" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="Activity_080o38p_di" bpmnElement="Activity_ApprovalInfo">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="2460" y="77" width="100" height="80" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmndi:BPMNShape>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmndi:BPMNShape id="Activity_0wuukfn_di" bpmnElement="Activity_WhatNext">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="3480" y="77" width="100" height="80" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmndi:BPMNShape>
Updates RRT workflow spec files
2020-05-29 14:49:47 +00:00
<bpmndi:BPMNShape id="Activity_0js9ww9_di" bpmnElement="Activity_AreaMonitorNotification">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="3330" y="77" width="100" height="80" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="Activity_0wnn9de_di" bpmnElement="Activity_0absozl">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="2750" y="77" width="100" height="80" />
Updates RRT workflow spec files
2020-05-28 14:43:03 +00:00
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="Activity_0f0ak6p_di" bpmnElement="Activity_1u58hox">
More updates
2020-06-01 04:28:37 +00:00
<dc:Bounds x="530" y="77" width="100" height="80" />
</bpmndi:BPMNShape>
<bpmndi:BPMNShape id="Activity_11iexzh_di" bpmnElement="PersonnelSchedule">
<dc:Bounds x="1450" y="77" width="100" height="80" />
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNShape>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNShape id="Activity_0r358ps_di" bpmnElement="Activity_1sq56an">
<dc:Bounds x="2890" y="77" width="100" height="80" />
Updates RRT workflow spec files for reals this time
2020-06-01 04:14:09 +00:00
</bpmndi:BPMNShape>
More updates
2020-06-01 04:28:37 +00:00
<bpmndi:BPMNShape id="Activity_1i34vt6_di" bpmnElement="Activity_14xt8is">
<dc:Bounds x="3040" y="77" width="100" height="80" />
Run the validation process twice, each time it is requested, first populating everything, and then a second time using on the required form fields.
2020-05-30 22:43:20 +00:00
</bpmndi:BPMNShape>
Fixing add_study api endpoint, so you can actually add a new "Study" with just some basic information. Using the LDAP service for checking user details in development mode - even if you are using the back door. Added a new Flask fucntion load-example-rrt-data that loads the rrt workflow, and not the CRC wrokflows. Modified the "load-example-data" in the tests to use some test data, rather than loading up all the workflows[ in CRC each time, with a parameter to load crc data if that is required - which is enabled for just a handful of tests. (Tests run in 1/4 the time now)
2020-05-25 16:29:05 +00:00
</bpmndi:BPMNPlane>
</bpmndi:BPMNDiagram>
</bpmn:definitions>