Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verification | Trigger for In-Progress Email #97110

Open
8 tasks
steele-lm opened this issue Nov 13, 2024 · 0 comments
Open
8 tasks

Verification | Trigger for In-Progress Email #97110

steele-lm opened this issue Nov 13, 2024 · 0 comments
Labels
backend Dependency Verification New integration for updating diary entries dependents-benefits engineering Engineering topics

Comments

@steele-lm
Copy link
Contributor

Issue Description

If there is an existing failure email notification, confirm that it is sent through VA Notify. If yes, stop using existing email template and start using new failure email notification template created for all benefit forms.

If there is not an existing failure email notification, create a trigger that will send the VA Notify failure email template when a claim fails the backup submission pathway.

Resources


Tasks

  • If VA Notify is already leveraged, migrate failure notification to the new email template
    If a failure email is not currently sent:
  • Build notification code to call the VA Notify API
    • Notification should trigger an email when a submission fails the backup pathway (total failure)
    • The default email address should be the email the user entered into the form. If no email exists within the form, use their MyVA profile email.
  • Test notification by logging into staging with a test user, updating the profile ID to something that sends to you
  • Determine alerting and error handling if email fails to deliver

Acceptance Criteria

  • A notification trigger that sends an email to claimant when their submission fails
  • Logging and monitoring for failed sends
@steele-lm steele-lm added 686 Label for any work associated with Dependency Claims using VA Form 21-686c backend dependents-benefits engineering Engineering topics zero-silent-failures Work related to eliminating silent failures ZSF:UserExperience User experience changes on confirmation page/emails to clarify the status of the submission. labels Nov 13, 2024
@steele-lm steele-lm assigned sanjabaj2 and unassigned sanjabaj2 Nov 13, 2024
@steele-lm steele-lm changed the title Copy of 686 | Trigger for In-Progress Email Verification | Trigger for In-Progress Email Nov 13, 2024
@steele-lm steele-lm added Dependency Verification New integration for updating diary entries and removed 686 Label for any work associated with Dependency Claims using VA Form 21-686c zero-silent-failures Work related to eliminating silent failures ZSF:UserExperience User experience changes on confirmation page/emails to clarify the status of the submission. labels Nov 13, 2024
@steele-lm steele-lm added this to the Dependency Verification milestone Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Dependency Verification New integration for updating diary entries dependents-benefits engineering Engineering topics
Projects
None yet
Development

No branches or pull requests

2 participants