Investigate vet experience at submit (IPF?)

[SamStuckey]

We need to answer two questions

1. After a vet hits submit, what do they see if they return to the page / their in progress forms area, whatever is available? Underlying question, are we still showing them an open, unsubmited form while our submission jobs are running?
2. Is this linked to the presence of an InProgressForm record? If so, how does the presence of this record affect the UX?

[mengA6]

Thanks! Commenting to get updates on this. cc @evelynhilbrichdavis

[evelynhilbrichdavis]

First, the high level understanding of the relationship between submission and deleting the IPF/ITF.

A record of their submission is created every time a Veteran hits submit, even if it fails. The jobs to clean up the IPF/ITF after submission happen after the Claim ID is established and all of the perform-ancillary-jobs (see visual for included jobs for uploads, 4142,0781,8940, etc) run. If there is any failure before these jobs are triggered, it will never reach the cleanup job. As a result, the IPF remains available and open to Veterans for resubmission until that cleanup is complete.

Breaking down what happens based on different user experiences

1. Veteran receives a "We're sorry" submission failure error with no claim ID

• They can still access their IPF. When they do open it, they are sent to the beginning of the 526, fully prefilled with the claim they just submitted.
• As they click through to resubmit, they can make changes so the resubmission is not an exact duplicate (contributing to the challenge of identifying "duplicates" when slight changes are made
• They will be able to continuously open the IPF and resubmit it until a claim ID is generated and perform-ancillary-jobs runs successfully.

2. Veteran is told their claim was successfully submitted with claim ID

• It is likely that all Veterans have a window where they can access and resubmit a 526 because even after the claim ID is established, perform-ancillary-jobs still needs to run all the way through before it gets to cleanup.

3. Veterans are told submission is "taking longer" without claim ID

• We have not been able to recreate this scenario, but because the cleanup doesn't run until after the claim ID is generated, we can assume that Veterans still have access to their IPF for a longer period of time until that claim ID is created and perform-ancillary-jobs runs all the way through to cleanup the IPF and ITF.

4. Veterans are waiting on the loading screen after hitting submit, but decide to go back and try to resubmit

• Veterans can access the In Progress Form by hitting the back button to return to the application.
• The form is directed back to the ITF and then reenters the flow wherever the user last started, but the form is completely filled in
• At the review and submit page, the green button that normally reads "Submit Application" is gray and reads "Submitted" next to a checkmark.
• However, if the Veteran leaves the form, they can open their IPF in MyVA and submit it again that way.

[evelynhilbrichdavis]

Veteran hits back during submit loading screen Veteran submission fails, returns to In Progress Form

[lisacapaccioli]

@SamStuckey Is this ticket still needed or did you get your answers?