Court: Create an order tied to a message thread

[mariahkannenberg]

As a court employee, so I can create an order in response to an open message thread, I need the ability to create an order that's associated to the thread.

Pre-Conditions

Acceptance Criteria

• Court user can create an order from a messaging thread
• The new order is "attached" to the message
• When the order is saved, user is routed back to the message page
• Order should appear in draft documents

Security Considerations

• Does this work make you nervous about privacy or security?
• Does this work make major changes to the system?
• Does this work implement new authentication or security controls?
• Does this work create new methods of authentication, modify existing security controls, or explicitly implement any security or privacy features?

Notes

• Update Apply Signature screen for the Create Order flow to include "Skip Signature"

Tasks

• 1 Add “Create Order” link to message actions - should open modal (Rachael 4611: add Create Order button to message details; open modal #5597)
• 2 Add Skip Signature button and functionality to Apply Signature screen (Cody 4611 - adding the skip signing button #5605)
• 3 Navigate back to Message Detail with success message displayed after skipping or saving signature (Rachael 4611: navigate back to message detail after signing created order #5608)
• 4 Update create order endpoint - send messageId in props; submitted Order is attached to the latest message in the thread (Rachael 4611: submit order from message and add as attachment #5599)

Definition of Done (Updated 6-19-20)

Product Owner

• Acceptance criteria have been met

UX

• Business test scenarios to meet all acceptance criteria have been written
• Usability has been validated
• Wiki has been updated (if applicable)
• Story has been tested on a mobile device (for external users only)

Engineering

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

[klohman]

Updated Message Detail screen

• Add "Create Order" link to message actions

On click of "Create Order"*
Use current order creation functionality:

• User selects the title of the order
• User enter/pastes Order text and saves

Updated Apply Signature Screen

• On Save of the Order, app navigates to Apply Signature screen

On load of screen

• Skip Signature button displays
  

After signature has been applied

• Save Signature button displays
• Delete Signature button displays
• Skip. Signature button is hidden

On click of Delete signature

• Signature is removed
• Skip Signature button is displayed
• Save Signature button is hidden
• Delete Signature button is hidden

On click of Save Signature

• App navigates back to Message Detail screen with success message displayed
• Order is added to Drafts documents table
• Order is attached to Message
• Order is displayed as attachment on Message Detail screen

[klohman]

4611 + 4612

4611 Test Scenarios

1) Internal user launches order flow from Message Detail

• Login as docket clerk 1
• Navigate to Case xx1-20
• Create New message w/o attachments - subject line: Need Order
• Send to docket clerk 2
• Login as docket clerk 2
• Click on message “Need Order”
• Click “Create Order” on Message Detail screen
  Expected results

• Create Order or Notice modal displays

2a) Internal user skips signature in order flow from Message Detail

• Scenario 1
• Select “Order” as order type
• Click Continue
• Enter Order Text
• Save
• Click Skip Signature
  Expected results
  On click of Save:

• App navigates to Apply Signature screen with “Skip Signature” button displayed

On click of Skip Signature:

• App navigates to Message Detail with success message displayed
• Order is attached to Message
• Order is saved into Draft Documents without signature

2b) Internal user skips signature in order flow from Case Detail

• Login as docket clerk 1
• Navigate to Case xx1-20
• Click “Create Order or Notice” from case Actions dropdown
• Select “Order for Dismissal” as order type
• Enter Order text
• Save
• Click Skip Signature
  Expected results
  On click of Save:

• App navigates to Apply Signature screen with “Skip Signature” button displayed

On click of Skip Signature:

• App navigates to Draft Documents tab with success message displayed
• Order is saved into Draft Documents without signature

3a) Internal user adds signature in order flow from Message Detail

• Scenario 1
• Select Order as order type
• Enter Order text
• Save
• Apply signature to PDF
  Expected results:

• Skip Signature button is hidden
• Save Signature button displays
• Delete Signature button displays

3b) Internal user adds signature in order flow from Case Detail

• Login as docket clerk 1
• Navigate to Case xx1-20
• Click “Create Order or Notice” from case Actions dropdown
• Select “Order to Show Cause” as order type
• Enter Order text
• Save
• Apply signature to PDF
  Expected results

• Skip Signature button is hidden
• Save Signature button displays
• Delete Signature button displays

4a) Internal user saves signature in order flow from Message Detail

• Scenario 3a
• Click Save Signature button

• Expected results
• App navigates to Message Detail with success message displayed
• Order is attached to Message
• Order is saved into Draft Documents with signature

4b) Internal user saves signature in order flow from Case Detail

• Scenario 3b
• Click Save Signature
  Expected results

• App navigates to Draft Documents tab with success message displayed
• Order is saved into Draft Documents with signature

5) Internal user sees new order attached to original message on Message Detail

• Scenario 4a
• View Order PDF
  Expected results

• Order is displayed as attachment to message
• On select of Order, Order PDF is displayed in the PDF viewer

6) Internal user sees new order attached to message when replying to message

• Scenario 5
• Click Reply
  Expected results

• Order displays in Reply to Message modal under Attachments

7) Internal user sees new order attached to message when forwarding message

• Scenario 5
• Click Forward
  Expected results

• Order displays in Forward Message modal under Attachments

8) Internal user creates Notice from Message Detail

• Scenario 1
• Select. "Notice" as Order type and Continue
• Enter Notice text
• Click Save
  expected results

• App navigates to Message Detail with success message displayed
• Notice displays as attached to message
• Notice is saved into Draft Documents

[klohman]

UX feedback

-[ ] When creating a Notice from the Message Detail - on Save, app should navigate back to the Message Detail screen with notice attached (I didn’t specifically outline this but have now added a text scenario)

• Order Flow from Case Detail > On Save of Signature should navigate to Drafts screen (currently it’s going to the Draft Document Detail)