SuffolkLITLab / EfileProxyServer

A proxy server that acts as an Efiling Service Provider, connecting guided interviews to Efiling Managers on Tyler Technologies implementation of ECF 4.0
https://suffolklitlab.org/docassemble-AssemblyLine-documentation/docs/efiling/overview/
MIT License
3 stars 2 forks source link

Handle when both the Case category and case type don't exist anymore #171

Closed BryceStevenWilley closed 7 months ago

BryceStevenWilley commented 10 months ago

Apparently, this just works; if you are filing into an existing case, both the case category and case type just might not exist anymore. Our verifier is too strict in this case, and we'll assume that the user needs to select one of the existing case categories and types. In the Tyler docs, the case category "is only required in an initial filing", and from playing around on https://massachusetts-stage.tylertech.cloud/OfsWeb/FileAndServeModule, just showing filing types that have empty case categories and types works.

Example: 2016-P-0836 on MA STAGE; the case category is 2463, and case type is 2745 in the appeals:acp. Neither exist anymore.

BryceStevenWilley commented 7 months ago

As I realized pretty quickly, despite what might be in the docs and the information we were given from the case, we aren't able to actually do these, as we don't know what the mystery case categories should use for the ECF case type (i.e. Civil, Domestic, Appeals, etc. This information is embedded in the XML types).

From the Tyler issue we opened:

Me: However, the codes attached to the cases are not updated, and do not appear in the most recent code pulls. As mentioned in the original ticket, on MA STAGE, 2016-P-0836 had a case category code of 2463. However, the most recent code pull only showed 5796 and 5797 as available case category codes. It looks like the case category has since been updated on the case to be one of the valid codes; however, it is something that was happening, and not something that could have been fixed by a code pull. Is our only solution to open tickets for cases like that?

(Tyler rep): Yes, for those cases you would need to open a ticket. We would need to investigate it as either an EFM or CMS issue.

So unfortunately, this isn't something we can fix in the code. Closing as unable to fix.