Partner testing feedback
Vermont LITEFile testing on a laptop in Chrome:
- @VTskier When the tester chose a Relief from Abuse case type, Complaint was not available as a Filing Type. A complaint is expected for starting that case, so we need to determine why it is absent from the available filing codes.
Cross-repo code check
LITEFile's current get_filing_types endpoint does not maintain a Vermont-specific allow/deny list. It forwards the selected court, case category, and case type to EfileProxyServer's filing-types endpoint and sets initial=true for a new case (initial=false for an existing case):
/jurisdictions/{jurisdiction}/codes/courts/{court}/filing_types/?initial=...&category_id=...&type_id=...
That makes the proxy/code-table filtering the first place to investigate. If the proxy returns Complaint for the exact RFA selection, this can be moved back to LITEFile as a front-end problem.
Suggested investigation
- Reproduce in Vermont and record the exact court, case-category code, and Relief from Abuse case-type code.
- Query the filing-types endpoint directly with those values and
initial=true.
- Check whether a Complaint filing-code row exists for that court in the current Vermont code database.
- If it exists, verify its
initial/subsequent flag and category/type relationships and whether the query filters exclude it incorrectly.
- If it does not exist, determine whether the latest Tyler Vermont codes omit/misclassify it or whether code ingestion dropped it.
- Add a regression test/fixture for an initial Vermont RFA filing once the expected code is confirmed.
Related
Acceptance criteria
- The expected Complaint filing type is returned for the confirmed Vermont RFA initial-filing combination, or the issue documents an upstream Tyler code-data reason why it cannot be returned and the user-facing flow has an alternative.
- A regression test covers the confirmed behavior.
Partner testing feedback
Vermont LITEFile testing on a laptop in Chrome:
Cross-repo code check
LITEFile's current
get_filing_typesendpoint does not maintain a Vermont-specific allow/deny list. It forwards the selected court, case category, and case type to EfileProxyServer's filing-types endpoint and setsinitial=truefor a new case (initial=falsefor an existing case):/jurisdictions/{jurisdiction}/codes/courts/{court}/filing_types/?initial=...&category_id=...&type_id=...That makes the proxy/code-table filtering the first place to investigate. If the proxy returns Complaint for the exact RFA selection, this can be moved back to LITEFile as a front-end problem.
Suggested investigation
initial=true.initial/subsequent flag and category/type relationships and whether the query filters exclude it incorrectly.Related
Acceptance criteria