Flexible and extensible combination user interfaces

• US 7,747,959 B2
• Filed: 12/17/2004
• Issued: 06/29/2010
• Est. Priority Date: 12/17/2004
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Adelberg, Bradley Scott, Keller, Carl Paul, Flexer, Michael Eric, Malden, Matthew S.
• Primary Examiner(s): Pesin; Boris
• Application Number:
  US11/015,673
• Publication Number:
  US 20070113191A1
• Time in Patent Office: 2,020 Days
• Field of Search: 715/764, 709/206, 709/217
• US Class Current: 715/764
• CPC Class Codes: G06F 3/0481 based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

Flexible and extensible combination user interfaces are described. Combination user interfaces combine task-based and deductive user interfaces in such a manner that complex user interactions can be facilitated using a more meaningful and intuitive user interface than would have been possible using task-based or deductive user interfaces exclusively. The described combination user interfaces are flexible and extensible. They are flexible in that users can work on multiple tasks or switch between tasks without first needing to complete another task. They are extensible in that they can be extended to add, modify, or remove tasks or portions of tasks. User interfaces can be extended by manipulating metadata associated with the user interfaces. The combination user interface can be combined with an Inbox concept to facilitate saving and assigning tasks. The Inbox represents a work queue for a user.

Claims

1. A computer system the computer system comprising:

a first data storage for storing a state of a task of a user, wherein the task is a unit of activity that can be performed as a sequence of multiple steps, and

a goal comprises the task and a second task;

a second data storage for storing metadata, the metadata identifying elements of a user interface and indicating properties relating to the elements, the metadata enabling flexibility and extensibility of the user interface through additions and modifications of the metadata, wherein

the metadata comprises a unit of metadata defining a context menu associated with an inbox applet component;

the inbox applet component, wherein the inbox applet component is configured to, when requested, provide the user interface, wherein

the user interface has an inbox that enables the user to manipulate the task,

the user interface is generated from the second data storage, and

the inbox comprises items of the first data storage; and

logic configured to provide automatic behavior triggered by the task wherein the automatic behavior includes enforcement of a business rule.

2. The computer system of claim 1 wherein:

the inbox provides an indication of tasks for the user;

the foal is selected using a menu bar user interface element;

the task is selected using a screen tab user interface element; and

a first task-based interface is presented in response to selecting the task, wherein,

the first task-based interface and a second task-based interface both use a shared page from among a set of multiple pages,

the first task-based interface presents a first pane and a second page in an order representing the sequence,

navigating between the first page and the second pane causes data entered into the first pare to be validated and saved in a local data context,

the data saved in the local data context is not shared until the task is completed, and

returning to the first pare causes the data to be retrieved.

3. The computer system of claim 1, wherein the user can transfer the task to another user.

4. The computer system of claim 1 wherein the user interface provides an enterprise software application.

5. The computer system of claim 1 wherein information of the inbox is stored in a relational database.

6. The computer system of claim 1 wherein information of the inbox is stored in an extensible markup language.

7. The computer system of claim 1 wherein an application for displaying information of the inbox is defined in the metadata.

8. The computer system of claim 1 wherein the inbox provides an indication of unassigned tasks.

9. The computer system of claim 1 wherein the inbox receives an action from the user relating to a task.

10. The computer system of claim 1 wherein the action is to mark the task as done.

11. The computer system of claim 1 wherein an available action for a task is based on information contained in the task.

12. A method performed by a computing system to, the method comprising:

retrieving metadata from a database, the metadata identifying user interface elements and indicating properties relating to the user interface elements, wherein the database enables flexibility and extensibility through additions to and modifications of the metadata;

retrieving a task from a unit of storage, wherein

the task is a unit of activity that can be performed as a sequence of multiple steps, and

a goal comprises the task and a second task;

providing a user interface that enables a user to manipulate the task, the user interface generated from the retrieved metadata based on an indicated task, the user interface including the inbox, wherein

the user interface comprises the user interface elements, and

the metadata comprises a unit of metadata defining a context menu associated with an inbox applet component;

providing automatic behavior triggered by the task, wherein the automatic behavior comprises enforcement of the business rule; and

storing the task in the unit of storage after the user has manipulated the task.

13. The method of claim 12 wherein the retrieving includes retrieving from a relational database.

14. The method of claim 12 wherein the retrieving includes retrieving from an extensible markup language.

15. A system the system comprising:

a unit of storage;

an inbox applet component, stored in the unit of storage, that retrieves a definition for a user interface from metadata, wherein

the metadata defines the user interface, and

the metadata comprises a unit of metadata for defining a context menu associated with the inbox applet component;

an inbox commands component that receives commands from a user in relation to an inbox and provides the commands to the inbox applet component;

a component that receives a request from the inbox applet component, the request relating to information contained in a database comprising information displayed in the inbox with respect to a task, wherein the task is a unit of activity that can be performed as a sequence of multiple steps, and

a goal comprises the task and a second task;

logic configured to provide automatic behavior triggered by the task, wherein the automatic behavior includes enforcement of a business rule.

16. The system of claim 15 wherein the component that receives a request from the inbox applet component abstracts a data provider.

17. The system of claim 16 wherein the data provider retrieves data in a private data context, the private data context identifying data that is not shared with other users.

18. The system of claim 16 wherein the data provider retrieves data in a public data context, the public data context identifying data that is shared with other users.

19. The system of claim 15 wherein the metadata is stored in a relational database.

20. The system of claim 15 wherein the metadata is stored using an extensible markup language.

21. A computer program product in a unit of storage configured to perform a method, the method comprising:

retrieving a definition for a user interface from metadata stored in a unit of storage; and

providing the user interface based on the definition, wherein the user interface comprises an inbox, the inbox comprising a task for a user, wherein

the task is a unit of activity that can be performed as a sequence of multiple steps, and

a goal comprises the task and a second task,

the user interface enables the user to manipulate the task,

the metadata comprises a unit of metadata defining a context menu associated with the inbox;

providing automatic behavior triggered by the task, wherein the automatic behavior includes enforcement of a business rule; and

storing the task in the unit of storage after the user has manipulated the task.