Common use of Submission Methods Clause in Contracts

Submission Methods. SECURE G2G Portal User Interface (UI) – State Government Agencies who will be scanning paper or uploading image files directly into the SECURE G2G Portal must use a token for authentication. State Government Agencies will receive recording confirmation via the UI. The UI allows user to upload a pre-scanned 300 DPI TIFF Group IV image or use a browser scanner ▇▇▇▇▇ plugin. SECURE G2G Portal Web API (API) – State Government Agencies that directly connect to the API must adhere to the XSD standard. The XML files that are uploaded must include Base64 encoded 300 DPI TIFF Group IV image files. This process does not require a user to be involved in the transfer; it is an automatic process that will be programmed by the submitter in conjunction with the County. State Government Agencies will receive recorded information via XML return batch. SECURE G2G Portal File Transfer Site (File Transfer Site) – State Government Agencies that use the File Transfer Site will use secure file transfer protocols (FTPS or SFTP) to upload XML files. The SECURE G2G Portal will process the XML files uploaded by State Government Agencies and submit the XML files to the SECURE Web API on behalf of the State Government Agencies. The XML files shall remain encrypted in transit until they reach the designated Participating County. XML files containing recording confirmations will be placed on the File Transfer Site within one Participating County business day, not including Participating County’s holidays, for State Government Agencies to retrieve. The design of the single standard XML file format for use with the File Transfer Site will include all elements required by any County for recording documents. State Government Agency will use a standard naming convention to identify the Partner or Owner Participating County with which the file is to be recorded. State Government Agency will confirm that the name of the response file reflects the same county that was identified in the submission file.

Submission Methods. SECURE G2G Portal User Interface (UI) – The State Government Agencies who will be scanning paper or uploading image files directly into the SECURE G2G Portal must use a token for authentication. The State Government Agencies will receive recording confirmation via the UI. The UI allows user to upload a pre-scanned 300 DPI TIFF Group IV image or use a browser scanner ▇▇▇▇▇ plugin. SECURE G2G Portal Web API (API) – The State Government Agencies that directly connect to the API must adhere to the XSD standard. The XML files that are uploaded must include Base64 encoded 300 DPI TIFF Group IV image files. This process does not require a user to be involved in the transfer; it is an automatic process that will be programmed by the submitter in conjunction with the County. The State Government Agencies will receive recorded information via XML return batch. SECURE G2G Portal File Transfer Site (File Transfer Site) – The State Government Agencies that use the File Transfer Site will use secure file transfer protocols (FTPS or SFTP) to upload XML files. The SECURE G2G Portal will process the XML files uploaded by the State Government Agencies and submit the XML files to the SECURE Web API on behalf of the State Government Agencies. The XML files shall remain encrypted in transit until they reach the designated Participating County. XML files containing recording confirmations will be placed on the File Transfer Site within one Participating County business day, not including Participating County’s holidays, for the State Government Agencies to retrieve. The design of the single standard XML file format for use with the File Transfer Site will include all elements required by any County for recording documents. The State Government Agency will use a standard naming convention to identify the Partner or Owner Participating County with which the file is to be recorded. The State Government Agency will confirm that the name of the response file reflects the same county that was identified in the submission file.