<H3>Special Instructions</H3><p> <p>None</p> </p><H3>Description</H3><p>In RFD, there are two mechanisms defined to get a form from a Form Filler to a Form Archiver:</p><ul>     <li>The submission action is pre-encoded in the &lt;xforms:submission&gt; element of the     retrieved XForm, which points to the Form Archiver.&nbsp; It may be necessary to modify the     value of this attribute to enable testing with different Form Archiver systems.</li>     <li>The Form Filler supports the Archive Form options and specifies the desired Form Archiver     destination by encoding the archiveURL parameter in its Retrieve Form request.&nbsp; When     the Form Manager receives this request, it returns an XForm that will perform the Archive Form     transaction upon submission by the Form Filler.</li> </ul><p>In this test, a Form Filler retrieves a form from the Form Manager using HTTP-GET.&nbsp;    Form Filler knows the formID of a form with the &lt;xforms:submission&gt; element encoded    with the Form Archiver under test.&nbsp; It fills out the form and submits it to the Form    Archiver.</p><p>Form Archivers must demonstrate that they can archive form instance data (ie the xml document)    for *all* available forms (ie with all of the different formIDs) used at the Connectathon.</p><H3>Evaluation</H3><p>The ability to retrieve and archive a form will be demonstrated &lsquo;real-time&rsquo;    for the Connectathon Monitor.</p><p>On the <strong>Form Filler</strong>, in all scenarios, verify: </p><ul>     <li>Is able to complete all available fields on the form.</li>     <li>A single submit action by the Form Filler user results in submission of the form to both the     Form Receiver and Form Archiver (no extra manual step required).</li> </ul><p>If the <strong>Form Filler</strong> supports the <strong>Archive Form option:</strong> </p><ul>     <li>The <strong>Form Filler </strong>will show the Connectathon Monitor how it selects the Form     Archiver location in is application.&nbsp; Eg, this may be a configuration parameter or an     item on the Form Filler user interface.</li>     <li>The <strong>Form Manager</strong> encodes the archive destination specified by the Form     Filler properly in the XForm returned.&nbsp; This should require no manual intervention on     the Form Manager.</li>     <li>All actors will demonstrate that changing the archive destination specified by the Form     Filler automatically results in the form being submitted to the correct archive    destination.</li> </ul><p>On the <strong>Form Receiver</strong>, verify: </p><ul>     <li>The completed form was received on the Form Receiver</li> </ul><p>The <strong>Form Archiver</strong> will demonstrate for the Connectathon Monitor that all forms    (the entire xml documents) are archived as part of the Form Archiver application, ie it is not    sufficient for the Form Archiver to merely respond to the Form Filler with an HTTP response code    of 200 (OK); the forms must be saved by the application.</p><p>The Connectathon Monitor will observe that the saved forms contain all the data as entered by    the Form Filler.</p> 