|Recent Items Guidelines|
|Recent Items is an Oracle Fusion Applications global area menu that enables authenticated users to return to recently visited business flows or objects.|
|Description and Purpose|
|Intrawork area navigation, exemplified by local area transitions, is commonly perceived as page navigation. However, accessing flows and objects within a work area does not generate a new URL. Instead, the local area flow on the page may update to reflect a different flow or object, but the URL remains the same. The result is that the browser Back button and History feature do not map to what is generally perceived as page navigation.
The Recent Items menu enables users to return to flows across work areas that have been recently accessed, usually within, but not limited to, a single session.
|Figure 1. Manage Departments captured in the Recent Items menu|
|Example of Recent Items|
|Cooper is a manager using Oracle Fusion iRecruitment to find candidates for his organization. Cooper finds the perfect candidate but is interrupted by an employee who needs an expense report approved immediately. After navigating to the Expenses work area to approve the expense report, he can use Recent Items to return to the candidate in iRecruitment.|
|Recent Items Flows|
Recent Items does not track all flows. The flows that can and cannot be captured are limited both by their dependencies and whether or not the task flow appears in the main task area.
Flows that can be added to Recent Items are:
Flows that cannot be added to Recent Items are:
|Context vs. State|
Context is typically set at the beginning of a flow. For example, when a business object is added to Recent Items, it should include both the context of the activity (for example, create, view, edit), as well as the object identifier (for example, Customer ACME Corp., Employee John Smith).
State is something that changes during the course of the flow (for example, results in a search and traversing through master records in a master/detail layout). Recent Items is not intended to maintain the state of the flow. For example, the results of a particular search will not be part of Recent Items context. The native saved search capabilities are sufficient to support that requirement (see Search and Query Usage Guidelines for details). Instead, the Recent Item will only register the entry point of the search flow in this case.
|Launching a Flow from Recent Items|
|To launch a flow from Recent Items, select the Recent Items menu, and then select the flow that you want launched in the main area of the UI Shell.|
|Tab Model Navigation Through Recent Items|
|Interwork Area Navigation Through Recent Items|
The business flows or objects captured in Recent Items may belong to a different work area that navigates the user away from the current work area. The following outcomes describe how the navigation framework handles each type of navigation.
When navigating to a No-tab work area, the selected Recent Item is the flow loaded upon entry. When navigating to a Dynamic Tab work area, the Overview tab for that work area opens, followed by the selected Recent Item in a new tab (which is brought into focus). When navigating to a Static Tab work area, all static tabs are loaded upon entry, and the tab associated with the Recent Item selection comes into focus.
|Navigating from Unsaved Transactions|
Navigating away from an incomplete task flow from a Recent Items selection should fire the same unsaved data warning and necessary validations as any other link or button on the page (see Save Model guidelines for details).