JIRA reference: FT-501
High Level Requirements
Who: Coordinators and administrators
What: Applicant wishes to rescind their application
- 2 use cases
- Faculty separating
- remove it completely from the system
- if in flight; lock it down and stamp it with Withdrawn State
- applicant should get their materials back so that's accomplished with the shard drive copy
- lock it down and clone the application
- set to in progress so that the coordinator/admin can change the year and app type
- Faculty separating
- year 5, going for tenure and past the CR deadline, reapply online
- union has argued with Bev about TP and CR looking the same
Buttons:
- shows up for coordinators in the sub-banner
- shows up for any status except In Progress (101), Submitted (102), Under Appeal (118) and Final (115)
- generally an applicant withdraws after they get a negative recommendation from the TPRC
Notifications:
- functionals need to flesh out
Steps:
- Set application State to "Withdrawn" (this State needs to be created)
- Log the action
- id = 25
- action_code = application.withdraw
- action_description = Application withdrawn
- Send out notifications
- Google shared drive permissions
- remove everyone except for uhtnp, chancellor and coordinators
still contemplating this requirement
- For a withdrawn application, the applicant cannot see the DPC and DC assessments if the application is withdrawn prior to the Dean submitting their assessment; the applicant can see the assessments otherwise.
- get clarification from functionals as to why this requirement matters; I avoid exception programming
Questions
- How often does separation happen?
- if it doesn't happen often or a handful a year, perhaps it's best to leave it as an admin function to delete the application