Both forms have QuerySaveAgents that include the script library. The general text search agent simply generates a Notes formula language query and builds a document collection with the database FTSearch method. The specific field value agent is more complicated. First the agent sets the initial value of the search string:

Then, the agent needs to check if the user selected a value from each of the drop down lists. If so, the agent modifies the search sting:

At the same time the agent amends the string, it will display a message confirming the search criteria to the user. After checking, if there are any matches, the agent then builds a document collection using the database Search method:

Then the two agents use the exact same subroutines contained in the script library. These subroutines generate a URL if there were no matching documents, if there was only one matching document, or generate the HTML for an entire result set. If there were no matching documents, the agent generates a URL pointing to the search form, like this:

The "&redo" parameter tells the search form to display a usually hidden paragraph telling the user that no documents matched the search criteria. If the agent finds only one matching document, then it passes the universal ID of that document to the appropriate script library function, as this shows:

When more than one document is found the agent goes to another script library function. This function builds the entire needed HTML manually. After some basic HTML tags format the page, the agent loops through the returned document collection. Within this loop, the function checks the form and adds the appropriate field value as a label in the returned results. Also, the client required that rows be alternating colors to differentiate each returned document.