triston-notes/+ Encounters/CheckWriter Update Requirements.md

up:: tags::

Check Writer Update Requirements

Frontend

1. Move sub menus below table?
   1. "View checks to be printed"
   2. "void checks"
   3. "check register"
   4. "voided check register"
2. The menus open new pages/UI ( #new pages Q's )
3. Need to build 3 status.. below what?
   1. need to print
   2. printed
   3. voided
4. default fields
   1. check number needs to be provided by api #API
   2. date default today
5. override check button beside check number field
   1. create modal with override reason dropdown and save
   2. needs new api route? #API
6. remove reprint button
7. print button control flow
   1. yes/no correct check number varification
   2. ok checks for correct client verification
   3. ok checks loaded in printer properly
   4. yes/no checks in sequence (will initiate print) ( #Checks in sequence )
   5. yes print pdf (native print pdf modal)
   6. ... done printing
   7. yes/no check print success ( #Check print success )
8. display payee fields seperately ( #API )
9. void checks ui search field (#Void checks search field #API)

API

1. provide last check printed number on api requests
2. check number override reason api route?
   1. paper jam
   2. cartridge issue
   3. ventra checks
3. may need to split payee details
4. need to create a full void check search api route accepting client&check_number
5. hco auto process triggered automatically apon check status change

Questions

new pages

• do we need permissions on routes?
• do we need api to provide new routes?
• will hard coded check manager routes be fine? e.g. url/check-manager/to-be-printed these should only be available when check-manager main route available which will make the main permission to route apply to sub routes

Check print success

• unable to know status of print, so modal will appear immediately after print is started.

Checks in sequence

• wont see checks until print dialogue appears. Should we instead have a PDF viewer in the UI like with EOC manager?

Void checks search field

• so this takes a client number so that means its just a general void checks page (), nothing to do with the currently selected document?

Void checks page

• this is just a general page with two text fields and a table that will be populated with one check? so a user needs to search every check individually
• a NEW screen needs to appear just to select a void reason? or do you need a modal?