Oracle International Corporation

Harris Kravatz

Daniel M Schwartz

Arin Bhowmick

Aylin Uysal

Roy A Selig

Sally Stratton Baggett

Jeremy Ashley

Samuel Ting

Michael Remington

Katie Candland

Allison Farrell

A set of characteristics is received in response to a questionnaire. Using the characteristics, various tasks are identified as requiring or not requiring user input because of the applicability to the customer. An associated task owner is determined for a subset of tasks. In response to receiving a selection of a selectable dependency indication associated with a first task, displaying task dependency data associated with the first task is displayed, the task dependency data including a set of tasks on which the first task depends for completion, a set of tasks that depend on the first task for completion, and for each of these dependent tasks, an associated task owner and a task status. A task list that indicates tasks needing to be completed is presented to the user. Software is installed according to the task list.

Installing software using a set of characteristics and a task list

Embodiments described herein provide various features for a unified and simplified user experience. A first feature (or set of features) provides icons for launching or accessing applications and business flows. A second feature provides a unified menu system including an icon bar with thumbnails of a selected icon arranged adjacent to the icon bar. A third feature provides a framework for a menu that can expose application objects from diverse sources.

System for navigation in a computer user interface

In various embodiments, techniques for communicating and visualizing dependencies between a large number of flows are provided. One or more user interfaces can be generated that enable users to interact with information needed to complete each tasks in an ordered or unordered listing of tasks. In some aspects, elements of these user interfaces can including functionality enabling users to interact with each tasks, navigate to information needed to complete each task. In another aspect, one or more styles of presenting information is provided that facilitates navigation to dependency information for each task in a more useful manner. In further aspects, elements of these user interfaces can visually communicate the above functionality and dependency information as well as additional information about each tasks, such as status information, ownership information, or providing an audit trail.

Mechanism to communicate and visualize dependencies between a large number of flows in software

Growing community of inventors

Danville, CA, United States of America

Harris Kravatz