On successful bulk processing, send application status update emails to applicants whose records had notify-worthy changes, using the same content and templates as today’s single-application email update flow.
After the bulk process database commit, for each updated application:
- Compare before/after using buildApplicationStatusChanges
- If changes are non-empty, send via existing EmailService.applicationUpdateEmail
AC
- Status change triggers email with unchanged template content
- Decline reason / waitlist number changes trigger appropriate email sections
- Applications with no notify-worthy changes do not receive email
- Failed bulk upload sends no emails
On successful bulk processing, send application status update emails to applicants whose records had notify-worthy changes, using the same content and templates as today’s single-application email update flow.
After the bulk process database commit, for each updated application:
AC