Summary
How an applicant deletes an in-progress application: the confirmation modal, setting Internal Status to Marked for Delete, the follow-up Task and the Delete Job batch. Also lists the Apex classes, components, modal components, controllers and batch behind it.
Body
Overview
Applicant Experience
- Only appears for In Progress applications
- On click launches Modal asking applicant to confirm their decision to delete
- Upon confirmation, sets application's Internal Status to "Marked for Delete" and refreshed application dashboard, dropping application out of view and replacing with any other eligible apps from same program group
Task
- In addition to updating Internal Status, a task is also created
- Attaches to applicant's Lead record and is assigned to the Owner of the application's Program record
- Includes the App Number in the Task description and sets a Due Date of 14 days out from creation
- Task Type is "Deleted App"
Delete Job
- Runs nightly at 11pm
- Finds and deletes all applications with Internal Status of 'Marked for Delete'
- Also finds and deletes related Affiliation and Certifications, Recommenders, and Test Score records
- Deleted records stay in Recycling Bin for 15 days and then are permanently deleted.
Classes
Components
ApplyApplicationItem
- Builds list of Actions to display to applicant
- When "Delete Application" button is clicked, displays the MarkForDelete modal components.
Modal Components
ApplyApplicationMarkForDeleteBody
ApplyApplicationMarkForDeleteHeader
ApplyApplicationMarkForDeleteFooter
- When "Yes" is clicked, calls ApplyApplicationDeleteModalController
Controllers
ApplyApplicationDeleteModalController
- Calls ApplicantUtils.markDeleteApplication
ApplicantUtils
- Adds 'Delete Application' button to list of actions if application is editable
- markDeleteApplication method marks the app as "Marked for Delete" and creates task for Admissions
Batch
AdmissionsAppDeleteBatch
AdmissionsAppDeleteBatchScheduler