Updated Personnel (markdown)
parent
d3ece241ff
commit
ce5101718e
|
@ -47,5 +47,9 @@ The next section of the workflow then displays the School and Department informa
|
||||||
|
|
||||||
![image.png](https://images.zenhubusercontent.com/5f0623d8a1d620a9f39301dc/0b4b4ac8-44eb-45e5-8ed4-99ed3093d761)
|
![image.png](https://images.zenhubusercontent.com/5f0623d8a1d620a9f39301dc/0b4b4ac8-44eb-45e5-8ed4-99ed3093d761)
|
||||||
|
|
||||||
|
The next section sets information needed for the PI and Dept. Chair. For the PI, and all remaining personnel, the Coordinator is asked if they should have full access to the study in CRC2 and/or be included in the email notification group. They are also asked to enter the PI's experience if that has not been done yet, or edit it if it has been previously entered, but needs updating. If either of the cases are true, the PI Experience is saved to a user datastore. Next the workflow determines if the PI and Dept. Chair are the same person, and if so, they are informed that someone else will need to sign the Dept. Chair Approval document and that is all that is needed. If they are not, the Coordinator is prompted to specify of the Dept. Chair should have full study access in CRC2 and/or receive email notifications, or not.
|
||||||
|
|
||||||
|
![image.png](https://images.zenhubusercontent.com/5f0623d8a1d620a9f39301dc/68be394b-cdd8-4088-8209-83f3de176170)
|
||||||
|
|
||||||
### Documents
|
### Documents
|
||||||
No documents are produced from this workflow.
|
No documents are produced from this workflow.
|
Loading…
Reference in New Issue