5.) Please explain what problem you are trying to solve.
VEText currently handles all mobile registrations, we'd like to migrate registration of devices to VA Notify.
As a first step, we'd like to also receive a registration request in addition to VEText. And we'd like to know what the appropriate response to mobile team's https request should be.
6.) Please explain how this change would work.
VA Mobile team sends Va Notify requests in parallel with VEText, so there are no disruptions.
VA Notify will respond with a mock value of their choosing.
This would probably need to be feature-flagged until we all are ready to migrate.
Future work will involve a proper response and transitioning to using VA Notify's response (and dropping VEText).
7.) Features Impacted
Sending push notifications
8.) Please include all relevant documentation links for this change request.
9.) Does your team have all the necessary materials (documents, designs, processes, analytics, APIs, etc) in place for Mobile to make these changes right now?
No
10.) Has this change been discussed with VAHB POs (Ryan or Don)?
Don - yes
11.) Has this change been agreed upon by all impacted VA Stakeholders?
Yes
12.) What is your ideal due date for this change request?
1.) Requestor's Name
Ksenia Belikova / Kyle MacMillan
2.) Requestor's Email
ksenia.belikova@va.gov kyle.macmillan@va.gov
3.) VA Team
VA Notify
4.) What is the name of the project or change?
Mobile Registration through Va Notify
5.) Please explain what problem you are trying to solve.
VEText currently handles all mobile registrations, we'd like to migrate registration of devices to VA Notify. As a first step, we'd like to also receive a registration request in addition to VEText. And we'd like to know what the appropriate response to mobile team's https request should be.
6.) Please explain how this change would work.
7.) Features Impacted
Sending push notifications
8.) Please include all relevant documentation links for this change request.
Push Notifications Brief Document
Proposed Diagrams
9.) Does your team have all the necessary materials (documents, designs, processes, analytics, APIs, etc) in place for Mobile to make these changes right now?
No
10.) Has this change been discussed with VAHB POs (Ryan or Don)?
Don - yes
11.) Has this change been agreed upon by all impacted VA Stakeholders?
Yes
12.) What is your ideal due date for this change request?
End of Q4 2024