Search Customization

Dear community,
I would like to implement a language dependent search for the following scenario:
FirstSpirit CMS deploys static HTML pages to portal KM. The pages are deployed to language dependent folders named after the local. In our system we have the folders 'en', 'de', 'es' and 'fr' and one global index over all of them. On the search UI it is possible to select the language via the 'search_language' component.
Unfortunately FirstSpirit CMS creates pages for all four languages even if the page is available in English only. The other folders contain then a copy of the English version leading to the following problem: If a user submits an English search, some pages are displayed four times in the search result. This is when the page exists in English only but gets deployed due to FirstSpirit to all four subfolders.
The idea to solve this issue is to have one index for each subfolder. When a user submits a search via the search button the proper index is added to the SearchParamsMap (customized search component). This works well if the search is triggered via the search button but fails when the component is called via quicklink (e.g. /irj/portal/portal_search?SearchType=quick&QueryString=Currency). I have no idea why there is a difference and where I have to hook up in the SAP code.
Any suggestions are welcome ...
Best regards
Frank Opitz

Are you creating a portlet or a new UI page?
Portlet would be easier, but if you tie it into the existing Search Results Page, that requires UI customization and extension of our Search Results Page, so basically View replacement.
-> going the straight portlet way is much easier than the latter.
However, you mentioned you wanted to construct the querystring, makes me think you're wanting to use the search mechanism via querystring.
Look this up: it's a kb article
5.0 Search Results Page URL Format (DA_223496)
- this is only good for Portal 5.x
If you're using Portal 6.1 or higher, it may no longer be viable.

Similar Messages

Search customize field/segment in IDoc

Hi,
I've have requirement to delete a customize field ZMKOL that belong a append structure Yxxxx in VBAP. By doing that, i need to scan through all the existing IDoc interfaces that using ZMKOL.
Right now, i do have a list of inbound and outbound interfaces that using in my company. So could you please advise what is the best way for me to identify field ZMKOL is using in which interface?
Please comment.

Since ZMKOL is a custom field, to include it in an IDoc someone had to create a custom segment and extend the IDoc. The custom segments are maintained in WE31. Find out which custom segments have this field and then you'll be able to find which IDocs include these segments.
Also just do a 'where used' on the field in SE11 - this will most likely find the programs where the field is being populated for the IDocs.
Do a search on IDoc extension if you need more info.

RoboHelp Search - Customization?

I'm interested in whether RoboHelp allows customization of
the information displayed when using its Search function on a site.
A little background information...
The website I maintain was constructed through RoboHelp, and
is a collaboration of 6 projects under one server. We keep as
little content as possible on the actual Topic pages, and instead
link to content-heavy files (doc, xls, ppt, pdf, etc.) on another
part of the server.
For a large database of files, we use a coded naming
convention (ex: ABC 123 456.doc), which helps organize on the
backend. All of these similarly-named files are linked into the
Robo site, and therefore show up in the Search as a link to the
document, using the file name. This creates an issue because our
users are often unfamiliar with the naming convention, and can't
tell from the Search results which file they are looking for (even
if they know the exact title).
When a web page from the RoboHelp projects turns up in search
results, it displays as "Home Page," not "Home_Page.htm," so I'm
hoping there would be a way to make the files display another field
of information -- For example, can I edit each document's
Properties so the file
title reads in the Title field, then have the Search results
read from that? If there are no better ways of doing this, my last
resort is to rename AND relink over 500 document files.
Any assistance would be greatly appreciated.

Welcome to the forum.
Are you using RoboServer here as WebHelp Pro has different
search functionality than WebHelp?
For WebHelp, and I believe WebHelp Pro, what you get in the
search is the Topic Title and there is no option to change that.
For WebHelp perhaps ZoomSearch, described and used on my
site, would give you something closer to what you want. I don't
know whether it is possible to make that work with WebHelp Pro.

Search customization ... URGENT

gurus,
we have a potential client, the client will go for portal only if portal can do the following :-
1. for example - a search returns 10 items. the user shoule be able to print all the 10 items returned by the search. or alternatively, the user should be able to select the ones that he wants to print.
how would we do this in portal ? is there any mecahnism whereby we can bulk print and also have the ability to pick and choose from the search result.
2. for example - the search retrieved 10 items.
user chould be able to pick and choose 5 items and print them in bulk, but now these 5 items were for a particular vendor so there needs to be a tracking system that says that these 5 items were printed for vendor ABC on this date.
now when the user searches on the vendor name ABC, the search should retrieve the 5 items that were printed for this vendor.
how would this be done n portal.
is there any way to customize the search in portal and also add some flexfields kind of thing to keep the tracking for the vendors.
pls reply on this ...
these are 2 major requirements of this client.
thanx a lot
hero
null

I remember seeing the reply somewhere. Pls check the archive. I present version it is not possible.

Windows 2012 Search customization

Hello All
We are using Windows server 2012 R2 as a TS host, we control most aspects of users option via GPO, One group of users want to make use of Search option to search for files and email in a particular shared folder and mailbox, is it possible to customize the
search location? if yes, can it be achieved through GPO's?
TIA
Dev

Hi,
>>One group of users want to make use of Search option to search for files and email in a particular shared folder and mailbox, is it possible to customize the search location?
Before going further, by default, we can search in a folder and mailbox. Did you mean that we disabled the Search function for our users and then just wanted to enable the function for specific folder and mailbox? As far as I know, this can't be achieved
and group policy can't help us do this.
Best regards,
Frank Shen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Webcenter Spaces Search Customization

Hi All,
1) In Spaces PS3, the user can setup preferences where he/she can specify which services to include in the search. Is there an Administrator setting to control this site-wide (possibly without allowing users to override restrictions)?
2) Can the search be setup such that the results (People results, tag results, etc.) are restricted to the Space where the search is executed? For e.g. if I have Space A and Space B and the user performs a search for a string "adam" on Space A then the search results should only list those users with adam in their name and are members of Space A.
3) Does someone know where I can find the complete API documentation for WebCenter Framework? The doc - "Oracle Fusion Middleware Java API Reference for Oracle WebCenter 11g Release 1 (11.1.1.4.0)" - doesn't contain doco for the Search API classes like SearchServiceAPIFactory, SearchServiceAPI, SearchOptions, etc.
Thanks,
Bijesh
Edited by: Added 3)

In addition to above, I tried adding the Webcenter Search-view taskflow into a simple Webcenter Portal application.
The search returns no results. I had expected the search to be able to find the pages on the portal or the registered users at the least.
I followed the instructions here - http://download.oracle.com/docs/cd/E17904_01/webcenter.1111/e10148/jpsdg_search.htm#CBHEHJHI - to setup the Webcenter Search adapters. That didn't help either

Full-Text Search - Customize results

Hi everybody,
Does anyone know if it's possible to deactivate some topics
in order that they don't appear in the results list of the FTS?
In fact I have some topic that haven't got added value in the
case of a search.
Thanks in advance,
Bernard

Hi Bernard,
Please check the following thread which covers this issue.
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=65&catid=451&threadid =1167875&highlight_key=y&keyword1=exclude
Kind Regards
Craig

Product Search Customization

Hi Experts,
I need to enhance the product search functionality in webshop ,ie i need to search products based on Vendors , alongwith the standard search criteria.
I can u suggets me an approach to tackle ?
Also, i am not sure whether the search can be modified in CRM. i have the following perception of product data : ECC -> CRM -> Index server.
Is this perception correct?
If it is right, then can the search enhancement not be done in CRM system? Shoul it be done in the index server only?
Awaiting your replies.
Thanks and regards,
Shantanu.

Hi Ram,
Just to add to Shantanu's mail as I am his colleague.
Vendor name cannot be used as an attribute for product as it is the separate field in searh criteria.
In crm we have one relation table where we are storing VendorID and ProductID where every vendor is associated with few products.
I guess the actual search is happening on TREX based on the attributes like description, number....etc.
Vendor is the additional parameter to this search. It means there will be 2 search condition one is an attribute and second one is the vendor name.
We thought of filtering records on basis of 2 scenario. First fetch the product list from trex as per the standard way and then apply filter on the returned product list by making use of relation table in crm like in ('10001','10002',....') and vendor_name='XYZ'.
I hope this is will give you an idea about the requirement.
Need your inputs on how we can achieve this.
Thanks.
Regards,
Rupali

Customize Search User Behaviour

Hi, when inving users to an event, Is it possible to customize the query used to search users on the directory in order to allow to invite only a subset of the user ?
In our envirnment we have a flat organization of the ldap tree and all the customers belong under the same ldap subtree. I want to customize the inviting behaviour because I don't want that customer of the company "A" can invite customer of the company "B".

Andrew, there's some search customization information in the UI Customization Guide that lists the views on the search results page, and there's also a "5.0 Search Developer Guide" with this same info plus more. The Search Developer Guide is being turned into a new Search Customization QuickStart that will be a bit more usable, but that new doc isn't quite done yet.
The most straightforward approach I can think of is for you to subclass two of the existing views (off the top of my head, I think these are FollowupSearchView and GroupedResultsView) and simply add
if (userID != PT_INTRINSICS.PT_USER_GUEST) {
blocks around the code that generates the links you don't want for the Guest user.
As for opening results in a new window, note that the "Display Options" page under "My Account" has a preference for opening document results in a new window. Assuming you don't want users to have this option, in GroupedResultsViewHelper, you can always take the code path that generates the "open in a new window" link. You'll also have to handle the cases of user and community results. Other result types (i.e. Collab and portlet results) should already open in specially sized popups.

OIM 11gR2PS1 - Catalog customization -Tagging on Application Category

Hi All,
I am looking for "how to tag attribute for catalog search". I came accross scenario where i have to do catalog search based on attributes other than "Role", "Application Instance" and "Entitlement" which are provided as OOTB by default form catalog sync job.
When i read through these docs :
http://docs.oracle.com/cd/E27559_01/admin.1112/e27149/reqcat.htm
http://fusionsecurity.blogspot.in/2012/12/oim-11g-r2-ui-customization-tips-and.html?goback=.gde_98999_member_200577979
I found out that tagging capibility of OIM catalog can be used for search customization without doing any ADF in JDev or Sandbox UI customization.
But still i didnt get how to tag particular attribute through catalog administratot role.
Please provide any input which is helpful for this scenario. Any doc or blog with proper screenshot of the same will be very useful to understand.
Thanks,
RPB
Edited by: RPB25 on Jun 7, 2013 1:20 AM

If I understood your query correctly, You can login as the catalog admin into identity self service. Then search for the name of the app instance/role and click on the desired role/app instance. After that you can add your own tag in the User Defined Tags text box. Click on Apply. You can search with the specific tag you have added instead of the name of the app instance/role. It will work. Also in the API's you can pass this tag as the search criteria to identify the specific entity. Hope this helps

Customizing the Search window

Whenever I do a search in a Finder window (i.e., as opposite to the Spotlight bar) it's because I'm looking to search the contents of a folder (and, usually, its subfolders). Is there a way to by default limit the search to that folder, rather than having to switch it from "This Mac" to "[foldername]" after I start typing the search?

This is one of the dumbest features of leopard and nobody has figured out how to change it yet. Try this [hint|http://www.macosxhints.com/article.php?story=20080229204517495] for some search customization.

Basic Search Implementation

Can anyone suggest how Basic Search is implemented through Adaptive Tags in WCI.
Or is there any way how to show basic search settnigs in community page.

Found this article in my saved files, I think it's what you're looking for. It's for 5.0 Portal, but I suspect it works with later releases as well.
5.0 Search Results Page URL Format (DA_223496)
Print Page
Article ID: DA_223496 Article Type: INFO
Created: Mon, Apr 19, 2004 Updated: Mon, Apr 19, 2004
Summary
This article provides instructions on how to build a portal URL that runs a search with a given set of constraints.
More Information
This article describes how to construct a portal URL that runs a search and displays results on the portal's search results page. For example, an HTML form that includes a search box would also include these parameters (most of which would be hidden inputs in the form).
Step 1: Required parameters for all searches
Start constructing any search URL with these parameters:
Parameter
Value
Explanation
in_hi_space
SearchResult
Tells the portal to create a new SearchResult ActivitySpace.
in_hi_spaceID
<integer>
(UI Framework parameter) Leave this off the initial search URL. Links on the result page include this parameter so that the portal framework can reuse a cached ActivitySpace.
in_hi_control
searchstart
Use this on the initial search URL to indicate that it is, indeed, an initial search.
cached
false
(UI Framework parameter) Tells the portal not to reuse any previous SearchResult space. Include this on the initial search URL.
parentid
<integer>
(UI Framework parameter) The spaceID of the ActivitySpace that launched the search. Not used by the search code.
in_hi_userid
<integer>
(UI Framework parameter) Current user’s ID. Not used by the search code.
Step 2: Indicate the type of query you want to run
The initial search URL needs to specify a search query. After the user views the initial page of results, links or controls on the page let the user modify the query (for example, go to the second page) or add additional queries (“search within results” or category drill-down).
There are two types of initial query you can run:
Basic search: Specify a search string. Also, optionally, specify object types, folders, and such via URL parameters. You cannot restrict the search by the value of an arbitrary portal property. Only the properties listed on the "Banner Fields Alias" page of the Search Results Manager are searched (this list is usually Name, Description, and Full-Text Content).
Advanced search: Offers all the flexibility of the portal’s advanced search page. Specify a complete PTFilter in URL parameters: some settings might come from user form inputs, while others might come from hidden parameters. You can also specify object types, folders, and such via URL parameters.
Banner search is a special case of basic search in which certain settings (the object types to be searched) are preset by the portal. The portal uses the special value in_hi_control=bannerstart to distinguish banner search from an ordinary basic search. Ordinarily you should use in_hi_control=searchstart unless you want the special banner search behavior.
The URL parameters for basic and advanced search differ slightly.
To run a basic search use just one required parameter:
Parameter
Value
Explanation
in_tx_query
<string>
The user’s search string.
Advanced search has a long list of possible parameters. (If you do not need to constrain by property values, just use basic search and skip to the next step.)
Looking at the Filter Editor or Snapshot Query Editor in the portal will make the following table clearer. An advanced search query is the same as a filter (except for the optional settings shown in Step 3 below). There is a top-level text search string, which matches items’ name, description, or full-text content (like basic search). There is also a tree of property constraints; each grouping (or clause) in the tree consists of a set of statements, which in turn consist of a property ID, an operator (such as “contains”), and a value to match against.
The easiest way to proceed might be to build the search on the Advanced Search page or in the Snapshot Query Editor, then click through to the search page (from Advanced Search or the Content Snapshot portlet). Save the initial search result page URL and compare it with the parameters below.
Parameter
Value
Explanation
in_ra_topoperator
and or or
This is a required parameter for advanced search. Indicates whether the top-level text search string and the entire property constraint tree will be joined by an AND or an OR (corresponding to “all criteria” or “any criterion” on the advanced search page). If the text search string is empty or there is no property tree, this operator is unimportant, but the parameter must still be included.
in_tx_fulltext
<string>
The top-level text search string. Can be empty.
in_hi_totalgroups
<integer>
Number of groups (clauses) in the property constraint tree. (This is not the depth of the tree, since there could be more than one clause at a given depth.) This is always 1 for a search constructed on the Advanced Search page, since the page does not allow nested clauses.
in_ra_groupoperator_j
and or or
Boolean operator that joins statements in group j (first group is 1, not 0). For searches constructed on the Advanced Search page, there is always just one such parameter with j=1, and it is the same as in_ra_topoperator.
in_hi_revealed_j
<integer>
Number of statements in group j. Must be at least 1.
in_hi_depth_j
<integer>
Depth of clause j in the tree. For group 1 (the single group you can build on the Advanced Search page) this is 0. In general, if clause j has depth d, then clause j’s parent is the last clause to be specified with depth d-1. This means that you need to number the clauses depth-first, not breadth-first.
Example: If group 1 has depth 0, group 2 has depth 1, group 3 has depth 2, group 4 had depth 1, and group 5 has depth 2, then 1 is the parent of 2 and 4, and 2 is the parent of 3, and 4 is the parent of 5.
in_se_PropSelect_j_k
<integer>
ID of property being constrained by statement k of group j (the first statement of any group is 1, not 0), followed by a bar (|) character, and a single-digit code indicating the type of the property (which should match the property definition in the portal – this is inconvenient). The code is 3 for long, 5 for double, 7 for date, 8 for string.
in_se_OpText_j_k
<integer>
If statement k of group j constrains a text property, this is the operator (from PT_FILTEROPS) that joins the property ID and value. For example, 7 is “contains”.
in_se_OpNumber_j_k
<integer>
Same as preceding, except used for numeric properties. 1 is “equals”, 2 is “not equals”, 3 is “less than”, 4 is “greater than”, 5 is “less than or equal to”, 6 is “greater than or equal to”.
in_se_OpDate_j_k
<integer>
Same as preceding, except used for date properties. 3 is “comes before”, 4 is “comes after”.
in_tx_compareval_j_k
<string> or <double>
For statement k of group j, the comparison value. If the property being constrained is of type date, use the next item instead.
in_tx_comparedate_j_k
<long>
For statement k of group j, the comparison value if the property being constrained is of type date, expressed as the number of milliseconds since 1/1/1970 00:00:00.
Step 3: Add optional settings to the search
Finally, for either a basic or advanced search, you can use any of the parameters listed in the following table to restrict the search as described. This list does not include restrictions by portal property values; to do this you must use an advanced search.
These arguments must be preceded by a prefix. You can generally use in_hi_req_ in all cases, but refer to the text after the table for other options.
Parameter
Value
Explanation
prefix + lang
2-letter language code
Language that query is parsed in. Default is the user’s current language setting.
prefix + lbl
1 for true, 0 for false
Limit By Language. If true, results must be in the same language used to parse the query. Default is true.
prefix + apps
1 for portal, 2 for Collab, 4 for Content
Plumtree application to search. You can combine applications by bitwise-ORing the values, for example, 3 for “portal or collab”. Default is whatever applications are installed.
prefix + objtype
Any value from PT_CLASSIDS, such as 18 for cards
Portal object types to search for. Repeat multiple times to search for multiple types. You cannot restrict the types of Collaboration Server or Content Server items using URL parameters; all you can do is turn them on or off with the apps setting.
prefix + ddfolder
<integer>
ID of Knowledge Directory folder to search. Repeat this argument multiple times to search multiple folders.
prefix + adfolder
<integer>
ID of Administrative Object Directory folder to search. Repeat this argument multiple times to search multiple folders. If ddfolder and adfolder are both included, items from either the Knowledge Directory or Administrative Object Directory can be returned.
prefix + subfolders
1 for true, 0 for false
If true, subfolders of any folder specified by ddfolder or adfolder are included as well. Default is true.
prefix + community
<integer>
ID of community to search.
prefix + spell
1 for true, 0 for false
If true, use the Search Server’s spell correction capabilities to try to find matches for any terms it does not recognize.
prefix + bbs
1 for true, 0 for false
If true, and if the query string matches a Best Bet trigger string, rank the Best Bet’s targets at the top of the result list. Applies only to basic search, not advanced search.
prefix + thesaurus
1 for true, 0 for false
If true, use the Search Server’s thesaurus to expand the query string(s).
prefix + portletid
<integer>
For Content Server items (only), restricts the search to items associated with the supplied portlet ID.
A note on prefixes: As stated above, ordinarily you can prefix any of these arguments with in_hi_req_ and things will be fine. However, the portal UI framework sometimes forces checkboxes and radio buttons to have names starting with in_cb or in_ra, so you can also use in_cb_req_ or in_ra_req_ in those cases.
Also, the prefix in_hi_opt_, in combination with the in_se_sel_ family of arguments, lets you add drop-down selectors to search forms that cause conditional behavior depending on the selected item. The rule is:
If any parameter starting with in_se_sel_ appears, take its value (call it V).
Look for any other parameters starting with in_hi_opt_V_, where V is the value you just located. Apply those settings to the search (using the above table) in addition to any in_hi_req_ prefixed settings.
See the examples below.
Examples
Here is a search form that implements very basic search for portal documents:
<form method="post" action="http://portal.plumtree.com/portal/server.pt">
<input type="hidden" name="in_hi_space" value="SearchResult"/>
<input type="hidden" name="in_hi_control" value="searchstart"/>
<input type="hidden" name="cached" value="false"/>
<input type="hidden" name="in_hi_req_apps" value="1"/>
<input type="hidden" name="in_hi_req_objtype" value="18"/>
Search: <input type="text" name="in_tx_query"/>
<input type="submit" value=">>"/>
</form>
Here is a search form that implements an advanced search for portal documents. It displays two search boxes. One matches text in the name, description, or content of the document, and the other matches the Author property. In addition, the Keywords property is implicitly constrained to contain the text ‘plumtree’.
<form method="post" action="http://portal.plumtree.com/portal/server.pt">
<input type="hidden" name="in_hi_space" value="SearchResult"/>
<input type="hidden" name="in_hi_control" value="searchstart"/>
<input type="hidden" name="cached" value="false"/>
<input type="hidden" name="in_hi_req_apps" value="1"/>
<input type="hidden" name="in_hi_req_objtype" value="18"/>
Search for: <input type="text" name="in_tx_fulltext"/>
<input type="hidden" name="in_ra_topoperator" value="and"/>
<input type="hidden" name="in_hi_totalgroups" value="1"/>
<input type="hidden" name="in_ra_groupoperator_1" value="and"/>
<input type="hidden" name="in_hi_revealed_1" value="2"/>
<input type="hidden" name="in_hi_depth_1" value="0"/>


<input type="hidden" name="in_se_PropSelect_1_1" value="103|8"/>
<input type="hidden" name="in_se_OpText_1_1" value="7"/>
where the Author contains <input type="text" name="in_tx_compareval_1_1"/>


<input type="hidden" name="in_se_PropSelect_1_2" value="101|8"/>
<input type="hidden" name="in_se_OpText_1_2" value="7"/>
<input type="hidden" name="in_tx_compareval_1_2" value="plumtree"/>
<input type="submit" value=">>"/>
</form>
Here is an example of using drop-down selectors in a search form. It is a bit contrived, but this form gives the users the option of searching “Marketing” (documents under folder 123), “Sales” (documents under folder 456), “Communities” (search for any community the user has access to), or “Collab projects” (items within Collaboration Server projects).
<form method="get" action="http://portal.plumtree.com/portal/server.pt">
<input type="hidden" name="in_hi_space" value="SearchResult"/>
<input type="hidden" name="in_hi_control" value="searchstart"/>
<input type="hidden" name="cached" value="false"/>

<input type="hidden" name="in_hi_opt_marketing_apps" value="1"/>
<input type="hidden" name="in_hi_opt_marketing_objtype" value="18"/>
<input type="hidden" name="in_hi_opt_marketing_ddfolder" value="123"/>

<input type="hidden" name="in_hi_opt_sales_apps" value="1"/>
<input type="hidden" name="in_hi_opt_sales_objtype" value="18"/>
<input type="hidden" name="in_hi_opt_sales_ddfolder" value="456"/>

<input type="hidden" name="in_hi_opt_communities_apps" value="1"/>
<input type="hidden" name="in_hi_opt_communities_objtype" value="512"/>

<input type="hidden" name="in_hi_opt_collab_apps" value="2"/>
Search..
<select name="in_se_sel_1">
<option value="marketing">Marketing folder</option>
<option value="sales">Sales folder</option>
<option value="communities">All communities</option>
<option value="collab">All Collab projects</option>
</select>
for: <input type="text" name="in_tx_query"/>
<input type="submit" value=">>"/>
</form>
The information in this article is related to:
Foundation (Portal) versions: 5.0.x
Search Server versions: 5.0
Other Products:
Topics: Search
Related Articles: 5.0 Search Results Page
Search Syntax in Plumtree Corporate Portal
Keywords: search,customization,link,clickthrough,url parameters

SharePoint Search vs Autonomy

Hi,
We are evaluating SharePoint Search vs Autonomy search. Has any body experience on any of those? I understand that SharePoint does not support wildcard search or contex/conceptual search (VB is Visual Basic). I also saw that we can enable wildcard search by building a custom search interface.
Any thoughts or inputs on the comparision is greatly appreciated.
Regards,
Raj

Hello I have worked on both SharePoint Search and Autonomy Search (IDOL). I can say that before SharePoint 2013, IDOL had edge over FAST search in SharePoint 2010, but with the integration of FAST search in SharePoint 2013 it becomes much organized and easy
to configure with excellent out of box UI that has "hover panel" which adds much more flexibility to add actions.
If you are looking at complex search cases and intelligent processing of content which should help in finding more meaningful content over the other simillar contents then go for IDOL, otherwise go for SharePoint as it has most of the features OOB.
Another practicle conideration for selecting the search product is inhouse technical ability. Autonomy has great flexibility in customization which means it has bigger learning curve compared to SharePoint 2013.
Presenting you few points below which may help you selecting correct product for your purpose
Feature
Autonomy(IDOL)
SharePoint 2013
(FAST Search)
Customization
Heavily supported and has many tools to do it
It provides most out of the box options. However it can be customized using custom search interface.
Wildcard search
Supported with customization
Supported with customization
External DB/Store Support
Available with wide range of connectors
Possible with BCP or third part, added cost.
Ranking
Have to customize.
Extremely efficient
Content processing
Meaning based computing
Linguistic Analysis

Save button on QBE report not working

Hi,
I included a save button in my QBE cutomization form. it saves everything except for the values I enter for my actual field parameters. The save button works in all other reports (SQL Query, Qurey Wizard based)
is that a bug or am I doing soemthing wrong? Please help with this one.
Thanks, Maike!!

Hi,
thanks for your reply - but I wasn't trying to save the record but really the search customization parameters e. g. like a date value to search for records for that certain date.
And that does not seem to be saved - only the columns I want to display or by what field I want to order.
Please let me know if that should work this way. Thanks, Maike.

Can I add more than one horizontal separator to the PanelUI (the new panel menu)

Steps:
1. Click the new panel menu button (hamburger)
2. Click Customize
3. On the left, drag "Separator (for panel menu)" from "Additional Tools and Features" to the panel on the right. A horizontal separator appears. "Separator (for panel menu)" no longer appears in the "Additional Tools and Features".
I can add many "Separator" (vertical separator) to toolbars, but it appears I can only add one "Separator (for panel menu)" (horizontal separator) to the panel.
I would like to add additional horizontal separators to the panel. Is there a way to do that?
Firefox version: 33.1.1

Yes, I do have Classic Theme Restorer installed (I love it!), but missed these customization nuances. After reading more threads, searching, and reviewing prefs.js, I saw the ctraddon_puib_separator.
A while back, I had problems with vertical separators, specifically with AIOS, and had also looked for horizontal separators. The solution at that time was customizableui-special-separator{d}, where d was a unique digit.
I always found the customization menu to be difficult to use, especially if a buttons addon was installed, mainly because it was unordered. I recently installed Sort and Search Customization Dialog and it has made a world of difference.
I just started changing my FF ways and using the new menu. I wanted to divide up the menu into sections or activities. On top I'd have a row of user tools like history, bookmarks, then a divider and have a row of customization tools, another divider and development tools. The divider which provides the visual separation and grouping is really nice. I hope FF adopts them. I'll take my questions and feedback to the Classic Theme Restorer Forum thread shown on the addon page:
https://addons.mozilla.org/en-US/firefox/addon/classicthemerestorer
Thank you.

Search Customization

Similar Messages

Maybe you are looking for