Docket Clerk: Direct scan paper filing, preview, then associate with case

As a Docket Clerk, in order to make sure the right document gets uploaded, I need the ability to scan paper documents directly into the system and review the document before it is associated with a case/docket entry.

The Court will continue to receive paper filings. As a result, Docket Clerks will need the ability to get those paper documents into the system. The idea that a Docket clerk would scan, save, and upload the document leaves a lot of room for error that the wrong document will be uploaded. Plus, it involves multiple steps. To avoid this, the Docket Clerks will need the ability to directly scan a document into the system (#1066) and be provided a review feature (#1566) before doc is associated with case/docket entry

Pre-Conditions:

Docket Clerk has received a paper filing from a party in a case
A case exists in the system for the party submitting the external filing

Acceptance Criteria:

Docket Clerk has the ability to scan paper documents directly into the system without having to perform a separate scan, save and upload function.
Docket Clerk can see that the document has been scanned successfully into the system (before it's added to the docket record)
Docket Clerk can preview the content of the document that was uploaded to confirm it's correct (before it's added to the docket record)
Docket clerk can delete the document if it's incorrect or scanned poorly (before it's added to the docket record)
A cover sheet should be added to the document before it's added to the Docket Record
Docket clerk can add the scan to the docket entry when creating the docket entry
Once added to the docket record, the scanned document is available for the Docket Clerk to view
New docket entries (with a document) appear in the My and Section Document QC Processed tabs
Reduce chances of user accidentally clearing a scan

Notes:

Functionality for this story is tied to https://github.com/flexion/ef-cms/issues/1895, and may be under development.
~Should we include CLAM AV scans for internal users as well?~ No
Some documents require multiple scans (more than 50 pages) to create one document
Design note 6/10/19 - consider removing scan button once the document has been uploaded
This story is intended to capture scanning a document and creating a docket entry all at the same time. The ability to scan/upload a document after the docket entry is created is handled in another story #1567

Tasks

[x] Update/refactor view for Create Docket Entry (currently Add Document) (Cody, Matt, Jojo #2656) ~- [ ] Validation for docket entry that does not include adding a document as required~ (This is handled in #1567)
[x] Add scanning/preview module to page (MOB together) (Cody, Matt, Jojo #2656)
[x] Update/refactor adding supporting/secondary documents
[x] Implement incomplete scan error handling if user has scanned 1 or more batches and tries to click "Finish" (Cody, Matt, Jojo #2656)
[x] Create Document QC entry for newly created docket entry

Definition of Done (Updated 7-10-19)

Product Owner

[x] Acceptance criteria have been met

[x] Usability has been validated

Team

[ ] Test scenarios to meet all acceptance criteria have been written

Engineering

[x] Field level and page level validation errors (front-end and server-side) integrated and functioning (Joe)
[x] New screens have been added to pa11y scripts (Matt)
[x] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html - (Matt)
[x] READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated - (Cody)
[x] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
[x] Module dependencies are up-to-date and are at the latest resolvable version (npm update)
[x] Errors in Sonarcloud are fixed https://sonarcloud.io/organizations/flexion-github/projects (Matt)
[x] Lambdas include CloudWatch logging of users, inputs and outputs (Matt)
[x] Code refactored for clarity and to remove any known technical debt
[x] Deployed to the dev environment

Scan with New Docket Entry

Docket Clerks may manually add a filing to a case with a docket entry.

Important: This is an expansion of prior work which incorporates several changes to the existing metadata form and task flow.

Add Docket Entry Screen

Docket clerks arrive on "Add Docket Entry" page via a link on the "Case Detail" page
This story uses the same scan / upload utility from Petitions #1895 with no changes
User must enter required metadata but does not have to optional metadata
Wireframes in figma show versions of the dynamic form
"Add Another Entry"
- saves the current data as a distinct entry on the docket record
- sets "paper" icon for entry on docket record
- takes the user to a fresh "Add Docket Entry" page
"Finish"
- saves the current data as a distinct entry on the docket record
- sets "paper" icon for entry on docket record
- takes the user to the case detail page with a confirmation message
- creates an item in that docket clerk's Document QC Processed box assigned to that docket clerk (also appears in Section Inbox)
"Cancel" triggers "are you sure" modal - if user says yes, returns the user to the case detail page with no action taken

Add Another Docket Entry

DC is given a fresh docket entry page for a brand new, distinct docket entry (no pre-filled information)
A confirmation message is displayed to acknowledge the previous entry has been saved
Use the same metadata fields and dependent display rules as before
"Cancel" applies only to current entry data - previous entries are not affected

Complete Docket Entry

Clicking "Finish" sends clerk to case detail page
Confirmation message appears on case detail to acknowledge docket entry
Creates an item in that docket clerk's Document QC Processed box assigned to that docket clerk (also appears in Section Inbox)

Test Scenarios: Published 8/2

The following test scenarios from #1895 apply. Details provided where the scenario differs materially from the counterpart from #1895.

Set-Up Flow

[x] Verified test scenario
Docket clerk logs in
Navigates to Case Detail page
Selects "Add Docket Entry"
Sees "Add Docket Entry" page
Scan radio button is selected by default

Document Upload Flow

[x] Verified test scenario

Add First Batch Flow

[x] Verified test scenario

Preview Multiple Batches Flow

[x] Verified test scenario

Create PDF Flow

[x] Verified test scenario

Add Another Entry without Errors Flow

[x] Verified test scenario
[scan flow]
[create PDF flow]
Enter metadata
Click Add Another Entry
Sees Add Docket Entry page (default) with confirmation message
Fills out all required fields and clicks Finish
Taken back to Case Detail page and see BOTH documents are entered as docket records with paper file icon and doc title is linked to document detail page
View Document QC Processed box and see BOTH newly created records listed there assigned to you (docket clerk)

Add Another Entry with Errors Flow

[x] Verified test scenario
[scan flow]
[create PDF flow]
Enter metadata (skipping a required field)
Click Add Another Entry
Sees page and field level error messages

Cancel Docket Entry Flow

[x] Verified test scenario
Sees Add Docket Entry Page
Clicks Cancel
Sees "Are you sure" modal
- Select yes, sees Case Detail Page and no docket record is created
- Select no, returns to Add Docket Entry page and all information is still intact

Cancel Docket Entry of 2nd Document Flow

[x] Verified test scenario
Adds first docket entry and clicks "Add Another Entry"
Sees new docket entry screen and clicks cancel
Sees "are you sure" modal and clicks yes
Returns to case detail where first docket entry is correctly logged (no 2nd entry)

Unfinished Scans Flow (see Non-Petitions Document Not Finished)

[x] Verified test scenario

PO review 8/13/19 -- will be addressed as regression bugs in 1567: (1) the additional info 1 and 2 are not populating on the docket record; (2) additional info 1 is not showing on cover sheet when that box is selected; (3) the code for a lodged document is always “MISL” not the normal code for that doc — see 486-19 entry 8 — you may want to talk to Rachael about this as I know she changed it on the file a doc flow

flexion / ef-cms