Skip to main content
Ecabinet Home
 
You are here ► Ecabinet > eFiling Dev > 1.1 - Basic Quick File submission 
Go Search

eFiling Dev: 1.1 - Basic Quick File submission

Category

22-QuickFile 

Title

1.1 - Basic Quick File submission 

Description

File watcher takes in a quick file document for an existing case.  User able to call up document in Clerk Review with the metadata filled in (from the XML fields in the document).  Document is rejected (via Error Procedure) if the docket number is not in eCabinet.  Clerk "Accepts" "Completes" this single filing.  Document is successfully added, available in Clerk Viewer.
Tests:
1) Tests file watcher and input mechanism (new U:QuickFile folder)
2) Tests taking document, placing into proper Work Queue (unit/division), and automatically filling in the metadata for Clerk Review.
3) Tests error procedure (NOTE:  per phone status on 11/16:  if error, sends email, with comprehensive error message and error document attached, to submitter if ERN is valid, to system administrator(s) if ERN is not valid).
4) Tests Clerk/Judge Viewer results after Clerk Review complete.
Input:
Sample test documents supplied.
Other similar test documents as determined by Judiciary
- Filing into an existing case
- Also note more detailed “Quick File 1.1 Test Case” pseudo code in sharepoint.

Status

25-NeedsFixes 

Priority

20-Std 

Due Date

10/31/2012 

Phase

50-QuickFile-PCR02 

TaskType

10-SoftwareDev 

AssignedTo

10-Rao 

Notes

1/23/13: CF Added Michael P's email to attachments "signature graphic not captured in pdf".  Changed status to "needs fixes".  Quickfile doc contained a picture of a signature block; pdf on clerk review screen did not display the graphic.
01/02/2012 Rao - Applied corrections to Review screen to address issues in attachment "2012-12-28 - Testing 6 docs"
 
12/28/12 RC/CF:  See attachment, "2012-12-28 - Testing 6 docs not able to change metadata".
 
12/27/12 Rao - Please note the changes to File naming Conventions as per email/discussion from Last Firday. Event Number Tag Name is "EventNumber" (case does not matter). Also corrected Email (Replaced Smart Document ... with Quick File). Can change external email template if needed
12/21/12 RMC: Per phone call today: want to put an XML field for "event number" in smart docs with a hard coded zero for now – so would put in the logic to move the value into the metadata in case we want to insert a real value in the future.
12/18 RMC: Rao - Error Message Text is not correct.  We will have Michael review.  One thing- this system is called "Quick File" here, not the name you gave it in the top of the error message that I saw.
12/14/12 CF:
1.1.1. Successful (docx transmitted to eCab)
1.1.2. Partial success.  Clerk review fields populated EXCEPT event # = "0" (see structure Englist 1.2.2.3.4)
1.1.3 FIX NEEDED: Error testing produced system emails sent to ERN when valid, system admin when no valid ERN.  Rao -PLS CREATE WAY FOR US TO MAINTAIN LIST OF SYS ADMINS via the Admin screens.  List of errors tested is below.  Screenshots will be attached of the contents when Sharepoint can upload docs.)
Error 1- No docket number
Error 2  No docket number, invalid ERN
Error 3  No Unit (omitted inadvertently) and no doc group
Error 4 - WRONG docket number
1.1.4 Judge and Clerk search and review screens successful in accessing the filed docx.
 
12/6/12 RMC: Not sure why this is still in "being developed" state, except maybe the error messages are not working??  I think if this Test doesn't work none of the others will. (We tried to move on to Test 1.2 -- see those notes).
11/30/12 RMC:  Cindy/Rick - test what happens for the default of Folder/Subfolder.  Do we need a way to set "defaults" for certain doc types (e.g., does WRJV default to Not Public/Confidential)?
11/1/2012 RMC: Michael sent second template, attached. I believe Rao asked for another example of a QuickFile document.  See attached.  This is a hearing notice, which is being developed as part of eNotices version 2. The document_group and document_type tags are at the bottom of the page.  I may make the font white so they don’t show to the user, but I left them black for now so it’s not confusing.

OldNumBeforeMay

 
Attachments
2012-10-18-Generic--AMCAD Sample.docx    
2012-11-1-Paper_Notice_Template.docx    
2012-12-28 - Testing 6 docs not able to change metadata.docx    
QF1-1StructuredEnglishSpec.docx    
Signature graphic not captured in pdf.docx    
Created at 11/7/2012 11:05  by Rick Conklin 
Last modified at 1/23/2013 13:28  by Cindy Foster