Faculty have to go through the contract renewal process every year or every 2nd and 4th year depending on their job type. The process is slightly different than the Tenure and Promotion process.

JIRAs

Create new application type
- Insert type in the drop down
- Create sql script to add the new record to APPLICATION_TYPE
  - id=5 description='Contract Renewal'
- Run and fix and broken tests
- Hide exclusions tab
Workflow
- Create new workflow path based on this application type
  - DPC → DC → Applicant → Dean → Chancellor for application type 5
  - DPC → DC → Dean → TPRC → Chancellor for application types 1-4
- Do NOT auto submit this application type the 1st week of October like the tenure and promotion application types
  - there is no hard deadline
- 3rd step (Applicant Reviewing State 130)
  - Send out an email to the applicant and the department chair when the app transitions to State 130
  - The applicant shall have the ability to push the document to the Dean
  - Grant the applicant Viewer access to the shared drive at this state
  - Create a batch job to fire 5 days when it gets to this state which pushed the app to the Dean
  - Applicant needs to see the Reviews tab in order to view the assessments
If time permits or easy to do
- Hide exclusions tab
Change the shared drive name from "Tenure and Promotion Application xxxx" to "Contract Renewal Application xxxx"
Change the label in the email when the application is created/copied (put in parking lot)
Take off "Strengths and Weaknesses" option on the Recommendations tab at the DPC level
~~Exclude contract renewals from the auto submit job that fires on the first week of October for the Tenure and Promotion applications~~