<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- 
This is the search template file (search_template.html) which contains the layout
to your search page. 

Note that you can not access the search function from this page (by default). Instead, 
you should open or link to the search script, which is a file named "search.php", 
"search.asp", or "search.cgi".
-->
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252" />
	<title>Example Zoom search template page</title>	
	<!-- 
	You can change the fonts, colors, and styles of your search results with the CSS below.
	For some examples and more information on Cascading Style Sheets (CSS), visit our support page at:
	http://www.wrensoft.com/zoom/support/css.html
	-->
	<style type="text/css">
		.highlight { background: #FFFF40; }
		.searchheading { font-size: 130%; font-weight: bold; }
		.summary { font-size: 80%; font-style: italic; } 
		.results { font-size: 100%; }
		.category { color: #999999; }
		.description { font-size: 100%; color: #008000; }
		.context { font-size: 100%; }
		.infoline { font-size: 80%; font-style: normal; color: #808080;}
		.sorting { text-align: right; }
		.result_title { font-size: 100%; }

		.zoom_searchform { font-size: 100%; }
		.zoom_options { font-size: 80%; }
		input.zoom_button {  }
		input.zoom_searchbox {  }		
	</style>		
</head>

<body>

	<!-- 
	The ZOOMSEARCH tag below marks the place where your search form and search results
	will be inserted when you run the search script. By default, you do not need to place a 
	search form here, the search script will generate one and display it before the search 
	results. Also note that the ZOOMSEARCH tag should be on a seperate line of its own.
	-->
	<h1>Search this site</h1>
	<p>
	Enter one or more keywords to search for using the Zoom Search Engine.<br />
	Note that '*' and '?' wildcards are supported.
	</p>	
	
<!--Zoom Search Engine Version 4.2 (1013) PRO-->
<form method="get" action="sitesearch.cfm" class="zoom_searchform">
Search for: <input type="text" name="zoom_query" size="20" value="operator" class="zoom_searchbox" />

<input type="submit" value="Submit" class="zoom_button" /> 
<span class="zoom_options">Results per page:
<select name='zoom_per_page'>
<option selected="selected">10</option>
<option>20</option>
<option>50</option>
<option>100</option>
</select><br /><br />
Match: <input type="radio" name="zoom_and" value="0" checked="checked" />any search words
<input type="radio" name="zoom_and" value="1" />all search words
<input type="hidden" name="zoom_sort" value="0" />
</span>

</form>
<div class="searchheading">Search results for: operator</div><br />
<div class="results">
<div class="summary">5 results found.<br /></div>
<br />Did you mean: <a href="sitesearch.cfm?zoom_query=Opportunity&amp;zoom_page=1&amp;zoom_per_page=10&amp;zoom_cat=-1&amp;zoom_and=0&amp;zoom_sort=0">Opportunity</a> or <a href="sitesearch.cfm?zoom_query=Operators&amp;zoom_page=1&amp;zoom_per_page=10&amp;zoom_cat=-1&amp;zoom_and=0&amp;zoom_sort=0">Operators</a>?<br /><p></p>
<div class="result_title"><b>1.</b>&nbsp;<a href="http://dev.fsenablers.com/fse/_devteam/griffin/updates/Operator_Portfolio_Update_081610.htm">I have made some significant changes to the Add <span class="highlight">Operator</span> Dialog box</a></div>

<div class="context">
 <b>...</b>  I have made some significant changes to the Add <span class="highlight">Operator</span> Dialog box. It now is split across two tabs, this was done to create more room for fields <b>...</b></div>
<div class="infoline"></div>
<p></p>
<div class="result_title"><b>2.</b>&nbsp;<a href="http://dev.fsenablers.com/fse/_devteam/griffin/updates/Lookup_Manager_Update_122910.htm">The new version can be given to our client library users</a></div>
<div class="context">
 <b>...</b>  users. The client library users will only see two" Sub Modules ": <span class="highlight">Operator</span> Segments, and CRM Campaigns. When lookup manager is given to a client library account <b>...</b></div>

<div class="infoline"></div>
<p></p>
<div class="result_title"><b>3.</b>&nbsp;<a href="http://dev.fsenablers.com/fse/_devteam/griffin/updates/Opportunity_Pipeline_Distributor_Portfolio_Update_081110.htm">All,</a></div>
<div class="context">
 <b>...</b>  column is an indicator column to indicate if a Sales Deal exists for the <span class="highlight">operator</span> or not. If a Sales Deal is present a $will appear in this column <b>...</b></div>
<div class="infoline"></div>
<p></p>

<div class="result_title"><b>4.</b>&nbsp;<a href="http://dev.fsenablers.com/fse/_devteam/griffin/updates/history.cfm">No title</a></div>
<div class="context">
 <b>...</b>  / 01 / 2010-Opportunity Pipeline Update 08 / 16 / 2010-<span class="highlight">Operator</span> Portfolio Update 08 / 11 / 2010-Opportunity Pipeline Distributor Portfolio Update 07 / 22 <b>...</b></div>
<div class="infoline"></div>
<p></p>
<div class="result_title"><b>5.</b>&nbsp;<a href="http://dev.fsenablers.com/fse/_devteam/griffin/updates/Opportunity_Pipeline_Update_072010.htm">This release include a "Bread Crumb" style territory list at  the top to help users see where they are in territory structure</a></div>

<div class="context">
 <b>...</b>  future. An Affiliation filter has been added to the search center for the <span class="highlight">Operator</span> Opportunity Pipeline. Also when the pipeline is filtered, the dashboard tab only shows the <b>...</b></div>
<div class="infoline"></div>
</div>
	
</body>
</html>

