Search Results Pattern Set Version 2.0.0.0Print this Page
Transactional Search and Results Pattern Group

Description Return to Top

Search results are presented after a user runs a search. (See the Search Pattern set for issues related to the appropriate form and location of the search interface.)

There are two major aspects to search results:

  • Presentation: The form of presentation depends primarily on the Work Area model. Search results can appear in the local area and in a dialog box.
  • Actions: Any action that can be taken on a row in a table can be taken on a row in a search results table. For guidance on how the user interface (UI) should behave when those actions are performed, see the design patterns for those actions, such as Add Existing Object, Create, Editing Objects, and Details on Demand: Drill-Down Details.

Pattern Set Decision Table Return to Top
  Local Area:
No Tabs Work Area

Local Area:
Dynamic Tabs Work Area

 Dialog Box

Is the user working on an incomplete task when searching?

No

No

Yes

Are search results limited to 50 percent of the page width or less?

No

No

Yes
Does the user want to skip directly to an edit or view mode of a transaction if the search yields only a single result? Yes
(see Shortcutting
pattern)		 Yes
(see Shortcutting
pattern)		 Yes
(see Shortcutting
pattern)

Matching Search and Results Return to Top

The following table shows which search and search results combinations are valid:
  Local Area:
No Tabs Work Area		 Local Area:
Dynamic Tabs Work Area		 Dialog Box
Local Area: Quick Search Yes Yes No
Local Area: Multiple Criteria Yes Yes No

Taking Actions on Search Results Return to Top

Most actions taken on search results are initiated from a table toolbar menu that is part of the search results table. Users can access actions by using menus or toolbar icon buttons. The toolbar icon buttons, from left to right, are Create, Edit, Duplicate, and Delete. Next is the [Show/Hide] Query by Example icon button, followed by the Detach icon button. See the Table Usage guidelines for additional information.

The Query by Example (QBE) bar can be enabled on search results tables. This bar is described in the Table Elements Usage guideline. The interaction between search and QBE fields is described in the Query by Example design pattern.



Relevant Patterns

The following design patterns are commonly used with search results tables:

Also see the Common Table Actions usage guideline .


Related Patterns Return to Top
Transactional Search Search is limited to one business object and provides a single view of current data pulled from live tables.
Shortcutting Shortcutting involves skipping directly to a record when only one result is found when conducting a search.

Related Guidelines Return to Top
Table Usage guidelines Guidelines for designing tables and using the Application Development Framework (ADF) Table component
Work Area guidelines Detailed discussion of work areas and their design, including tabbing and object models
 
About Oracle | Legal Notices | Terms of Use | Your Privacy Rights