Sap Ag

Sap Se

Jens Böckenhauer

Holger Bohle

Sven-Eric Eigemann

Jens Ruths

Techniques for managing user interface (UI) building blocks (UIBB) include presenting, by a form repeater UIBB, initial UI representations of structured entities through a graphical user interface (GUI), each initial UI representation including one or more fields; receiving a trigger from a user through the form repeater UIBB; determining, based on the trigger, an event condition; and based on the event condition, replacing, by a substitute UIBB, an initial UI representation of a particular structured entity of the initial UI representations of the structured entities with a substitute UI representation of the particular structured entity.

Managing user interface building blocks

One embodiment of a method comprises adding an action script to an ordered stack of action scripts maintained by an execution controller, wherein the added action script corresponds to a navigation input received at a first application, the added action script is unpopulated by a data input, and the added action script is added last in an order of the ordered stack. The embodiment also comprises providing the ordered stack of action scripts to a second application by the execution controller, and executing at the second application the ordered stack of action scripts according to the order, the ordered stack having the unpopulated first action script. The embodiment also comprises populating the added first action script with the data input, wherein the data input is received at the first application and the populating occurs after the executing.

Method and system for data preparation and communication between software applications

A method includes receiving by a first application an input from a user; performing a service by the second application, the service related to the input received by the first application; obtaining a log of all data locks set by the second application while performing the service, wherein the log indicates a data lock object and a data lock argument for each data lock set by the second application; and setting a generic lock having an associated generic lock object and a generic lock argument, wherein the generic lock argument indicates the data lock object and the data lock argument. In one embodiment, the a unique checksum is created, using an algorithm, for every service response.

Growing community of inventors

Wiesloch, Germany

Jens Böckenhauer