EVSS Service Modernization

[MekoHong]

Project Status: IN PROGRESS

• Mobile team confirms weekly with LH team to determine what next we will implement or "turn on".
  See Items listed under "Icebox": (Pending to be flipped)

---

Items Still Pending on Mobile Flip to Prod:

1. Flip Traffic to LH Letters. (OPEN)

(Web is still in test mode, Mobile awaiting confirmation to flip)

8/23/24 -LH still making Updates in the current sprint. After this will be the new baseline and should be good to migrate after this sprint for WEB

• Updates are expected to be different from EVSS functionality

9/6/24- LH expecting to deploy final solution no later than Tuesday.

2. Flip Traffic to LH Rated Disability (Testing CLOSED- In Prod, 100% on 9/11/24 for mobile

(Mobile Discussed with Web Last week, Plan is to turn on or "flip" this week 8/23/24 (estimated) after testing.- Ticket 7927)

3. Flip Traffic to LH Request Decision (5103 waiver) (Closed, In prod 100% for mobile)

-9/6/24: VA.gov completing a few tests, plans to merge early next week and test in staging. If working as expected, will begin rolling out in prod.
-10/7/24-Claim Status Tool team has completed their rollout for 5103 (Request Decision).Mobile team will analyze if we can proceed to test and turn on this function
-10/29/24- Roll out still in progress. Currently at 25% for Request Decision.

4. Flip Traffic to LH Documents (OPEN)

9/6/24: LH deployed updates to validation endpoints. VA.gov plans to start implementing next week.

Latest Update from Web Team-9/23/24 Meeting:

• LH potentially rolling back out next sprint. LH completed new validation endpoints with optional token updates. Validation token pieces still being fully worked out. Rollouts will be planned per document type label sheet (Ex: Cover sheet) (edited)

Monthly Update for Stakeholders

Date	Project Health	Progress & Key Accomplishments	Issues/Risks/Blockers
5-6-24	In Progress.	Continuing to check with LH Teams on Progress.	No Blockers
5-21-24	In Progress	Continuing to check with LH Teams on Progress.	No Blockers
6-6-24	In Progress/At Risk	No New Movement, continuing to check in with LH Team in order to Flip Items on Mobile Backlog	No Blockers on Mobile side. Note: At risk based on EVSS Timeline of July Turnover
6-17-24	In Progress/At Risk	LH team (Jerek shoemaker) is currently testing Letters in Web. Letters is slated up next for Mobile to flip in production	Note: At risk based on EVSS Timeline of July Turnover
6-26-24	In Progress/At Risk	Still awaiting the "go" from LH team for Letters	Note: At risk based on EVSS Timeline of July Turnover
7-8-24	In Progress/At Risk	Still awaiting the "go" from LH team for Letters	Note: At risk based on EVSS Timeline of July Turnover
8-6-24	In Progress/At Risk	Web team still testing and mobile team checking in for confirmation to move forward	Note: At risk based on EVSS Timeline of July Turnover
8-19-24	In Progress/At Risk	Plan is turn on Disability Rating for mobile this week per ENG discussion with Web team. A final check/testings will be done this week (8/24 estimated) in order for mobile to turn it on in prod and and monitor a* TICKET 7927 Note: Original Testing in Feb 2024 showed extra records for Disability Rating and that should now be fixed.	Note: At risk based on EVSS Timeline of July Turnover
9-3-24	In Progress/At Risk	Closed and Tested Ticket 7927. Next Lighthouse Meeting Scheduled for 9-6-24	At risk per original LH migration date
9-16-24	In Progress/At Risk	Disability Rating in Prod for Mobile. Updates from 9/6 meeting noted in comments Next Lighthouse Meeting Scheduled for 9-20-24
10-07-24	In Progress	Claim Status Tool team has completed their rollout for 5103 (Request Decision).Mobile team will analyze if we can proceed to test and turn on this function.	Ticket for Testing
10-29-24	In Progress	Roll out for Request Decision COMPLETED via ticket #6019. In prod at 100% Below	No Blockers
11-12-24	In Progress	Awaiting Next Steps from LH team for Letters	No Blockers

---

See Product Brief: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/va-mobile-app/features/evss-migration/evss-migration-product-brief.md

General testing notes:

• Each implementation ticket has the vets-api/BE PR linked, but it shows up randomly in the timeline (may have to expand some of the "N older events" links) rather than the usual spots, because it's in a different repo than the tickets
• Each migration ticket will have a per-user, BE feature flag. To test, you will need to reach out to the BE Eng who worked the ticket to let them know which users you'd like to flip to the Lighthouse services. As a courtesy, also let the QA folks know which users are flipped (in case they see something weird/need to test in that area as well)
• Want to be able to flip feature flags yourself? The page to flip it is here: https://staging-api.va.gov/flipper/features but you have to create a personal id.me on staging (with your work email so you'd be logging in to id.me through the google account login intergration) account to be logged in that is whitelisted to be allowed. BE Eng can add your email to the allowlist if you want to make the account. If you do want to make an account, just be sure not to use any of your real information, it'll ask for ssn but you can just put any numbers.
• These migrations should work with any mobile client, and will not require any FE changes. Sometimes we will want to make FE changes (like Remove VA Representative Conditional Logic from Claim Detail #5707, where a field was removed from the Lighthouse service), but those will be ticketed separately and - critically - the BE services in Lighthouse should continue to work with the old mobile clients regardless.
• The migrations themselves shouldn't involve any changes in error codes/handling, so a basic case of mocking an error state & confirming the FE is still OK is fine. If you run into an issue with that, it's actually probably a FE issue (we're not handling errors well in that screen/API) rather than a BE/migration issue.
• Maintenance windows also need to be migrated, but that's happening on a different ticket (Update Maintenance Windows #5715) than the implementation tickets
• BE Engineers are responsible for adding certain info to each of the implementation tickets: the URLs that are being migrated for each implementation ticket, and notes on the fields that needed the most work to get correctly mapped (so we can focus our attention to the risk of each migration accordingly). If you don't see those notes on your ticket when you go to start testing, ask the BE Eng to add them
• Also - since the core testing work here is "look at the EVSS version of the data, then the migrated/Lighthouse version for the same user", it's helpful to know whether the staging va.gov website is using EVSS or Lighthouse. That is going to vary by migration, and when you're testing, so that's a good question to ask your BE counterpart before you jump in.

[bischoffa]

Per PO request during 7/11 SoS the release estimate has been updated to match the SoS doc - it could only be added in the 100% release as there is no other option. Date pulled from Q3 planning. Date to be updated if it moves / changes.

[timwright12]

@kellylein Assigning @jperk51 as tech lead to this epic, but feel free to reassign as appropriate

[StacyB2023]

Latest from 8/23/24 LH meeting: (Next meeting 9/6/24)

Letters:

Letters: LH still making Updates in the current sprint. After this will be the new baseline and should be good to migrate after this sprint for WEB

Updates are expected to be different from EVSS functionality

Documents: LH potentially rolling back out next sprint. LH completed new validation endpoints with optional token updates. Validation token pieces still being fully worked out. Rollouts will be planned per document type label sheet (Ex: Cover sheet) (edited)

[jperk51]

Aside from any updates be need to make because of recent changes lighthouse has made to their responses we should be prepared to flip out switches for the remaining features whenever we want. Since LH has made changes to a few of these features we will need to make tickets to make sure our integration is good still then probably have QA retest each feature before we sign off on the LH implementations being correct. Previously we found bugs in their logic for most of initial attemtps.

[StacyB2023]

Updates from today's meeting with LH: 9/6/24

• Letters Update - 9/6: LH expecting to deploy final solution no later than Tuesday.

• Documents Update - 9/6: LH deployed updates to validation endpoints. VA.gov plans to start implementing next week.

• 5103 Update (request decision) - 9/6: VA.gov completing a few tests, plans to merge early next week and test in staging. If working as expected, will begin rolling out in prod.

[StacyB2023]

Note: Epic was accidentally close. Now reopened. Remains in progress

[StacyB2023]

9/20/24 LH/EVSS Meeting Update:

• Rated Disability: LH Team is aware that mobile has fully tested this and released at 100%. They are looking to "turn on" for Web soon. Date not stated.

• Letters- Jerek is still testing. LH pushed a fix recently.

• Documents- VA.gov will need to implement all of the polling logic before rolling the migration to LH. Octo does not want to use the benefits document API until polling is in place (related to the silent failures effort)

All other items remain the same.

[StacyB2023]

Rated Disability for Mobile- 100% for Mobile on 9/11/24

Supporting thread: https://dsva.slack.com/archives/C02CQP3RFFX/p1726078755673619?thread_ts=1725464813.453849&cid=C02CQP3RFFX

[StacyB2023]

@jperk51 : Will check in monday, but anything new here in the past 2 weeks fom Jerek? I will check in with the LH team on Monday.

[StacyB2023]

Note: Claim Status Tool team has completed their rollout for 5103 (Request Decision).Mobile Team currently testing request decision via ticket #9809 and will plan for % release

[StacyB2023]

Roll out for Request Decision on mobile is still in progress via ticket #6019

[StacyB2023]

Update: Request Decision in mobile at 100%

[StacyB2023]

Reopened. Issue closed by accident