Skip to main content
Ecabinet Home
 
You are here ► Ecabinet > eFiling Dev > 2.1 - Test various documents and XML fields 
Go Search

eFiling Dev: 2.1 - Test various documents and XML fields

Category

22-QuickFile 

Title

2.1 - Test various documents and XML fields 

Description

Test 1.1 – 1.5 apply. +
1)  Test “what ifs” – e.g., one or more fields are missing
2) Test what happens if there are Handling Instructions (how do we input these)
3) What if we put in Plaintiff and Defendant – how will it recognize these and will it construct a Case Title?
4) What if docket number is missing?
5) What if docket number is not an electronic case?
Input:
Various XML documents with various XML fields
-- Parent “docx” of various types
-- Filing into an existing case

Status

40-NextDrop 

Priority

20-Std 

Due Date

11/27/2012 

Phase

50-QuickFile-PCR02 

TaskType

10-SoftwareDev 

AssignedTo

10-Rao 

Notes

12/27/12 Rao - See Email from  last Friday regarding file naming conventions. Also changed review screen so that when parent (i.e first document ) is accepted all children are also accepted. Same with rejection. Also can't modify the children during review process.  Document group/type for the children is derived from document if document is a smart document or from file extension.
12/6/12 RMC:  Without 1.1 - 1.5 fully working, this test is not ready for Jud Testing.
12/05/2012 - Copied Sample documents i tested with to folder \\10.226.20.68\efile\TEST\VTTestSamples. For importer to map information correctly , content control tags must match known Property names.  Recognised content control tags are
 
Organization (AKA Unit)
Division (Example Civil , Family)
casenumber (AKA Docket Numer)
CaseTitle
DocumentGroup
DocumentType
ERN
case (upper/lower) of tag does not matter. Space does matter

OldNumBeforeMay

 
Attachments
Created at 11/27/2012 15:36  by Rick Conklin 
Last modified at 1/18/2013 10:25  by Rick Conklin