The EFM makes calls to the CMS in order to query for information pertaining to existing cases. The telephone number of the person or organization. The Street, City, State, Country, and Zip code of the person or organization. The PartyID of the organization or business. The name of the organization or business. The FilerID of the organization or business. Represents a case participant that is not a single person (e.g. Represents a case participant that is a single -78,9 +54,9 Use of the xsi:type attribute can cause parsing to fail, which could result in u
If the party cannot be found or cannot be loaded, the CMS should return an error code of their choosing along with a description to help aid troubleshooting. The court location identifier for the party. GetPartyGetParty queries for a party by the CMS's party ID and court location, which the EFM obtains from the GetPartyList API.
The party ID of the organization matching the submitted filer ID. The name of the organization or business matching the submitted filer ID. Only one party ID should be returned for the filer ID -66,7 +42,7 Use of the xsi:type attribute can cause parsing to fail, which could result in u tyler:dc101, tyler:dc356)įor court locations that do not provide the EFM with the ability to search for parties by the filer ID, the EFM will use only the filer ID information provided through case messages. That is, a search for tyler:dc should include the court locations that fall under the tyler:dc location (e.g. This value represents a location within the clerk/court hierarchy.Īs such, the filer ID search should include all child locations within the hierarchy. The intent is to retrieve a single party ID for the specified filer ID. Regarding secured parties or confidential data, the CMS should adhere to jurisdictional requirements as to whether to mask sensitive data or return such parties. GetPartyList queries for a person or organization within a particular court location, matching the filer ID. The EFM makes calls to the CMS in order to query for information pertaining to existing parties. The EFM makes calls to the CMS in order to query for information pertaining to existing parties and cases, to docket accepted filings, and to retrieve documents. Successful queries return an ErrorCode of 0.Īdditional details regarding each of these categories are provided below. Please refer to Appendix A of the OFS CMS Specification.pdf for more details about SFTP and document -37,22 +13,22 Use of the xsi:type attribute can cause parsing to fail, which could result in u RecordFiling API documentation useful since the request XML is identical with the exception of the document binaries. However, vendors implementing the one-way SFTP integration will find the This guide is targeted primarily towards CMS vendors who are building an integration to the EFM via web services.
0 kommentar(er)
