ACTIVE BUSINESS CLIENT

• US 20090083643A1
• Filed: 02/19/2008
• Published: 03/26/2009
• Est. Priority Date: 09/24/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Beringer, Joerg
• Granted Patent: US 8,127,237 B2
• Time in Patent Office: Days
• US Class Current: 715/762
• CPC Class Codes: G06F 13/4027 using bus bridges G06F13/4022 takes precedence
• 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 8/38 for implementing user interfaces
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

Methods and apparatuses enable generation of and consumption of business context data. A server generates business context data that describes a resource, a view, and actionable context data related to a business scenario. The business context data is not specific to any particular UI capability of the client device, and may include little or no UI information. The server transmits the business context data to a client device that has an active client. The active client identifies one or more UI capabilities of the client device and generates a UI component based on the business scenario and the UI capabilities. The UI component enables functionality in the client device related to execution of the actionable context data. In one embodiment, the active client enables predictive deployment of services on the client device based on an understanding of the business scenario.

Claims

1. A method comprising:

receiving, at a client device from a server, business context data that describes a resource, a view, and actionable context data related to a business scenario;

identifying user interface capabilities of the client device; and

generating a user interface (UI) component based on the business scenario and the identified UI capabilities, the UI component enabling functionality related to the actionable context data on the client device.

2. The method of claim 1, wherein receiving the business context data that describes the resource comprises:

receiving business context data that describes one or more of a business object, a document, a form, a report, or an identified individual.

3. The method of claim 1, wherein receiving the business context data that describes the view comprises:

receiving business context data that describes one or more of a data layout, an association of a graphic with a function, or a text field to display.

4. The method of claim 1, wherein receiving the business context data that describes the actionable context data comprises:

receiving business context data that describes an activity of a workflow.

5. The method of claim 1, wherein receiving the business context data related to the business scenario comprises:

receiving a description of the business scenario as metadata associated with the data describing the resource, the view, and the actionable context data.

6. The method of claim 1, wherein receiving the business context data comprises:

receiving data of a model layer of a model-view-controller (MVC) architecture; and

wherein identifying the user interface capabilities of the client device and generating the UI component comprise;

implementing the controller and view layers of the MVC architecture.

7. The method of claim 1, further comprising:

generating a request for a contextual action based on a context of the business context data.

8. The method of claim 1, further comprising:

predictively deploying a service based on detecting a disconnect condition.

9. An article of manufacture comprising a machine readable medium having content stored thereon to provide instructions to cause a machine to perform operations including:

receiving, at a client device from a server, business context data that describes a resource, a view, and actionable context data related to a business scenario;

identifying user interface capabilities of the client device; and

generating a user interface (UI) component based on the business scenario and the identified UI capabilities, the UI component enabling functionality related to the actionable context data on the client device.

10. The article of manufacture of claim 9, wherein the content to provide instructions for receiving the business context data that describes the resource comprises content to provide instructions for

receiving business context data that describes one or more of a business object, a document, a form, a report, or an identified individual.

11. The article of manufacture of claim 9, wherein the content to provide instructions for receiving the business context data that describes the actionable context data comprises content to provide instructions for

receiving business context data that describes an activity of a workflow.

12. The article of manufacture of claim 9, wherein the content to provide instructions for receiving the business context data comprises content to provide instructions for

receiving a meta object having an aggregation of data elements from multiple backend systems.

13. The article of manufacture of claim 12, wherein the content to provide instructions for receiving the meta object having the aggregation of data elements from multiple backend systems further comprises content to provide instructions for

receiving the meta object having a bound data component, where the binding links the data component to one of the multiple backend systems.

14. A client device comprising:

a network interface to connect to a server that provides a business context data stream; and

an active business client to receive from the server a data stream having business context data that describes a resource, a view, and actionable context data related to a business scenario, and to identify user interface capabilities of the client device, the active business client having

a controller layer to process the business context data; and

a view layer to generate a user interface (UI) component based on the business scenario and the identified UI capabilities, and to render the UI component in a UI to enable functionality related to the actionable context data on the client device.

15. The client device of claim 14, the active business client to further determine whether to make a task of the actionable context data available on the client device.

16. The client device of claim 15, the active business client to selectively access one or more services based on whether the task is made available on the client device.

17. A method in a server, comprising:

generating business context data that describes a resource, a view, and actionable context data related to a business scenario, the business context data not specific to any particular user interface (UI) capability of a client device; and

transmitting to the client device the business context data, the client device having a business client that identifies UI capabilities of the client device and generates a UI component based on the business scenario and the UI capabilities.

18. The method of claim 17, wherein generating the business context data comprises:

generating data of a model layer of a model-view-controller (MVC) architecture, wherein the view and controller layers are implemented by the client device.

19. The method of claim 17, wherein generating the business context data further comprises:

annotating an action associated with the actionable context data to indicate what resources and capabilities are necessary to execute the action.

20. The method of claim 17, wherein generating the business context data further comprises:

accessing data components from multiple backend systems.

21. The method of claim 20, wherein generating the business context data further comprises:

accessing a meta object model that includes mapping rules to determine how to generate an instance of a composite meta object from components accessed from the multiple backend systems.

22. An article of manufacture comprising a machine readable medium having content stored thereon to provide instructions to cause a machine to perform operations including:

generating business context data that describes a resource, a view, and actionable context data related to a business scenario, the business context data not specific to any particular user interface (UI) capability of a client device; and

transmitting to the client device the business context data, the client device having a business client that identifies UI capabilities of the client device and generates a UI component based on the business scenario and the UI capabilities.

23. The article of manufacture of claim 22, wherein the content to provide instructions for

generating the business context data further comprises content to provide instructions for generating a metadata description of the business scenario;

and

including the metadata description in the business context data.

24. The article of manufacture of claim 22, wherein the content to provide instructions for

generating the business context data comprises content to provide instructions for generating a mashup composite data object having data components from multiple backend systems.

25. The article of manufacture of claim 24, wherein the content to provide instructions for transmitting the business context data comprises:

sending an updated data component to replace one of the data components to reflect a change of the data component in its respective backend system.

26. A method comprising:

identifying actionable context data of a business scenario hosted by a server, the actionable context data to be performed on a client device having particular user interface capabilities, the client device capable of operation while disconnected from the server;

identifying a disconnect condition indicating a likelihood that the client device will be disconnected;

automatically identifying a resource and a service associated with the actionable context data based on identifying the business scenario;

automatically accessing the resource and the service from the server while connected to the server in response to detecting the disconnect condition; and

locally storing the accessed resource and service at the client device to enable performing the actionable context data while the client device is disconnected from the server.

27. The method of claim 26, wherein identifying the disconnect condition further comprises:

determining from a schedule that the client device is likely to be disconnected.

28. The method of claim 26, wherein locally storing the accessed resource and service further comprises:

activating the locally stored resource and service to enable execution of the actionable context data from the local storage.