-
Logged In: YES
user_id=908765
j:Case is a GJXDM structure that describes any type of case.
In this project, we use j:Case for describing many aspects
of a court case, including the defendants and case number.
CaseInformation is an OXCI-specific structure for describing
other case-related information not found in j:Case.
CaseInformation is most useful for describing new cases.
2004-11-06 04:16:10 UTC in Open XML Court Interface
-
The final development iteration, release 3.3, for the OXCI Electronic Filing Manager is complete. You may download the code through the Files tool at https://sourceforge.net/project/showfiles.php?group_id=7304 or through CVS.
2004-11-06 04:11:47 UTC in Open XML Court Interface
-
FilingConfirmations returned by the EFM only include
cf:FilingDisposition.
According to the XML Interface Specifications,
FilingConfirmations must include the following elements:
j:SubmissionSubmittedDate
j:SubmissionSubmittedTime
j:SubmissionReceivedDate
j:SubmissionReceivedTime
cf:FilingSubmissionID
j:CaseTrackingID
cf:FilingDisposition
cf:DocumentConfirmation.
2004-10-26 22:28:21 UTC in Open XML Court Interface
-
On the Filing Detail Screen, the clerk can view the
Lead Document. There is no indication of whether there
are any attached documents. The screen should
1. List the attached documents
2. Allow the clerk to view each attached document.
2004-10-26 22:18:21 UTC in Open XML Court Interface
-
Logged In: YES
user_id=908765
This is a mistake. The button is there.
2004-10-26 22:10:28 UTC in Open XML Court Interface
-
Logged In: YES
user_id=908765
Actually, Filings with a PaymentRequest attached are
received by the EFM. However, when you try to view them in
the clerk review GUI, you get the infamous " An error
occured while attempting to retrieve filings." message.
In answer to your question about "where does the Payment
attachment come from", the EFM should generate the Payment
based on the...
2004-10-26 21:57:15 UTC in Open XML Court Interface
-
The EFM accepts FilingSubmission with a Payment
attachment but not one with a PaymentRequest attachment.
There are two structures for describing payments:
1. PaymentRequest - which includes information needed
to process a payment
2. Payment - which describes a payment that has been
processed
The EFSP must be able to attach a Payment to the
FilingSubmission if the EFSP collects...
2004-10-26 03:48:24 UTC in Open XML Court Interface
-
Logged In: YES
user_id=908765
I am now seeing the callbacks. However, there are still a
couple problems:
1. When a clerk rejects a filing, the EFSP should receive an
asynchronous FilingConfirmation with the disposition of
"rejected".
2. When the filing is docketed, the filing status should
change to "filed" and the EFSP should receive an
asynchronous FilingConfirmation with the...
2004-10-26 03:36:31 UTC in Open XML Court Interface
-
The Filing Detail screen in the clerk review interface
does not include the “Process Fees” button as shown in
the Software Design document. Without this button, a
clerk cannot process a Payment Request.
2004-10-26 02:39:06 UTC in Open XML Court Interface
-
Based on the config.xml file, the Liberty adapter
appears to be using old Court Filing and Court Policy
schemas. See http://oxci.sourceforge.net/xml for the
latest schemas.
2004-10-19 03:30:17 UTC in Open XML Court Interface
