Description
User Story - Business Need
The database needs to establish a relationship between Template and SMS Senders.
Example scenario:
As a Service using VA Notify I want to send out text messages when something like a compensation payment will be going out. The data is the same regardless of the recipient's location. I do not want to have to track which Veteran is in which area of the world, as that can change at any time. I would like to send to those Veterans regardless, without having to be aware of where they are.
VA Notify will use a list of SMS Senders for a given Template to identify if a sender is available. In order to do that we need to add that structure to the database.
- Ticket is understood, and QA has been contacted (if the ticket has a QA label).
User Story(ies)
As a Service using VA Notify
I want to send to the Veteran without specifying a phone number to use for each request
So that I do not have to track extra data or do VA Profile lookups prior to calling VA Notify
Additional Info and Resources
We have multiple relationships in the code already.
This is a One to Many relationship in SQLAlchemy docs.
Acceptance Criteria
- Template and ServiceSmsSender tables have a relationship that allows multiple ServiceSmsSenders linked to a single Template.
- This work is added to the sprint review slide deck (key win bullet point and demo slide)
QA Considerations
Potential Dependencies
None.
Activity