MAIN-B-20941-ssw-duplicate-state-zip

[MInthavongsay]

B-20941

INT PR

Summary

MAIN

This PR fixes a small issue in the SSW PDF for AOA/Payment download where Authorized Origin field was displaying duplicate state and zip.

Verification Steps for the Author

These are to be checked by the author.

• Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
• Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers

These are to be checked by a reviewer.

• Has the branch been pulled in and checked out?
• Have the BL acceptance criteria been met for this change?
• Was the CircleCI build successful?
• Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

• Instructions for starting storybook
• Instructions for starting the MilMove application
• Instructions for running tests

How to test

1. Login as customer to create and submit move with PPM. Make sure to click YES for "Would you like to request an advance on your incentive?"
2. Login as a SC and fill in all required fields and click submit move details. Page will refresh containing AOA download link. Download and verify Authorized Origin field does not contain duplicate state/zip.
3. Login as customer and click upload PPM Documents and complete/submit process of providing documents for review.
4. Login as SC and review documents. Approve/Reject and confirm/submit. Page will refresh containing Payment Download link. Download and verify Authorized Origin field does not contain duplicate state/zip.
5. Login as customer and click Payment Download and verify Authorized Origin field does not contain duplicate state/zip.

Frontend

• There are no aXe warnings for UI.
• This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
• There are no new console errors in the browser devtools.
• There are no new console errors in the test output.
• If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
• This change meets the standards for Section 508 compliance.

Backend

• Code follows the guidelines for Logging.
• The requirements listed in Querying the Database Safely have been satisfied.

[antgmann]

Matches INT

[r-mettler]

good