Florida Courts E-Filing Portal Third Party Vendor Certification Process

Transcription

1 Application Version Release HEAT Ticket Functional Area Filer s Interface Environment Production Date 1/21/2017 Short Description: Certification Process by which Third Party Vendors will follow to connect to the Portal Table of Contents Introduction... 3 Functionality... 3 Adherence (to Standards)... 3 Resiliency... 3 Terms and Definitions... 3 Abandoned Filing Queue... 3 CMS... 3 Correction Queue... 3 Court/Clerk Case Number... 4 Exhibit... 4 Existing Case... 4 Filing Fee... 4 Lead Document... 4 NEF... 4 New Case... 4 Notification Submission Number... 4 TPV... 4 UCN... 4 Certification Process... 4 TPV Submits Application and Fee... 4 TPV Complete Integration Development... 4 XML Review... 5 TPV Provides Sample XML for Review... 5 Portal Team Provides Feedback on XML Submitted... 5 End to End Testing in Portal QA Instance... 5 TPV Submits Test Case Scenarios... 5 Page 1

2 Portal Team/Clerk Reviews... 5 End to End Testing in Portal Test Instance... 5 TPV Submits Test Case Scenarios... 5 Portal Team/Clerk Reviews... 5 TPV Executes and Submits the License Agreement... 5 Portal Team Submits Test Results, Request for Certification and signed License Agreement to Florida Courts E-Filing Authority Board... 5 Florida Courts E-Filing Authority Board Grant Certification... 5 Certification Wrap-Up... 5 Status Values... 6 Page 2

3 Introduction To maintain a high level of service quality for the Florida Courts E-Filing Portal (herein referred to as the Portal), CiviTek will provide a certification process for Third Party Vendors (herein referred to as TPVs) wishing to engage in electronic court filing in the Florida Courts System by submitting filings via web services in the Portal s production environment. The CiviTek team will provide QA and TEST environments for prospective TPVs to ensure that their implementations conform to the Florida Third Party Vendor and ECF Specification. The certification process focuses on three main areas: Functionality Functionality test cases will determine the TPV s ability to implement and consume the web services defined in the Florida Third Party Vendor and ECF Specification. Adherence (to Standards) TPVs must adhere to the web services definition stated in Florida s associated XSD document that contains the schema for input XML (requests) and output XML (responses) messages. Resiliency Additional test cases focus on the TPV s ability to handle errors identified and communicated by the Portal, such as scheduled service and unscheduled system outages. TPVs must successfully account for each of the provided error test cases during the certification process. This includes providing validation logic that addresses all preventable failures (e.g., vendor error prevention failures) and non-preventable failures (e.g., user error). Document Version Control Date Version # Editor Description of Change 1/21/ Portal Team Creation Terms and Definitions Abandoned Filing Queue When a submission is returned to the Correction Queue the filer has five business days to correct the deficiency. If the submission is not corrected and resubmitted in those five days, the submission is moved to the Abandoned Filing Queue. CMS Case Maintenance System Correction Queue When a submission has a deficiency that needs to be corrected by the filer, the Clerk returns the submission to the Correction Queue. Page 3

4 Court/Clerk Case Number The case number used by the Clerk or the Court which is an abbreviated version of the Uniform Case Number (UCN). Exhibit A document that is filed in support of a lead document. Existing Case The filing path for a case that has been created and a Uniform Case Number assigned. Filing Fee The statutory fee that is required to be paid when submitting a new case Lead Document The document that is filed with the Clerk that is requesting an action. NEF Notice of Electronic Filing that provides service of the documents in the submission. New Case The filing path that creates a new case to be filed with the Clerk. Notification The s that the Portal returns to the filer as the submission goes through the process. Submission Number The number assigned to the submission when it is received by the Portal. TPV Third Party Vendor UCN The Uniform Case Number is a 20 character number assigned to a new case and is required for state reporting purposes. Certification Process TPV Submits Application and Fee The Third Party Vendor Application can be found on the Florida Courts E-Filing Authority Board web site at www/myflcourtaccess.com. Any TPV interested in pursuing this opportunity must complete the Application and submit it along with the $500 application fee. TPV Complete Integration Development The Vendor must use the ECF 4.01 Specification and Portal extensions to integrate all available services provided by the Portal. Page 4

5 XML Review TPV Provides Sample XML for Review The TPV must provide XML samples to the Portal Team for the filing path(s) and division(s) for which they are seeking certification. Portal Team Provides Feedback on XML Submitted The Portal Team will evaluate that sample XML and provide feedback when corrections are necessary and work with the TPV to help them reach create XML. End to End Testing in Portal QA Instance TPV Submits Test Case Scenarios The TPV must complete every Test Case Scenario for the filing path(s) and division(s) to each County listed. The TPV shall provide the Submission # in the Test Case document to the Portal Team for each County. Portal Team/Clerk Reviews The Portal Team (for Portal Review) or the County (for Local Review) will verify the Test Case Scenarios using the Submission # and provide feedback to the TPVs if necessary. End to End Testing in Portal Test Instance TPV Submits Test Case Scenarios The TPV must complete every Test Case Scenario for the filing path(s) and division(s) to each County listed. The TPV shall provide the Submission # in the Test Case document to the Portal Team for each County. Portal Team/Clerk Reviews The Portal Team (for Portal Review) or the County (for Local Review) will verify the Test Case Scenarios using the Submission # and provide feedback to the TPVs if necessary. TPV Executes and Submits the License Agreement Upon successful completion of the Test Case Document, the TPV must execute and submit the License Agreement to the Portal Team. Portal Team Submits Test Results, Request for Certification and signed License Agreement to Florida Courts E-Filing Authority Board Upon successful completion of the Test Case Document and receipt of the signed License Agreement, the Portal Team will compete the Request for Certification and submit the documents to the Florida Courts E-Filing Authority Board for approval. Florida Courts E-Filing Authority Board Grant Certification The Florida Courts E-Filing Authority Board will consider the Request for Certification and the accompanying documents and grant certification. Certification Wrap-Up CiviTek will send a formal letter to the TPV confirming their certification status. Page 5

6 Status Values Status Pending XML Submission for Review Pending XML Submission for Review in one or more * Remarks Very First status RVFR XML Received for Review RVFR XML Received for Review in one or more RVFR XML Review Completed RVFR XML Review Completed in one or more Ready for end to end testing in QA instance Ready for end to end testing in QA instance in one or more End to End Testing in QA instance in Progress End to End Testing in QA instance in Progress in one or more End to End Testing in QA instance Completed End to End Testing in QA instance Completed in one or more Ready for end to testing in Portal Test instance Ready for end to testing in Portal Test instance in one or more End to End Testing in Portal Test instance in Progress End to End Testing in Portal Test instance in Progress in one or more End to End Testing in Portal Test Instance Completed End to End Testing in Portal Instance Completed in one or more Certification Request Submitted to E-Filing Authority Board Certification Request Submitted to E-Filing Authority Board in one or more Certification Request Granted by E-Filing Authority Board Certification Request granted by E-Filing Authority Board in one or more Production Access Granted If RVFR xml is sent back for corrections status will go back to the very first status In order to get this status, TPV has to successfully complete all applicable test scenarios from the Test Case document To get to this status, TPV has to successfully complete all applicable test scenarios from the Test Case document for each filing path and division in which they are seeking certification. TPV is ready to go to Production on a specified date Page 6

7 Status Production Access Granted in one or more Florida Courts E-Filing Portal Remarks * Phrase in one or more is used to indicate TPV has yet to complete the task associated with that status in one or more in which they are seeking certification. For example, status of RVFR XML Received for Review means the Portal Team has received RVFR XML for all court and filing path combinations in which the TPV is seeking certification. On the other hand, status of RVFR XML Received for Review in one or more indicates TPV has yet to submit RVFR XML for one or more court division, filing path combinations. Page 7