EVSS PCIU Migration: Discovery around the EVSS integrations in Vets API

[jennb33]

Duplicate Ticket!

Issue Description

To prepare for the eventual sunsetting of EVSS, all calls to PCIU must eventually be removed from vets-api. During the course of discovery for Form526ez, it was discovered that calls to PCIU were being made in the FormProfile base-class related to the Pre-fill functionality- specifically to gather phone and email information. While Form526ez and many other forms intentionally use it in combination with their own derived Pre-fill classes, further digging through vets-api and in DataDog revealed that essentially every form in the system was calling out to PCIU. Either way, it became apparent that the scope of the problem was beyond just Form526ez.

The good news is that the base-class pre-fill is already calling out to VA Profile, which is widely considered the best one-stop source of all contact information within the VA. The specific reason we call out to PCIU here at all remains a mystery, although the best educated guess so far suggests that it may have to do with a potential lag between the time that the user enters/updates information and the time when it becomes available in VA Profile. In other words, if a user just updated their information and went straight to an application that uses Pre-fill, that information might not prefill in that application's form. This is just speculation, however, and there's a chance that if it WAS a problem when they added the PCIU calls 4-6 years ago, that latency might not be an issue anymore.

---

Tasks

• Discovery around EVSS integrations in Vets API

Acceptance Criteria

• TBD

---

How to configure this issue

• EVSS PCIU Migration: Remove calls to PCIU in global Pre-fill
• Product Support
• backend, devops
• request

[RachalCassity]

Duplicate ticket, can be closed.