Name:	[name]
Description:	[description]
Autorun?	[autorun radio keys="0;1" vals="Show search form;Run without form"]
Type	[category]
Select Library:	{execute %ufcgilib'getlibs$("srform_lib.html","srform_librow.html","srform_cathdr.html","")}
Filter:	[filter]

To configure a saved search, enter a name, select one or more libraries, enter search criteria, and save the search. When run by a user, any document in the selected libraries that meets the criteria will be selected. All entered criteria must be be true when applied to a given document for the document to be selected. Instructions The name is a unique identifier for this saved search, and is what is presented to the user when selecting a saved search. If the auto-run button is selected, then the search begins immediately when selected. If not, then the search form is presented, allowing the user to edit the search criteria (see run-time prompting, below). The type field is used to categorize the list of saved searches presented to the user. Saved searches given the same category are listed together. A search can span one or more libraries. All searches search at least one library. The filter is a simple word, phrase, or wildcard that is checked against all the data in the archive. To use a wildcard, simply use an asterisk () to represent any number of characters (including none), or a question mark (?) to represent any single character. If you want an actual or ? character, enter it as \* or \? instead. Additional criteria can be specified on other tab pages. Click Types, Dates, or Fields to access these pages. Runtime Prompting If some or all of a criteria should be entered at runtime by the user, you can enter a run-time prompt using the syntax: {{prompt text}}. Prompts discovered at runtime are presented in a form before the search is executed. User responses to the prompts replace the {{...}} text in the criteria.

	{if $datefmt = "mdy"}MM/DD/YYYY,{end} {if $datefmt = "dmy"}DD/MM/YYYY,{end} {if $datefmt = "ymd"}YYYY-MM-DD,{end} or YYYYMMDDHHMMSS with all parts after YYYY optional)
Start Date:
End Date:
Start Date Updated:
End Date Updated:
Enter date ranges, either document dates, or last updated dates, or both. The search may run faster if you specify only a limited range of document dates, as only documents in that range need to be searched. If some or all of a criteria should be entered at runtime by the user, you can enter a run-time prompt using the syntax: {{prompt text}}. Prompts discovered at runtime are presented in a form before the search is executed. User responses to the prompts replace the {{...}} text in the criteria.

Document ID:	[docid]
Entity ID:	[entityid]
Title:	[title]
Notes:	[notes]
Keywords:	[keywords]
Categories:	[categories]
Sub IDs:	[subids]
Text content:	[text]
The search fields recognize these formats: Any field can contain a list of items by entering each element separated by a comma (,) or the word or. Any item in the list may satisfy the selection criteria. For example, aging, trial balance to find either "aging" or "trial balance". In place of a comma, you can use a semi-colon (;) or the word and to indicate that all items listed must satisfy the selection criteria. For example, "invoice;12/15/06" will find documents with both "invoice" AND "12/15/06". This "and" logic can be very useful in keyword field or text content searches. At the beginning of any element, place an exclamation point (!) or the word not to indicate the criteria should not be true. For example, !scan in the Sub IDs field would find documents without a sub ID containing the text "scan". Any item may be a wildcard by including * or ? characters to represent any number of characters or any single character, respectively. For example, po ??123 to file "po", a space, any two characters, and "123". Any item may be a range by separating the starting and ending values with a dash (-). For example, 000100-000199 in the Doc ID field to find a range of document ID values. Any item may be a regular expression by prefixing it with a tilde (~). For example, ~[A-Z][0-9][A-Z] [0-9][A-Z][0-9] to find Canadian postal codes. To prevent interpretation of a comma, wildcard, dash, or tilde as described above, surround the item in quotes (") or prefix the individual character with a backslash, such as \. The search can run faster with enough information in the following fields. To utilize this, wildcards must not prevent identifying the starting characters of the field (i.e. do not use value), and can't use a regular expression. A document ID with enough starting characters to be as unique as possible A date or limited date range A category of at least two or three segments A title with enough starting characters to be as unique as possible Note that document types and IDs are case-sensitive, unless fully wildcarded (value). If some or all of a criteria should be entered at runtime by the user, you can enter a run-time prompt using the syntax: {{prompt text*}}. Prompts discovered at runtime are presented in a form before the search is executed. User responses to the prompts replace the {{...}} text in the criteria.