Main b 22692

[brianmanley-caci]

Agility ticket

INT PR

Summary

Feature E-06260 is for adding the ability for the Prime to send an acknowledgement date for moves and shipments. This story does the DB work to prepare for that capability. We are adding a new prime_acknowledged_at column to the moves and mto_shipments tables to store that prime acknowledgement value. We are also adding a new function to take in the acknowledgement data sent by the prime, validate it, and update the prime_acknowledged_at DB values accordingly.

Is there anything you would like reviewers to give additional scrutiny?

this article explains more about the approach used.

Verification Steps for the Author

These are to be checked by the author.

• 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 build successful?
• Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

How to test

One note for testing. The prime_acknowledged_at column can only be populated once. For repeated testing make sure to null out the column values, or you'll just get stuck with the initial value you populated.

1. Run the migrations.
2. Verify that the new prime_acknowledged_at column is on the moves and mto_shipments tables and the proc is there. You can run
   SELECT * FROM information_schema.columns WHERE table_name in ('moves', 'mto_shipments') AND column_name = 'prime_acknowledged_at';
   , and
   SELECT * FROM pg_proc p JOIN pg_namespace n ON p.pronamespace = n.oid WHERE n.nspname = 'public' AND p.proname = 'prime_acknowledge_moves_shipments';
   , or you can just look for them in DBeaver like a normal person.
3. In DBeaver grab some move and shipment data from the database that can be used to pass to the procedure. You'll just need the move IDs and shipment IDs.
   select m.id as move_id, ms.id as shipment_id, m.prime_acknowledged_at as move_prime_acknowledged_at, ms.prime_acknowledged_at as shipment_prime_acknowledged_at from moves m join mto_shipments ms on m.id = ms.move_id;
4. Call the new procedure to populate the prime_acknowledged_at columns for the moves/shipments you selected. Here is an example with a json string you can use, but you'll need to plug in your move and shipment IDs.
   CALL prime_acknowledge_moves_shipments( '[ { "id": "7c982615-d1e2-44ad-bfbb-b1d22ec29df3", "primeAcknowledgedAt": "2025-12-20T14:15:22Z", "mtoShipments": [ { "id": "d76ae57b-a0da-4dc7-b493-74f11fd6193d", "primeAcknowledgedAt": "2025-12-21T14:15:33Z" } ] }, { "id": "d4d95b22-2d9d-428b-9a11-284455aa87ba", "primeAcknowledgedAt": "2025-12-22T14:16:32Z", "mtoShipments": [ { "id": "acf7b357-5cad-40e2-baa7-dedc1d4cf04c", "primeAcknowledgedAt": "2025-12-23T14:16:44Z" } ] } ]'::jsonb );
5. Query the moves and mto_shipments tables to verify the columns were populated. Make sure to plugin your move and shipment IDs.
   select m.id as move_id, ms.id as shipment_id, m.prime_acknowledged_at as move_prime_acknowledged_at, ms.prime_acknowledged_at as shipment_prime_acknowledged_at from moves m join mto_shipments ms on m.id = ms.move_id where m.id in ('7c982615-d1e2-44ad-bfbb-b1d22ec29df3', 'd4d95b22-2d9d-428b-9a11-284455aa87ba') and ms.id in ('d76ae57b-a0da-4dc7-b493-74f11fd6193d', 'acf7b357-5cad-40e2-baa7-dedc1d4cf04c');

Play around with some different scenarios that could break this:

1. Non existent move and/or shipment IDs.
2. Shipments nested in moves they don't belong to.
3. ...

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.

Database

Any new migrations/schema changes:

• Follows our guidelines for Zero-Downtime Deploys.
• Have been communicated to #g-database.
• Secure migrations have been tested following the instructions in our docs.

Screenshots

[danieljordan-caci]

Code and commits match up!

[msaki-caci]

LGTM