As shown in the previous test drive, Querying with Numeric Property Operators, you can create forms and query scripts that put many useful features of Index Server at the disposal of users. In this test drive, you will see how a single query form can allow the user to select different result formats.
The line of code should now look like this:
<INPUT TYPE="HIDDEN" NAME="ColChoice" VALUE="3">
You should see a result set that displays the following information: The record number, the file name, the URL to the document, the size of the file, and the last modification date and time.
The line of code should now look like this:
<INPUT TYPE="HIDDEN" NAME="ColChoice" VALUE="2">
The query results show the physical path to each file matching the search, with a link to the file.
When you selected the different output formats (ColChoice), the form actually referenced different output templates in the form-data and query script. A single query form can reference several different output templates to show different sets of data in different formats. So, an administrator could give users customized views, such as a table view sorted by author or modification date, or a conventional record view similar to the Index Server standard result set.
With Index Server you can create a set of query forms and a set of output templates, and have them interoperate with each other to give customized queries and result views. The template forms can be programmed to remember which query form called them so that the a link such as the New Query link in the Simple Content Query form returns the user to the previous form.