NOTE!! This Form Service is available only to the Notre Dame Community
Eg. <input type="hidden" name="$subject" value="My favorite Subject">
If certain fields in your forms need to be filled or selected by the form user, you can enable a mandatory option for those fields by using pre-defined hidden field $mandatory .
The tags:
St. Address : <input type="text" name="address" size=40>
City : <input type="text" name="city" size=40>
Zip : <input type="text" name="zip" size=10>
<input type="hidden" name="$mandatory" value="address, city, zip">
<input type=submit value="Submit Address">
After the form is submitted, you can send the user to another URL with the '$next_url' option. This option will be executed only when the form submission is successful.
Eg. <input type="hidden" name="$next_url" value="http://www.nd.edu/">
In the above case, a continue hyper_link will be shown to the user after the form is submitted. In the above example, clicking on continue will navigate the user to Notre Dame Home page. You can use the 'value' field to point to any valid URL.
You may also directly send user to a new URL without user action.
Eg. <input type="hidden" name="$goto_next_url" value="http://www.nd.edu/">
You may send a copy of the form content to another recipient with '$CCrecipient' option.
Eg. <input type="hidden" name="$CCrecipient" value="netid@nd.edu">
<FORM method=POST action="/cgi-bin/forms-s/feedback.cgi">
it will force the user to authenticate and user's real e-mail address will show up in the mailed form. Of course, this only works for ND users.
Viewing and Replying to Responses from Your Form
However, if you are using a vanity URL to serve your web contents, you should notify OIT HTTP Service team to map the vanity URL to your NetID e-mail account so that the mailed form can be sent to you.
The e-mail responses originate from the e-mail address "wwwforms@www.nd.edu", since there is no guaranteed way to authenticate the e-mail address of your form user. If you trust the form users and would rather see the sender's e-mail address in the response , you can add the following line to your form.
<input type="text" name="$from_email" size=40>
<input type="text" name="$from_name" size=40>
Which should look like the input fields below:
TIP: The filtering capabilities of Eudora will let you sort e-mail so that submissions from your form will go into a predetermined mailbox upon receipt.
BEWARE!: We have no way to authenticate the e-mail address and name input by the user at the form submission time unless you use the setting mentioned above to capture user's real e-mail address.
To use this method use afs_single_folder as the $NDmethod.
The file generated from the form is stored in your afs space in a directory named .wwwinbox/feedback. Each of your pages will be stored in feedback/path/formname.html. (eg. feedback/forms/guestbook.html)
Other choices to store forms content are:
*MacNote, to make the .wwwinbox visible when using MacAFS add the line "option dotfiles" to the "AppleVolumes" file in your AFS home directory.
BEWARE!: Currently, the .wwwinbox storage is only available for AFS.
CGI is a privileged service due to the security
concerns that are introduced by this interface. Since we have received a large number
of requests for forms capability from our user community we have developed this generic solution
which gives forms capability to any user without the need for custom CGI programs.
This service has been implemented so that any Notre Dame
user can deploy HTML forms in their www directory in the same way as other HTML
files. FORM providers can currently view the feedback from Web users via personal e-mail or a WWW
Inbox Service.
Our goal is to provide a functional www forms service that does not require you to write a CGI
program to handle the output of your forms. If you have any suggestions for the improvement of
this service please send them to ndoit@nd.edu.
About the Notre Dame Forms Service
Traditionally you need to write a CGI
(Common Gateway Interface) program to handle submissions from web forms. A CGI program can be
written in your favorite language (Eg. C, C++, Perl, Tcl, Fortran, Shell). The minimum
requirement is that it is executable on the Web server platform (ours is running Solaris 2.8 at this time).