Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USPS API for Mailing and Physical Address validation(Feb release) #1190

Open
rohanjay10 opened this issue Jan 16, 2025 · 4 comments
Open

USPS API for Mailing and Physical Address validation(Feb release) #1190

rohanjay10 opened this issue Jan 16, 2025 · 4 comments
Assignees
Labels
CCC Priority 1 Issues to be addressed in the current release

Comments

@rohanjay10
Copy link
Collaborator

  • USPS API would be used to validate mailing and physical address for User Profile
  • Once built out, this needs feedback from Ops prior to testing
  • Built into User Profile, PWA(user info), and SMDB

Look into partial entry of Physical Address fields:
If any one of Physical Address fields Line 1, City, State, and Zip are entered, then all those fields must be required otherwise error given. However as Physical Address is not required all the fields can be blank

@jhflorey
Copy link
Collaborator

@jhflorey jhflorey moved this from Backlog to Development in Connect Development and Support Jan 30, 2025
@sonyekere sonyekere added CCC Priority 1 Issues to be addressed in the current release and removed CCC Priority 2 Issues will be prioritized in the upcoming/next release labels Jan 31, 2025
@rohanjay10
Copy link
Collaborator Author

Hi @robertsamm @brotzmanmj, @jhflorey is currently working on the USPS API. Is there a date you have in mind for a demo of the API User Interface Experience? This is part of the February release, per the priority list

@rohanjay10
Copy link
Collaborator Author

2/7 Requirements call notes by @Davinkjohnson

  1. How to interpret API results (when/what messages to display when minor changes are found vs invalid addresses)

Suggested Address field changes:

• Accepting/Declining - Use “suggested change” modal
@depietrodeanna to provide language

Image

English/Spanish translations for current messages
• "Invalid Zip code"
• "Address not found"
• Other (@rohanjay10 to add)
@depietrodeanna to confirm language for these

How/Where error messages would be shown. Address validated after UP submission
• Have the errors display “in line” as a field is filled in check to see whether all boxes are populated if so then call API
• Find a way to force API error results to log in DataDog (check with Tony/Warren for this)
• Interim modal will check if there are any errors for the addresses (and email address) and display those.
• Ideally have a message saying “reach out to NORC if errors continue” – @depietrodeanna to provide

  1. How to interpret and respond to PO boxes
    @jhflorey will do a little more testing to see if API handles
    • No change in the logic for this (hopefully just better flagging whether this IS a PO Box)

  2. Mailing vs Physical addresses
    • User Profile - Keep as-is (no changes to display/logic)
    • MyProfiles – no changes for how data are displayed, required vs optional, edited, etc.
    • SMDB - No changes required

  3. Edits for MyProfile - Implement API changes (have the API run when a participant clicks “save/submit”)

  4. Edits for SMDB – No changes required

  5. How to manage Partial addresses• Partial address logic is working as expected – no changes needed
    • Including non required Physical Address fields

@depietrodeanna Error messages to return:

• "Address not found"
• "Invalid Zip Code"
• "Invalid City"
• "Invalid State"
• "Invalid"
Example wording from mockup for suggested address:
"You originally entered xyz, the suggested address is abc, do you want to use the suggested address or keep the original address?"
• Buttons: "keep original address" "use suggested address"

@depietrodeanna
Copy link
Collaborator

depietrodeanna commented Feb 7, 2025

@rohanjay10 @jhflorey For the errors found during validation within UP submission, add a modal with language stating, “Please fix the errors in the information you entered before continuing. If you are having problems fixing these errors and can't submit your profile, please reach out to the Connect Support Center (Dev, either hyperlink CSC or add “at MyConnect.cancer.gov/support”) for help.”

For address validation, add this error message:
"We can’t verify your address but found a close match. Please confirm the correct address or enter a different address." (Dev- if they want to go back and re-enter a diff address, is there a way to go back with a button that we should reference in the message, or will it be clear that they can go back and make a new entry? Kind of like the "try again" hyperlinked in the example modal from the presentation)

Display both original and suggested addresses alongside these buttons: "Keep address I entered" or "Use suggested address"

tagging @robertsamm and @brotzmanmj to review messaging- let me know if you have any concerns about the above.

I will ask NORC to translate the above messages as well as these phrases:
"Address not found"
"Invalid Zip Code"
"Invalid City"
"Invalid State"
"Invalid"

@rohanjay10 if there are any others please add to this list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CCC Priority 1 Issues to be addressed in the current release
Projects
Development

No branches or pull requests

6 participants