KRACOEUS-7072
KRACOEUS-7072
KRACOEUS-6652:   Code changes to complete IACUC functionality and to not require a schedule in order to assign reviewers on a modify submission. Fix for IRB committee not displaying correctly.
KRACOEUS-7071
KRACOEUS-7071
KRACOEUS-7097: Sponsor name not updating in Prop Dev
KRACOEUS-6601,IRB-Notify Committee Issues
KRACOEUS-6652: Fixes for user testing issues and side effects from KRACOEUS-6601 changes in the Assign Reviewers authorizers.
KRACOEUS-6802,Notify IRB - hide committee when user is not authorized to assign committee
KRACOEUS-7035
KRACOEUS-6803:,These changes are for IACUC:,Code was modified to allow PI to only see the Withdraw Suspension action after a request for suspension. Code was modified to allow the admin role to see the additional actions of Assign to Reviewers, Assign to Agenda (once user selects a schedule date), and Modify Submission Request after a request for suspension is performed. [NOTE:] The Request for Suspension action sets the submission review type to Full. This submission review type value REQUIRES a schedule date before the Assign to Reviewers action will show.,All submission types values were coded to be available for the Modify Submission Request action after a user performs a Request for Suspension action.
KRACOEUS-7122: Making the template fields not required and fixing the validation patterns used for dates
KRACOEUS-6849
KRACOEUS-7120: more service refactoring for s2s
KRACOEUS-7120: moving s2s BOs into propdev
KRACOEUS-7122: Fixing the title
KRACOEUS-7126: Changing mime type to allow all characters.
KRACOEUS-7035
KRACOEUS-6969
KRACOEUS-7048:,Performed changes similar to those made for KRACOEUS-6801 for both IRB and IACUC due to required base classes needing to be modified.,For IRB:,It was determined that additional modifications were also required because the same sequence (SEQ_VALID_SUBM_REVW_TYPE_QUAL) was being used to load initial data via the data load scripts for two different IRB maintenance data tables (VALID_PROTO_SUB_REV_TYPE and VALID_PROTO_SUB_TYPE_QUAL) but the application data dictionary was configured to use a different sequence SEQ_PROTOCOL_ID) for the maintenance document data inserts on both of those tables.  SQLException?226?128?153s were resulting when attempting to create new data rows via the maintenance document because sequence SEQ_PROTOCOL_ID had a value lower than the maximum value of sequence SEQ_VALID_SUBM_REVW_TYPE_QUAL used for the initial data load.,To solve this issue, the following was done per Gayathri?226?128?153s request:,1. Two new sequences were created for both IRB tables.,2. These new sequences were set to start at 200 for now.,3. JIRA KRACOEUS-7128 was created and assigned to her to look at this issue further.,For IACUC:,IACUC did not exhibit the SQLException?226?128?153s because there was no initial data being loaded and the two IACUC maintenance data tables (VALID_IACUC_PROTO_SUB_REV_TYPE and IACUC_VALID_PROTO_SUB_TYP_QL) each have their own sequence (SEQ_VAL_IAC_PRO_SUB_REV_TYP_ID and SEQ_VALID_PRO_SUB_TYPE_QUAL_ID) defined in the application data dictionary.