Some many dumb question order dependencies when it comes to e-filing:
- does the user want to efile?
- what court they are filing in?
- if we know they want to efile, can filter these
- if we know this, can show if they are able to e-file or not
- user's address
- if we know this, we can filter for the best court
- if the user is logged in, they don't have to enter their address again
The user's ideal flow (minimal re-entry, assumes all courts can handle e-filing, SRLs over attorneys):
- interview proceeds as normal, user enters contact info / address
- get court user wants to file into
can_check_efile as normal
- if user needs to register a new account, re-use all of the info already entered
Easier flow to implement (still assumes all courts can handle e-filing):
- ask if user is interested in e-filing
- have them log into to Tyler's e-filing / register account early, without knowing the court
- continue interview, user doesn't have to re-enter contact info / address after registration
- checks the court after getting the address
Some many dumb question order dependencies when it comes to e-filing:
The user's ideal flow (minimal re-entry, assumes all courts can handle e-filing, SRLs over attorneys):
can_check_efileas normalEasier flow to implement (still assumes all courts can handle e-filing):