[CST] Add design for second type of 5103 Notice request so that we can fully remove "Ask for your claim decision" banner

skylerschain commented 1 month ago

Value Proposition

As a veteran with a 5103 standard notice, I want to be able to find the place in CST where I can submit a waiver, so that I can hopefully get my claim decided faster if I have no evidence to submit.

Background Context

As @jerekshoe pointed out here, the 5103 Notice Response request is treated differently in CST than the Automated 5103 Notice Response request.

The Custom 5103 shows up as Automated 5103 Notice Response and our new design will apply to this case. But Standard 5103 requests don't show up in CST (until the request is closed).

Once a user has gone to the 'Ask VA to Decide' page and clicked the submit button; this will mark evidenceWaiverSubmitted5103 to true. Then someone from the VA will go to VBMS and closes the tracked item. The request will be considered closed and it will show up as a tracked item with a closedDate and a status of NO_LONGER_REQUIRED in the CST.

The Veteran will still get a letter for this request though, so it makes sense to have some alert for this in CST and some way for them to satisfy the tracked item.

Current idea is to use the same FE logic that shows the "Ask for you claim decision" banner on the Files tab to instead show an alert that directs the user to the 5103 detail page.

Open questions

Q: For @jerekshoe: Can we connect this backend logic to a frontend that is the same as the new 5103 design? It wouldn't technically be a 1P request from BGS but we could make it look like one in our frontend (until we can get BGS to change this for us).

@skylerschain the 5103 Notice Response are not actual tracked items when they show up under the Ask for your claim decision so changing this to show up as a primary alert would require us to change a bunch of logic. I would be easier and much less work if we just left the experience as it currently is and we show the blue banner on the files tab and then change what page the user is directed to when they click the 'View Details' button
We can still reach out to BGS and make a request for them to make the 5103 Notice Response request a tracked item that shows up in the claim and if/once they do this we can then show it as a P1 request and remove the banner from the files page. Q: Assuming we can do the above, what are the other implications of the fact that Standard 5103 tracked items are not treated as requests by BGS? (e.g. It will not show up in Recent Activity until it's closed)
Answered above, only other thing to note is this request wont show up in recent activity until it has been closed.
Also important to note that the tracked items in recent activity are not showing open and close dates currently, they only show the most recent date based on the tracked items status. If we want this to change we would need to change logic on our side which would be in a new ticket @skylerschain

Design

FIGMA

Design Tasks

[x] Need to figure out what the design should be for Standard 5103 requests in CST.
[x] Create a design that allows the Veteran to close the "5103 Notice Response" (i.e. Standard 5103) tracked item via CST, similar to what we designed for "Automated 5103 Notice Response" (i.e. Custom 5103)_

Currently Standard 5103s show the "Ask for your claim decision" banner":

Ideally we would show a message similar to what we will show for Custom 5103:

Enablement team (if needed)

@jstrothman

Engineering Tasks

[ ] Once Design is created and discussed/approved we will implement
[ ] Put logic behind the 5103 feature flag cst_5103_update_enabled

(Notes from XFN Sync 7/19) Logic and other engineering tasks to hide Standard 5103 alert (AKA blue banner AKA "Ask for your claim decision") when a Custom 5103 ("Automated 5103 Notice Response") is present: Update status tab:

[ ] Show a primary alert under the 'What you need to do" section for the 'Standard 5103'
- [ ] Create new component for alert
- [ ] Alert 'Details' link takes user to new URL - /track-claims/your-claims/{claimId}/5103-evidence-notice
- [ ] Logic to show this is alert when claim.attributes.claimPhaseDates.latestPhaseType === GATHERING_OF_EVIDENCE and claim.attributes.evidenceWaiverSubmitted5103 = false
[ ] Add logic that states if user has a tracked item that is ‘automated 5103’ that we don’t show the new component and only show the alert for the ‘automated 5103’
[ ] Put behind feature flag cst_5103_update_enabled

Update files tab:

[ ] Hide the Ask for your claim decision banner
[ ] Show a primary alert between claim files header and additional evidence section for the 'Standard 5103'
- [ ] Create new component for alert
- [ ] Alert 'Details' link takes user to new URL - /track-claims/your-claims/{claimId}/5103-evidence-notice
- [ ] Logic to show this is alert when claim.attributes.claimPhaseDates.latestPhaseType === GATHERING_OF_EVIDENCE and claim.attributes.evidenceWaiverSubmitted5103 = false
[ ] Add logic that states if user has a tracked item that is ‘automated 5103’ that we don’t show the new component and only show the alert for the ‘automated 5103’
[ ] Put behind feature flag cst_5103_update_enabled

Create a new component for the Standard 5103 Notice:

[ ] Create new component for submission page
[ ] Hide the Ask for your claim decision page
[ ] Put behind feature flag cst_5103_update_enabled

Create a new URL:

[ ] Create new URL /track-claims/your-claims/{claimId}/5103-evidence-notice that hosts the new 'Standard 5103 page'
[ ] Hide current URL (ask-va-to-decide)
[ ] Update routes.js for new components and URL
[ ] Put behind feature flag cst_5103_update_enabled

Add Tests:

[ ] Cypress tests
[ ] Unit tests

Out of scope

Add here

Definition of Done

[ ] Meets acceptance criteria
[ ] Passed E2E testing (90% coverage)
[ ] Passed unit testing (90% coverage)
[ ] Passed integration testing (if applicable)
[ ] Code reviewed (internal)
[ ] Submitted to staging
[ ] Team approved production verification process
[ ] Design performs design QA and verifies the implementation matches the design spec
[ ] Accessibility specialist performs accessibility review (in code or design)
[ ] Engineering identifies staging users required to test and shares account and credentials with design and product
[ ] Product performs functional QA and verifies acceptance criteria was met

Acceptance Criteria

[ ] New logic for Standard 5103 is behind the 5103 feature flag cst_5103_update_enabled
[ ] When cst_5103_update_enabled = true
- [ ] Standard 5103 notices will appear on the Status Tab under the 'What you need to do" section as a primary alert
- [ ] The 'Details' link takes users to the url /track-claims/your-claims/{claimId}/5103-evidence-notice
- [ ] If user has a tracked item that is ‘Automated 5103’ then the new Standard 5103 Notice alert doesn't show and only the ‘automated 5103’ alert shows
- [ ] Standard 5103 notices will appear on the Files Tab between claim files header and additional evidence section as a primary alert
- [ ] Ask your claims decision banner is hidden
- [ ] Ask for your claim decision page is hidden
- [ ] Ask for your claim decision url is hidden

jacobworrell commented 1 month ago

We don't know exactly where to get a screenshot of the present state, can't duplicate in staging easily.

skylerschain commented 1 month ago

Added design spec to "Design" section above. @pmclaren19 this should be ready to work when you're back. Let me know if you want me to add anything else to the spec.