Submission Details  

From the Resolution Queue you reach the age that shows further details of the submission including a listing of the documents.

At the top of the screen is the case type information followed by a link to Change the Status of this submission.

In addition to the ability to change the status you can see the details listed from the previous page and a listing of documents.

• Tracking # - this is the ID given to the submission by the Clerk Review Interface.
• Filer ID - this is the ID given to the submission by the Filers Interface.
• Case # - this is the case number assigned by the Court CMS. If the submission is initiating a case this will be blank.
• Status - this is the last status assigned to this filing.
• Documents - this is a link to a screen that presents the Details of the Submission.
• Official File Stamp - this is the date/time recorded when the submission was received by the Clerk Review Interface.
• Filers Name - this is the name of the filer that sent in the submission.
• Client # - this is a number entered by the filer that is only of value when trouble shooting with the filer. It is especially valuable when external systems are allowed to prepare and submit filings to the system through an API.
• Listing of Documents - this is a separate section that lists the documents in the submission. Links are provided to download the documents to view.

Following the details and documents is a button called download. This allows you to download download the XML submission package.

The next button is Reset Status and Process. You would use this button when you knew the network was not communicating and you simply need to restart this submission because the network problem is resolved. There are time when this button should not be used. The error message at the top of the screen will provide the clue as to whether the condition is a simple condition or an asynchronous condition that cannot be reset by this button. Tybera will help you understand those conditions. These conditions vary from on installation to another. An example of an asynchronous condition is where eFlex has posted information in an Oracle advanced queue and the entry in the queue failed. If the status was reset eFlex would begin querying the queue for a response but the response will never be returned.

This screen also gives the Administrator the ability to reject the submission. One reason you use this reject feature is if the submission has viruses in the documents. The note field allows you to add comments about the rejection.