You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Veteran I want status information on the confirmation page that is consistent with the status of my application so that I feel that understanding submission status is trivial. I expect the confirmation message to truthfully communicate the status of my application.
This story covers these possible error scenarios at the time of submission.
200 no claim id
401 unauthorized
402 bad request
404 no record found
500 ?
For reference the Figma design file for this feature is here.
Tasks
[ ]
Acceptance Criteria
The yellow warning alert on the Confirmation page is removed and is no longer possible to show to the Veteran
A green success alert is shown on the Confirmation for any success, retryable, and non-retryable http responses
All scenarios are tested and known to be working
Additional Information
Open questions
Do we still need a generic red error alert on the Confirmation page? I know that we expect the vast majority, if not all, form errors to be caught on Review & Submit, but are there any remaining edge cases where we may need a red generic error? See #94479
How might we break this up to be smaller? Should we move the 200 no claim id scenario to #94421
The text was updated successfully, but these errors were encountered:
pacerwow
changed the title
Implement design into Confirmation page
show the "In Progress" alert for success, and retryable, and non-retryable https responses
Oct 7, 2024
pacerwow
changed the title
show the "In Progress" alert for success, and retryable, and non-retryable https responses
show the "Your submission is in Progress" alert for success, and retryable, and non-retryable https responses
Oct 10, 2024
pacerwow
changed the title
show the "Your submission is in Progress" alert for success, and retryable, and non-retryable https responses
show the "Your submission is in Progress" alert for retryable, and non-retryable https responses
Oct 17, 2024
From what i understand, the no claim id scenario would come after the 30 seconds wait, so I think we should keep that separate from the success scenario with claim id.
Issue Description
As a Veteran I want status information on the confirmation page that is consistent with the status of my application so that I feel that understanding submission status is trivial. I expect the confirmation message to truthfully communicate the status of my application.
This story covers these possible error scenarios at the time of submission.
200 no claim id
401 unauthorized
402 bad request
404 no record found
500 ?
For reference the Figma design file for this feature is here.
Tasks
Acceptance Criteria
Additional Information
Open questions
Do we still need a generic red error alert on the Confirmation page? I know that we expect the vast majority, if not all, form errors to be caught on Review & Submit, but are there any remaining edge cases where we may need a red generic error? See #94479
How might we break this up to be smaller? Should we move the 200 no claim id scenario to #94421
The text was updated successfully, but these errors were encountered: