USER INTERFACE CUSTOMIZATION SYSTEM

• US 20090063988A1
• Filed: 08/31/2007
• Published: 03/05/2009
• Est. Priority Date: 08/31/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Graeff, Oliver, Reimitz, Uwe, Conrad, Peter, Weigmann, Florian
• Granted Patent: US 8,370,751 B2
• Time in Patent Office: Days
• US Class Current: 715/744
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

A system comprising an application data retriever configured to request application data; a mapping data handler configured to request a set of mapping data which is associated with at least a selected user interface (UI) view; a customizing data handler configured to request a set of customizing data associated with the selected UI view; a UI data aggregator configured to combine, at least, the mapping data and the customizing data into a UI view generation data set; and a UI generator configured to generate a UI view utilizing, at least in part, the UI generation data set from the UI data aggregator and the application data.

Claims

1. A system comprising:

an application data retriever configured to request application data;

a mapping data handler configured to request a set of mapping data which is associated with at least a selected user interface (UI) view;

a customizing data handler configured to request a set of customizing data associated with the selected UI view;

a UI data aggregator configured to combine, at least, the mapping data and the customizing data into a UI view generation data set; and

a UI generator configured to generate a UI view utilizing, at least in part, the UI generation data set from the UI data aggregator and the application data.

2. The system of claim 1 wherein the mapping data handler includes a mapping data creator configured to at least create in the mapping data an association between a fieldname included in the application data and a UI element included in a plurality of UI views.

3. The system of claim 2 wherein the mapping data creator is further configured to set, in the mapping data, a value for a control element which indicates how a user interface element of a UI view is to be treated.

4. The system of claim 3 wherein the control element which indicates how the user interface element of a UI view is to be treated, is selected from a group of control elements consisting of:

a control element that controls whether a user interface element is hidden;

a control element that controls whether a user interface element is disabled; and

a control element that controls whether a user interface element is mandatory.

5. The system of claim 1, wherein the mapping data handler is further configured to handle mapping data stored in a mark-up language format.

6. The system of claim 1, wherein the customizing data handler includes a customizing data creator configured to create an association in the customizing data between a fieldname included in the application data and a UI element included in a single UI view.

7. The system of claim 1, wherein the UI data aggregator is configured to:

combine a baseline UI view associated with the selected UI view and the mapping data into an intermediate UI view generation data set; and

combine the intermediate UI view with the customizing data into the UI view generation data set.

8. The system of claim 7, wherein UI data aggregator is configured to utilize portions of the mapping data to determine how the customizing data is combined with the intermediate UI view generation data set to form the UI view generation data set.

9. The system of claim 8, wherein the UI data aggregator is configured to, if the mapping data indicates that a UI element of the UI view is to be hidden, ignore the customizing data regarding the UI element.

10. The system of claim 1, wherein the UI generator is configured to:

combine a baseline UI view associated with the selected UI view and the UI view generation data set into an intermediate UI view; and

populate the intermediate UI view with at least a portion of the application data.

11. The system of claim 1, wherein the UI generator is configured to:

request a second application data; and

repopulate the intermediate UI view with the second application data.

12. The system of claim 1, wherein the UI generator is configured to generate a UI view that facilitates the creation of mapping data which influences, at least in part, the subsequent generation of a plurality of UI views.

13. The system of claim 1, wherein the application data retriever is configured to request customer relations management data.

14. A method of generating a selected UI view comprising:

retrieving mapping data which is associated with at least the selected UI view;

retrieving customizing data which is associated with only the selected UI view;

combining at least portions of the mapping data and the customizing data into a UI view generation data set;

retrieving an application data; and

generating the selected UI view utilizing the application data to populate the UI view generation data set.

15. The method of claim 14, wherein combining includes:

retrieving a baseline UI view;

combining the mapping data with the baseline UI view to create an intermediate UI view generation data set; and

combining the customizing data with the intermediate UI view data set to create the UI view generation data set.

16. The method of claim 15 wherein combining the customizing data includes utilizing portions of the mapping data to determine how the customizing data is combined with the intermediate UI view generation data set to form the UI view generation data set.

17. The method of claim 16 wherein utilizing portions of the mapping data includes utilizing at least one control element which dictates how the user interface element of a UI view is to be treated, and

wherein the control element is selected from a group of control elements consisting of:

a control element that controls whether a user interface element is hidden;

a control element that controls whether a user interface element is disabled; and

a control element that controls whether a user interface element is mandatory.

18. The method of claim 14 further including:

retrieving a second application data;

repopulating the UI view with the second application data.

19. The method of claim 14, wherein retrieving the application data includes retrieving customer relations management data.

20. A machine readable medium comprising instructions capable of being executed by at least one machine, wherein when executed cause the machine to attempt to generate a selected user interface (UI) view by:

requesting a first set of configuration information which can be utilized to customize the selected UI view and a number of other UI views;

requesting a second set of configuration information which can be utilized to customize only the selected UI view;

requesting a third set of configuration information which can be utilized to customize the selected UI view and is associated with a user who has selected the UI view; and

generating the selected UI view utilizing, at least portions of, the first, second and third customizing information sets to modify a generic version of the selected UI view.