Manually plan out all of the API calls we need to be able to make to their servers, and map onto the API we already have / support.
Similar to #398, the main thing here is how to indicate what features / calls a specific vendor / jurisdiction supports.
Tyler has all of the functions that already exist in the codebase.
TrueFile has:
- GetPolicy
- ReviewFiling
- GetFees
- GetCaseList
- GetCase
- GetDocument
- NotifyReviewFilingComments (the callback)
Still under the same Filing Review MDE, Court Record MDE, etc.
Our general architecture does reflect that layout, but should be more explicit about it (I can't imagine us supporting non-ECF standards at this point, yes to non ECF filing, but we can probably do that in a way that it follows the ECF interface best we can).
Manually plan out all of the API calls we need to be able to make to their servers, and map onto the API we already have / support.
Similar to #398, the main thing here is how to indicate what features / calls a specific vendor / jurisdiction supports.
Tyler has all of the functions that already exist in the codebase.
TrueFile has:
Still under the same Filing Review MDE, Court Record MDE, etc.
Our general architecture does reflect that layout, but should be more explicit about it (I can't imagine us supporting non-ECF standards at this point, yes to non ECF filing, but we can probably do that in a way that it follows the ECF interface best we can).