As a Veteran I want to receive an email when my application for disability compensation is submitted so that I know VA is working on my claim. Since Veterans are sufficiently informed of their submission status by the existing Received email, this feature only impacts Veterans who have an asynchronous submission, i.e. the Backup path.
Per VA's Design System Pattern, if there’s no lag time between when someone submits a form and when we receive it—the form was received in the system of record in time for us to show a success message on the confirmation page—then we consider it a synchronous form. In this case, you need to implement only one email notification:
Received: The notification when we’ve received a submitted form in the system of record. This means the form is ready for processing. Only send this status notification when we have confirmation that the request has reached the system of record.
Asynchronous
If there’s a lag time between when someone submits the form and when VA receives it in the system of record, you must implement these 3 email notifications:
Submission in progress: The notification we send immediately after someone selects the Submit button on an online form. This means that the form submission has successfully started, but it has not yet reached the system of record. During this time, data submitted by the person may travel through several systems.
Received: The notification we send when we’ve received a submitted form in the system of record. This means the form is ready for processing. Only send this status notification when we have confirmation that the request has reached the system of record.
Action needed: The error notification we send if a form submission fails to reach the system of record. This means we need the person to resubmit or take another action before we can process their form. This notification must include instructions for the person to recover from the error. There are different templates available based on the remediation steps specific to the form.
Acceptance Criteria
[ ] When a Veteran's 526 claim application uses the backup path the Veteran is sent a "submitted" email
How to configure this issue
[ ] Attached to a Milestone (when will this be completed?)
[ ] Attached to an Epic (what body of work is this a part of?)
[ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
[ ] Labeled with Type (bug, request, discovery, documentation, etc.)
Removed ZSF tag as it was incorrectly labeled. This work does not cover a gap of the Veteran UX where there is a failure and VA hasn't notified them of such.
Issue Description
As a Veteran I want to receive an email when my application for disability compensation is submitted so that I know VA is working on my claim. Since Veterans are sufficiently informed of their submission status by the existing Received email, this feature only impacts Veterans who have an asynchronous submission, i.e. the Backup path.
Additional Information
This work follows VA's Stay informed of their form submission status pattern, and follows the guidance below.
Synchronous
Per VA's Design System Pattern, if there’s no lag time between when someone submits a form and when we receive it—the form was received in the system of record in time for us to show a success message on the confirmation page—then we consider it a synchronous form. In this case, you need to implement only one email notification:
Received: The notification when we’ve received a submitted form in the system of record. This means the form is ready for processing. Only send this status notification when we have confirmation that the request has reached the system of record.
Asynchronous
If there’s a lag time between when someone submits the form and when VA receives it in the system of record, you must implement these 3 email notifications:
Submission in progress: The notification we send immediately after someone selects the Submit button on an online form. This means that the form submission has successfully started, but it has not yet reached the system of record. During this time, data submitted by the person may travel through several systems.
Received: The notification we send when we’ve received a submitted form in the system of record. This means the form is ready for processing. Only send this status notification when we have confirmation that the request has reached the system of record.
Action needed: The error notification we send if a form submission fails to reach the system of record. This means we need the person to resubmit or take another action before we can process their form. This notification must include instructions for the person to recover from the error. There are different templates available based on the remediation steps specific to the form.
Acceptance Criteria
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,Console-Services
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)