Method and system for customizing a software application

• US 10,185,576 B2
• Filed: 06/25/2012
• Issued: 01/22/2019
• Est. Priority Date: 07/25/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Zhao, Jie, Xiao, Youneng
• Primary Examiner(s): Zhen, Wei Y
• Assistant Examiner(s): Wu, Junchun
• Application Number:
  US13/532,445
• Publication Number:
  US 20120278794A1
• Time in Patent Office: 2,402 Days
• Field of Search: 717168
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

The technique introduced here includes a uniform customization system, which can support the customization of multiple software applications simultaneously. Customization data of a software application can be developed separately from the development of the application. The customization data is then stored, via the uniform customization system, into a customization storage. When the software application is executed, the software application retrieves, from the storage, the values of the customization data via the uniform customization system. The uniform customization system outputs the retrieved customization data indicating the current working context of a user, which may be used by the user to locate customization options in a customization user interface of the software application, for customizing functions performed in the current working context.

Claims

1. A method for customizing software applications, the method comprising:

generating customization data determining runtime behavior of one or more functions of a software application, wherein the customization data is generated independently from development of the software application, and wherein generating the customization data includes;

during a first execution of the software application, logging access to at least one customization entry associated with an executed function of the software application;

providing a log report that indicates;

i) the at least one customization entry, ii) how each customization entry is accessed by the function, and iii) how each customization entry is evaluated during execution of the function, wherein the log report further indicates, for each customization entry, a path of navigating, within a customization user interface, from a root node to a node representing the respective customization entry in the customization interface; and

receiving, through the customization user interface, the customization data that includes a value for each customization entry associated with the executed function of the software application;

storing the customization data in memory; and

during a second execution of the software application subsequent to the first execution;

receiving a request for execution of the function of the software application;

determining the at least one customization entry corresponding to the function, relevant to a current working context of a user;

obtaining, from the customization data, the respective value for each customization entry, wherein the value of the respective customization entry affects how the function is performed;

obtaining, from the customization data, information regarding how to locate each customization entry in the customization user interface of the software application; and

executing the function based on the respective value for each customization entry corresponding to the function.

2. The method of claim 1, wherein the current working context of the user is used for locating customization options in the customization user interface of the software application.

3. The method of claim 2, wherein the customization user interface includes a tree structure having a root node and a plurality of other nodes, the root node and the plurality of other nodes representing one or more corresponding customization categories and one or more corresponding customization entries.

4. The method of claim 3, wherein the corresponding one or more customization entries are combined together to determine behavior of the software application at runtime.

5. The method of claim 3, wherein the one or more corresponding customization entries are evaluated and the procedure of evaluation is recorded as a log.

6. The method of claim 5, wherein the log allows the user to identify which of the one or more corresponding customization entries are involved in the current working context.

7. The method of claim 5, wherein the log to indicate at least one of:

a list of customization entries accessed during execution of the function of the software application,

how each customization entry, from the list of customization entries, is accessed by the function of the software application, or

how each customization entry, from the list of customization entries, is evaluated during execution of the function of the software application.

8. A system comprising:

a processor; and

a memory coupled to the processor, to store instructions executed by the processor to;

generate customization data that determines runtime behavior of one or more functions of a software application, wherein the customization data is generated independently from development of the software application, and wherein generating the customization data includes;

during a first execution of the software application, logging access to at least one customization entry associated with an executed function of the software application;

providing a log report that indicates;

i) the at least one customization entry, ii) how each customization entry is accessed by the function, and iii) how each customization entry is evaluated during execution of the function, wherein the log report further indicates, for each customization entry, a path of navigating, within a customization user interface, from a root node to a node representing the respective customization entry in the customization interface; and

receiving, through the customization user interface, the customization data that includes a value for each customization entry associated with the executed function of the software application;

during a second execution of the software application subsequent to the first execution;

receive a request for execution of the function of the software application;

determine the at least one customization entry corresponding to the function, relevant to a current working context of a user;

obtain, from the customization data, the respective value for each customization entry, wherein the value of the respective customization entry affects how the function is performed; and

execute the function based on the respective value for each customization entry corresponding to the function.

9. The system of claim 8, wherein the current working context of the user is used for locating customization options in a customization user interface of the software application.

10. The system of claim 9, wherein the customization user interface includes a tree structure having a root node and a plurality of other nodes, the root node and said plurality of other nodes representing one or more corresponding customization categories and one or more corresponding customization entries.

11. The system of claim 10, wherein the one or more corresponding customization entries are combined together to determine behavior of the software application at runtime.

12. The system of claim 11, wherein the one or more corresponding customization entries are evaluated and the procedure of evaluation is recorded as a log.

13. The system of claim 12, wherein the log allows the user to identify which of the one or more corresponding customization entries are involved in the current working context.

14. The system of claim 12, wherein the log to indicate at least one of:

a list of customization entries accessed during execution of the function of the software application,

how each customization entry, from the list of customization entries, is accessed by the function of the software application, or

how each customization entry, from the list of customization entries, is evaluated during execution of the function of the software application.

15. A non-transitory machine readable storage medium having computer executable instructions that when executed cause a processor to perform operations comprising:

generate customization data determining runtime behavior of one or more functions of a software application, wherein the customization data is generated independently from development of the software application, and wherein generating the customization data includes;

during a first execution of the software application, logging access to at least one customization entry associated with an executed function of the software application;

providing a log report that indicates;

i) the at least one customization entry, ii) how each customization entry is accessed by the function, and iii) how each customization entry is evaluated during execution of the function, wherein the log report further indicates, for each customization entry, a path of navigating, within a customization user interface, from a root node to a node representing the respective customization entry in the customization interface; and

receiving through the customization user interface, the customization data that includes a value for each customization entry associated with the executed function of the software application;

store the customization data in memory; and

during a second execution of the software application subsequent to the first execution;

receive a request for execution of the function of the software application;

determine the at least one customization entry corresponding to the function, relevant to a current working context of a user;

obtain, from the customization data, the respective value for each customization entry, wherein the value of the respective customization entry affects how the function is performed; and

execute the function based on the respective value for each customization entry corresponding to the function.

16. The non-transitory machine readable storage medium of claim 15, wherein the current working context of the user is used for locating customization options in a customization user interface of the software application.

17. The non-transitory machine readable storage medium of claim 16, wherein the customization user interface includes a tree structure having a root node and a plurality of other nodes, the root node and the plurality of other nodes representing one or more corresponding customization categories and one or more corresponding customization entries.

18. The non-transitory machine readable storage medium of claim 17, wherein the corresponding one or more customization entries are combined together to determine behavior of the software application at runtime.

19. The non-transitory machine readable storage medium of claim 17, wherein the one or more corresponding customization entries are evaluated and the procedure of evaluation is recorded as a log, wherein the log allows the user to identify which of the one or more corresponding customization entries are involved in the current working context.

20. The non-transitory machine readable storage medium of claim 19, wherein the log to indicate at least one of:

a list of customization entries accessed during execution of the function of the software application,

how each customization entry, from the list of customization entries, is accessed by the function of the software application, or

how each customization entry, from the list of customization entries, is evaluated during execution of the function of the software application.