Int b 21669 doc viewer file upload status per s3 events

[samaysofo]

B-21669

Summary

This story adds UI changes that calls the server-sent event api calls for receiving real-time updates from AWS. As a user uploads a file, they will see real-time progress of the file "Uploading", "Scanning" , "Establishing document for viewing".

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.

• 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

1. Add this to your ~/.zshrc (remember to run source ~/.zshrc) to run your server
   alias aws-s3="STORAGE_BACKEND=s3 AWS_S3_BUCKET_NAME=transcom-gov-dev-app-devlocal-us-gov-west-1 AWS_S3_REGION=us-gov-west-1 AWS_DEFAULT_REGION=us-gov-west-1 AWS_PROFILE=transcom-gov-dev aws-vault exec transcom-gov-dev -- make server_run"
   NOTE: Uncomment export RECEIVER_BACKEND=sns_sqs in your .envrc to use the AWS sns_sqs .

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

How to test

1. Access the app
2. Login as an office user
3. Navigate to the respective queues
4. Select a move and click "View and edit orders"
5. Delete all uploaded files(both Manage Orders and Manage Amended Orders) if there are existing ones.
6. Should see "File Not Found"
7. Upload a new file
8. Should see "Uploading" when the file is in the upload status
9. Once upload is complete, should see "Scanning" (note: current the scan takes ~20 secs +/-)
10. When the scan is complete, then should see "Establishing document for viewing" and document displays.
11. In order to test out the already uploaded/scanned file, navigate back to the "Move details page" and click "View and edit orders"
12. Should see "Establishing document for viewing" and document displays.
13. Repeat step 5-9, and navigate back to the "Move details page" while "Scanning" is still in progress.
14. Then click "View and edit orders" to go back to the file being uploaded, should see "Scanning" if the anti-virus scan is not yet complete.

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

B-21669-File-Upload-Progress.mov

dismissing review