| Transactional Search and Results Pattern Group |
| Shortcutting | Version 2.0.0.0 |
||
|
|||
| Description |  |
| Use the Shortcutting pattern only when the user has no need to review the search results in a table format where the results can be acted upon (for example, Create, Edit, Delete). The Shortcutting pattern is appropriate when the user is referencing only existing objects in the database, and the user can search on a unique identifier, such as a purchase order number, to return only one result. |
| Pattern Decision Table | |
| Shortcutting | Search Results | |
| Does the user need to take actions on the results that appear in a search results table (for example, Create, Edit, Delete)? | No | Yes |
| Does the user need to search for records that may not exist? | No | Yes |
| Does the user need to see the search results regardless of the number returned before deciding on what action to take? | No | Yes |
| If the search resulted in only one result, should the user go straight to the object page to view or edit it, skipping the results table? | Yes | No |
| Is only one result returned? | Yes (Required) | One or more results returned |
| Display Options of Shortcutting | |
| Result Page Display |
After shortcutting to a single object, the appearance of the resulting object details page (for example, refresh the local area or launch a new dynamic tab) depends on the Work Area Model. Likewise, the navigation options available to users once they are done viewing or editing the object in the resulting page depends on the Work Area Model. See the Work Area Model guidelines for interaction details. If the user has permission to edit the shortcutting result, an editable page appears. For an example, see the Page Edit design pattern. If the user does not have permission to edit the shortcutting result, a view-only page appears. For an example, see the Drill-Down Details design pattern. |
| Pattern Sample |
| Shortcutting to an Editable Page |
This example uses the Local Area Search and Page Edit design patterns and the No Tabs work area model. The user performs a search that yields a single result. |
 |
| Figure 1. A search yielding only one result |
| The search results table is skipped and the user is taken directly an editable object details page. |
 |
| Figure 2. Editable object details page |
| Shortcutting to a View-Only Page |
This example uses the Local Area Search and Drill-Down Details design patterns and the No Tabs work area model. The user performs a search that yields a single result. |
|
| Figure 3. A search that yields only a single result |
| The search results table is skipped and the user is taken directly to a read-only object details page. |
 |
| Figure 4. A read-only object details page |
| Related Patterns | |
| Transactional Search | User interface for searching for a single object |
| Search Results | The option to use if shortcutting is not appropriate |
| Editing Objects | Patterns that enable users to edit objects |
| Detail on Demand | Patterns that enable users to view objects |
| Related Guidelines | |
| Search and Query Usage guideline | Usage guideline for the query component |