Modification Free Tagging of Business Application User Interfaces

• US 20110078600A1
• Filed: 09/30/2009
• Published: 03/31/2011
• Est. Priority Date: 09/30/2009
• Status: Abandoned Application

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Chadzelek, Thomas, Guertler, Jochen
• Application Number:
  US12/571,116
• Publication Number:
  US 20110078600A1
• Time in Patent Office: Days
• US Class Current: 715/765
• CPC Class Codes: G06F 2209/545 Gui
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

The present disclosure involves systems, software, and computer implemented methods for modification free tagging of business application user interfaces. One process includes operations for receiving a selection of a particular user interface element for tagging. If at least one bound data object is associated with the selected user interface element, tagging data for the bound data object is received. The tagging data is stored in the personalization settings of the application, and a listener function associated with the bound data object is defined.

Claims

1. A computer implemented method for causing one or more processors to apply tagging data to a data object used by an application, the method comprising the following steps performed by the one or more processors:

identify a selection of a particular user interface element of the application for tagging;

if at least one bound data object is associated with the particular user interface element, receive tagging data associated with the at least one bound data object;

store the tagging data in personalization settings of the application; and

define a listener function associated with the bound data object.

2. The method of claim 1, wherein the tagging data defines a relation between the bound data object and a component of a disparate application.

3. The method of claim 2, wherein the tagging data comprises an identifier of an input value to the component of the disparate application.

4. The method of claim 2, wherein the component of the disparate application is executed with the bound data object as an input.

5. The method of claim 2, wherein the component of the disparate application is a mashup component injected into a user interface of the application.

6. The method of claim 2, further comprising executing the listener function after a triggered user interaction.

7. The method of claim 6, wherein the triggered user interaction comprises modification of the bound data object.

8. The method of claim 7, wherein the execution of the listener function comprises passing the modified bound data object to the component of the disparate application.

9. The method of claim 4, wherein the component of the disparate application is executed with a second bound data object as the input after receiving selection of the second bound data object.

10. A computer program product encoded on a tangible storage medium, the product comprising computer readable instructions for causing one or more processors to perform operations comprising:

identify a selection of a particular user interface element of an application for tagging;

if at least one bound data object is associated with the particular user interface element, receive tagging data for the bound data object;

store tagging data in personalization settings of the application; and

define a listener function associated with the bound data object.

11. The computer program product of claim 10, wherein the tagging data defines a relation between the bound data object and a component of a disparate application.

12. The computer program product of claim 11, wherein the tagging data comprises an identifier of an input value to the component of the disparate application.

13. The computer program product of claim 11, wherein the component of the disparate application is executed with the bound data object as an input.

14. The computer program product of claim 11, wherein the component of the disparate application is a mashup component injected into a user interface of the application.

15. The computer program product of claim 11, further comprising executing the listener function after a triggered user interaction.

16. The computer program product of claim 15, wherein the triggered user interaction comprises modification of the bound data object.

17. The computer program product of claim 16, wherein the execution of the listener function comprises passing the modified bound data object to the component of the disparate application.

18. The computer program product of claim 13, wherein the component of the disparate application is executed with a second bound data object as the input after receiving selection of the second bound data object.