PCIU Replacement Step 5b: VAProfile Contact Information V2 Testing (VA Notify Team testing)

[rmtolmach]

For the PCIU migration, the Platform Product Team changed the data source for ContactInformation to call VA Profile instead of PCIU.

Tasks

• Turn on flipper remove_pciu IN STAGING
• Test any VA Notify code related to Contact Information.
• If testing is successful, comment and close this issue.
• If issues are found (or if there are questions) reach out in #platform-product-team #pciu-migration-testing

[AshleyGuerrant]

Blocked pending this department-of-veterans-affairs/vets-api#18729 being merged.

This work essentially serves as a "flood gate" PR where after it is merged, we will be pointing completely to VA Profile Contact Information instead of PCIU.

[nathanbwright]

@rmtolmach @AshleyGuerrant - We don't use EVSS in the va_notify module. We do pull some data for our in progress reminders but we use the MPI::Service for that - that is not related to this in any way is it?

[RachalCassity]

@nathanbwright This does not involve the MPI::Service.

[AshleyGuerrant]

Ticket handed off on 12/17 in this dedicated testing channel in Slack.

[RachalCassity]

@nathanbwright At the moment, the in-progress forms are using the MPI::Service, mpi_profile_response cache, for form pre-fills. Every 24 hours, the MPI::Service will request data from the Contact Information service, va_profile_v2_contact_info_response cache. This means the MPI::Service only refreshes a user's contact info once every 24 hours. If a user updates email, address, or phone number, the pre-fill data may not be accurate. The Contact Information Service, va_profile_v2_contact_info_response cache, is re-initialized every time a user logs in or when they modify contact info.

FYI: @LindseySaari @AshleyGuerrant

[AshleyGuerrant]

Hi @nathanbwright - are there any updates on the testing? Please let us know if you have any additional questions, we're happy to help.

cc @RachalCassity @LindseySaari

[nathanbwright]

@AshleyGuerrant - Re-pulling the contact info before attempting to send an email would be a possibility - but I do not think it would be worth the additional complexity given that these emails are just to remind users that they have an unfinished form. Can we simply document this as known behavior and close the ticket?

[AshleyGuerrant]

@nathanbwright - thanks for the update.
@RachalCassity & @LindseySaari - can you please review the question above?

[RachalCassity]

@nathanbwright Yes, we can close it. I was just informing your team that the email in MPI::Service is not always up to date. If a user updates their email then opens a form, the form will not contain the updated email.

[kbelikova-oddball]

Closing the ticket