Search Sources

Select the appropriate subsystem.

Type a name for this viewer.

Type a title for this viewer. This may be presented to the end-user by a Presentation Style.

The title supports multiple languages.

Type the appropriate external key.

For advanced users only, type the appropriate SQL hint. The syntax is the name of the hint, like FIRST_ROWS.

The hint will be inserted into the SQL-query; using the appropriate hint may help speed up query execution.

Type the name of the appropriate database procedure to use a special access control, if you want to extend the default access control. Note: You should use this carefully, as controlled security model may be set aside.

The following signature must be used for the database procedure:

PROCEDURE <package>.<procedure name> (
  site_id in number,
  user_id in number,
  reference_path in varchar2,
  result out
);

The returned result must be an SQL fragment which fits into the SQL WHERE clause generated by the Viewer. For example, the function could return

or oi1.owner_id = 125

and the query would then be

...
and (oi1.owner_id = <userid> or ((oi1.acl_guid is null or oi1.owner_id = 125 
or oi1.acl_guid in (select v_acl.acl_guid from v_acl)
...

Select the Presentation style you want to use to format the output.

Select the Styleset you want to apply. If set, this will override the styleset defined on the Presentation style.

For Oracle Portal portlets only, if you want to override the Oracle Portal portlet header, select the Portlet header styleset here.

Note: You must enable <show Portlet Header> for the Oracle Portal page region in which the portlet is placed. The HTML code for the portlet header styleset must only contain actions (e.g. ABOUT) that are selected for the Oracle Portal page region.

Select the target page to use for link to documents with text content.

Select the target page to use for link to documents with file or url content.

A function used as callback from Forms when adding new documents or editing existing documents initiated from the viewer.

You can use this property to avoid page redirect upon save from form. The parameter passed to the callback function is a json object with the properties action and documentId. The callback function could for example reload the search source.

Select the target page to use for the “show more” link. Please note that the target definition should have a parameter named p_search_id as Parameter1.

To reuse a single target page for multiple “show more” pages, select the search source you want to display on the target page.

Type the number of rows that you want to extract at a time. The default value is 10.

Type the row number from which you want to display the result set. The default value is 1.

Type the maximum number of documents that you want to extract. The default value is 100.

Type the time in minutes for which you want to keep content in the cache.

Select this check box to display the total number rows on the status line.

Select this check box to use the targets defined on this Viewer rather than the target selector mechanism.

Select this check box to use the target defined in the Target for text property for all links to documents, disregarding the content type.

Select this check box to use a session save on all the dynamic parameters. If these values are not in the URL, this property allows iKnowBase to use the saved values. e.g sortinfo.

If you do not save the session variables, no content appears when you enter the page without the necessary dynamic parameters specified on the portlet.

Select this check box to display the title of the portlet if the search finds no documents.

Select this check box to display the quick links within the header section of the viewer.

Select this check box to display the quick links even it mandatory attributes are not set.

Select this check box to print the portlet decoration that surrounds the content in a portlet.

Select this check box to build the search form using the HTML-based generator. You must enter the appropriate HTML code on the HTML form tab.

If you don�t select this check box, the limited, rule based generator is used.

Select this check box to save the search statistics of a user.

When you select this check box, the search statistics of the user are logged in the LOG_SEARCH_VALUES table.

Select this check box to use the search source as a list for selection of documents or dimension values. This list may be connected to a form as a new selector of values.

Select this check box to allow a user to manually add attributes to the search criteria.

When this is checked, iKnowBase will display a drop down list of all searchable attributes in the search form; selecting one will add that attribute to the search form.

Delete the parameter by clicking the icon.

Displays the names of the selected attributes to use as conditions for the Search source.

You can for debugging reasons disable attributes.

Used for performance reasons for advanced users. Will generate a SQL with either IN or EXISTS.

Select the appropriate conditions for the selected attributes. The conditions depend on the type of attribute.

Note: You cannot select a condition for parameters.

Select or enter the appropriate values for the selected attributes. Available options depends on the attribute/parameter type.

Applicable to SQL parameters only when the parameter is defined with an attribute.

Choose how you want to traverse the document structure. You can choose between :

No traversal: will not retrieve any subdocuments

Traverse down by using a connect-by clause: will fetch all subdocuments for every documents retrieved. It will use the same presentation style as defined on the main viewer definition. When selected, you can enter the number of levels you want to traverse.

Traverse up by using a connect-by clause: will fetch all documents above for every documents retrieved. It will use the same presentation style as defined on the main viewer definition. Suitable for viewers showing only one document where you want to see the top levels. When selected, you can enter the number of levels you want to traverse.

Traverse by using search sources: For each document it will run a new viewer. This is not as efficient (performance) as the above methods, but gives you the flexibility of defining separate conditions and presentation style for each level.

Type the level for the extraction source. Level 1 specifies first level, but you may specify extraction sources that traverse further on level 2 documents, etc.

Select the appropriate Search source as the base for the extraction of subdocuments. You can vary the style and layout on different levels.

To enable the expand/collapse functionality for the subdocuments, click Yes. To display the subdocuments directly, click No.

Enter the reference to the icon to be used to expand the list of subdocuments.

Note: You must click Yes in the Expand Collapse list.

Enter the reference to the icon to be used to collapse the list of subdocuments.

Note: You must click Yes in the Expand Collapse list.

Select the appropriate dynamic parameter, this must be a document ID, to pass to the Quick link in order to be able to create a subdocument.

Select this check box to add the respective Quick link to the Viewer.

Type the title that to use for the Quick link. If multiple languages are supported in the solution, each language displays a box, where you can type the title that appears. When you click in the Title box, the language box appears. The language code is placed behind the box.

Type the font class to use for the Quick link text.

Type the path of the image to use for the quick link.

Select this check box to display both text and image.

Type the sorting IDs to sort the quick links that you select.

Displays the description of each quick link.

Type an identifier for the label.

Type the text labels that you want to use in the page. If multiple languages are supported in the solution, each language displays a box, in which you can type the display form name. When you place the cursor in the Text field, the language box appears. The language code is placed behind the field.

Displays the selected attributes that makes up the search criteria for the search source.

Select the appropriate styles for the input fields of the search criteria.

Available options for lists of values are radio buttons, check boxes, select box, multiselect box, or <default>. If you define Valid values for a dimension attribute, the input field for this attribute is treated as a list of values.

Type the lengths of the input fields of the search criteria.

Select the default conditions for the search criteria.

Select the conditions which will be available for selection in the search form.

If none is selected, all will be available.

Select the check box to restrict the user from selecting a condition for the given search criterion in the search form. In this case the value given in the Condition will be used.

Note: If you lock the condition, the automatically created HTML code on the HTML form tab will not include the iKnowBase condition-tag. You are able to include it yourself though, and thereby override this property.

Select the values which will be available for selection in the search form.

Applicable to value list and dimension attributes.

Type the label you want to use for the dropdown used to manual add attributes to the search criteria. Available when the Dynamic attribute selector property is selected.

If multiple languages are supported in the solution, each language displays a box, in which you can type the prompt. The language code is placed behind the field.

Enter the style class to use for the label for the dropdown used to manual add attributes to the search criteria. Available when the Dynamic attribute selector property is selected.

Enter the style class to use for the dropdown used to manual add attributes to the search criteria. Available when the Dynamic attribute selector property is selected.

Enter the style class to use for the label for the manually added search criterion. Available when the Dynamic attribute selector property is selected.

Enter the style class to use for the value input field for the manually added search criterion. Available when the Dynamic attribute selector property is selected.

Enter the style class to use for the condition field for the manually added search criterion. Available when the Dynamic attribute selector property is selected.

Enter prompt and styles for the selected attributes

Displays the names of the selected filter attributes.

Type the labels for the respective filter attributes.

If multiple languages are supported in the solution, each language displays a box, in which you can type the prompt. When you place the cursor in the Prompt field, the language box appears. The language code is placed behind the field.

Enter the style classes to use for the labels of the respective filter attributes.

Enter the style classes to use for value input fields of the respective filter attributes.

Enter the style classes to use for the condition fields of the respective filter attributes.

Type the HTML template code.

Note: Use the action buttons Create new template or Update to automatically create or update HTML template code.

A list of available parameters and their IDs available for use in the HTML template code.

Select this checkbox to make documents at the upper most level selectable. Applicable if you have defined the search source with traverse features, e.g. to extract and display subdocuments on one or more sublevels.

Select this check box to always display a radio button, even though the calling dialogue accepts more than one return value.

Select which value to return; typically document ID or dimension ID. Available options are decided by the Presentation style associated with the Search source.

The selection must correspond to the value expected from the calling dialogue. If the calling dialogue is a related document or image attribute on a form, a document ID must be returned. If the calling dialogue is a dimension attribute on a form, a dimension ID must be returned.

Type the JavaScript code that runs when the end user clicks the radio button in the pick list.

Rather than typing your own code, you can use two pre-defined actions:

• StartReturnFromPickList (): This can be used where you use the pick list from an attribute field on a Form. It will return the selected value back to the calling dialogue.
• ReturnToEditor (): This can be used where you use the pick list from a TinyMCE field on a Form.

Type your own JavaScript code if needed, could for example be run using the button.

Enter the HTML code to be generated at the end of the page, after the extracted data. Examples can be a button which returns the selected values.