Int b 21507 pod poe too validation

[msaki-caci]

B-21507

Summary

Bulk of the work was completed and merged here.

This PR is just to make it so the Port Location has its own box SEPARATE from the Authorized Addresses box.

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

NOTE: We are following the same steps for 1-5 from B-21505 to setup the location for the POE/POD.

1. Create an INTL UB shipment as a customer (CONUS -> AK or AK -> CONUS)

2. Manually create the mto_service_items table for the shipment: INSERT INTO mto_service_items ( id, mto_shipment_id, move_id, re_service_id, status, created_at, updated_at, approved_at ) VALUES ( uuid_generate_v4(), '8eeba537-bb40-4f58-a534-74ea9ff64590', '813b7a43-2e3f-42f3-8c4e-eca95390d5ca', '388115e8-abe9-441d-96cf-a39f24baa0a3', 'APPROVED'::service_item_status, NOW(), NOW(), NOW() );

3. In the prime v3 api, call getMoveTaskOrder using the move_id for the service item you created in step 2. You will need the etag for the newly created service item for the next step.

4. In the prime v1 api, call updateMTOServiceItem using a payload like this (adjust for you specific service item ID): { "id": "40b7e71a-6b03-4413-8601-dea694253ee3", "modelType": "UpdateMTOServiceItemInternationalPortFSC", "portCode": "PDX", "reServiceCode": "PODFSC" }

5. Verify that you receive a 200 response like this: { "reServiceCode": "PODFSC", "eTag": "MjAyNC0xMi0wMlQxNjo0MjoxNi42NjUwNDla", "id": "40b7e71a-6b03-4413-8601-dea694253ee3", "modelType": "MTOServiceItemBasic", "moveTaskOrderID": "813b7a43-2e3f-42f3-8c4e-eca95390d5ca", "mtoShipmentID": "8eeba537-bb40-4f58-a534-74ea9ff64590", "reServiceName": "International POD Fuel Surcharge", "status": "APPROVED" }

6. Login as a TOO user or any office user that has permissions to access the MTO page. Search up the move id that we used to setup the POD/POE. When you travel to the MTO Page, you should now see the Port of Embark or Debark populated with the Port Code, Port Name, City, State, and Zip associated with it.

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.

Screenshots

[antgmann]

Accepted Happo diffs, still reviewing

[antgmann]

Everything looks good as far as I can tell frontend wise. Storybook component works nicely, tests look good. ANDI is passing:

Only thing to keep in the back of our minds I think isn't really for what this work is focused on, but it seems like UB shipments need to be added to a couple of enums somewhere to prevent additional console errors such as these two:

Just wanted to document the above in case you guys are doing a lot with UB and see somewhere that work might fit nicely. Otherwise it could be added to a general frontend fixes feature we have open on agility.

Thanks for the good work!

[deandreJones]

thanks for adding storybook for the new component
and tests!!

looks good

[msaki-caci]

Everything looks good as far as I can tell frontend wise. Storybook component works nicely, tests look good. ANDI is passing:

Only thing to keep in the back of our minds I think isn't really for what this work is focused on, but it seems like UB shipments need to be added to a couple of enums somewhere to prevent additional console errors such as these two:

Just wanted to document the above in case you guys are doing a lot with UB and see somewhere that work might fit nicely. Otherwise it could be added to a general frontend fixes feature we have open on agility.

Thanks for the good work!

Yeah I have been noticing some funkiness with UB shipments on this BL and another one I am working on. I imagine that what you are saying is probably related. I will try to keep a look out for these things and fix them the further down the "UB rabbit hole" I go

[antgmann]

Yeah I have been noticing some funkiness with UB shipments on this BL and another one I am working on. I imagine that what you are saying is probably related. I will try to keep a look out for these things and fix them the further down the "UB rabbit hole" I go

Sounds great, thank you!

[brianmanley-caci]

Working well for me 👍