Sap Se

Sap Ag

Markus Viol

Ioannis Grammatikakis

Joachim Fitzer

Juergen Sattler

Hilmar Demant

Jan Heiler

Sebastian Droll

Frank Schertel

Thorsten Weber

Alexander Rauh

Lars Erbe

Carsten Brandt

Stefan Haffner

Frank Brunswig

Thomas Fiedler

Jens Weiler

Oswald Gschnitzer

Rick Weigel

Axel Warner

Gerhard Wenzel

Felix Riegger

Christian Voshage

Stefan A Baeuerle

Uwe Schlarb

Martin Hartig

Bernhard Thimmel

Frank Jentsch

Juergen Specht

Gregor Karl Frey

Wolfgang M Koch

Marcel Hermanns

Rolf Krane

Matthias Lehr

Thomas Gieselmann

Franz Müller

Karsten Fanghänel

Rashmi Nagendra

Eugen Resch

Aditya Bhatia

An application executing on a pod may generate a content request for a particular version of content. The application sends a request including an identifier of the version of the content to a repository in a cluster of pods. The repository determines, using the identifier, whether the version of the content is stored in the cluster or stored at a database in a different cluster. The application receives a response from the repository that may indicate that the version of the content is stored in the cluster and the response may include an identifier of a content pod storing the version of the content. The application sends the content request to the content pod storing the version of the content and may receive the version of the content without querying the database for the version of the content.

Image scaling cloud database

Techniques and solutions are described for retrieving metadata artefacts from a repository that includes multiple instances of a metadata artefact. The instances can have at least some different content. Metadata artefacts are associated with metadata describing group, searching, or selection criteria, such as one or more of a particular solution, tenant, layer, or version. A request for a metadata artefact can include at least one value for one or more of the criteria, which in turn can be used to identify one or more relevant metadata artefacts. Identifiers for, or content of, relevant metadata artefacts can be returned in response to the request. Fallback logic can be used to determine at least in part what metadata artefacts are relevant to a request, or how to return or process request results.

System and method for selective retrieval of metadata artefact versions

Disclosed herein are system, method, and computer program product embodiments for creating and utilizing configuration providers for layered repository facilities. An embodiment operates by creating or loading a custom data structure for a software application, retrieving configuration information from at least one configuration provider, storing the retrieved configuration information in the custom data structure, and associating the custom data structure with the application and a specific layer of a layered repository facility. When this is done across multiple layers of the layered repository for the same software application, configurations can be efficiently managed for different users having different roles and relationships within an enterprise software environment, while maintaining a user experience that is flexible, extensible, dynamic, and yet consistent and familiar across many devices and platforms, even for users having multiple roles and different relationships within the enterprise software environment.

Configurable provider for layered repository

A client database manager can cause a memory of a client device on a client side of a network to store a first component, a second component, and a relationship value representing a dependent relationship between the first component and the second component. A client processing module can cause a processor to receive, after the storing, a request to process the first component at the client device. The client database manager can send to the server side of the network a request for an update of at least one of the first component or the second component. The client processing module can cause the processor to process at the client device, before receiving a response to the request for the update from the server side of the network, at least a portion of the first component and at least a portion of the second component based on the relationship value.

Rapid client-side component processing based on component relationships

Disclosed herein are system, method, and computer program product embodiments for managing and accessing variants of applications. In an embodiment, a request for an application including one or more contextual parameters may be received. A base user interface configuration corresponding to the application may first be retrieved. One or more interface configuration files corresponding to the one or more contextual parameters may then be retrieved from a layered repository. The layered repository may be partitioned into organizational layers that store a plurality of interface configuration files associated with the application. The retrieved interface configuration files may be merged with the base user interface configuration to generate a composite interface configuration, and the composite interface configuration may be applied to the application at runtime.

Adaptable application variants

According to some embodiments, a business service provider may define a stable user interface anchor entity associated with a business object data structure. A reference field may be associated with the stable user interface anchor, the reference field representing a path to a persistent node of the business object data structure. An end user adaptation to a user interface may then be applied in connection with the business object data structure, the adaptation referencing the stable user interface anchor entity.

Stable anchors in user interface to support life cycle extensions

A system includes execution of a software application based on metadata defining a first plurality of software components, reception of second metadata defining the first plurality of software components, determination, based on the second metadata, of a second plurality of the first plurality of software components for which the second metadata is different from the first metadata, and for which the second metadata is associated with elements of the software application, and generation of the elements of the software application based on the second metadata of the second plurality of software components.

Processing changed application metadata based on relevance

A computer system includes a UI designer client that runs on a client device and is configured to enable creation of UI models. A client engine runs on a client device and is configured to initiate requests for the UI models, receive the UI models in response to the requests and interpret and render the UI models at runtime. A UI runtime server client is located on a server and is configured to interface with the client engine to receive and process the requests for the UI models from the client engine. A repository is located on the server and is configured to interface with the UI designer client and store the UI models as created using the UI designer client and interface with the UI runtime server client to deliver requested UI models to the UI runtime server client for interpretation and rendering by the client engine.

Architecture for modeled pattern based user interfaces

Methods and apparatus for displaying objects in client GUI. A lead selection and scoping information is used to determine whether the object is viewable, and the object is rendered only if it is at least partially viewable. The lead selection and scoping information is used to determine whether data is needed to render the object, and data is received from a corresponding object on a server only if it is needed to render the object. Determining whether the object is viewable in the GUI can be based on declaratively marked entities within the object's view and on view calculation rules. Determining whether data is needed to render the object can be based on declaratively marked entities within the object's data model such as flags indicating whether the data field is valid or whether the binding of the data field to a data source is valid.

Dynamic view computation and display

A plurality of domain-specific service adaptation languages can be supported by a back-end service adaptation system to provide runtime access to a runtime instance of a data object comprising data stored in a repository. By defining a language-specific data access service and parser for each domain-specific service adaptation language, a single, service adaptation language-independent compiler and interpreter can prepare and execute a runtime load that includes an execution plan for retrieving and converting data from the repository for delivery in a data object according to a query request from a consumer runtime environment. A consumer using the consumer runtime environment can define the service adaptation language to be used and provide a parser and source code to enable access to business object data using the back-end service adaptation system.

Multi-language support for service adaptation

Various embodiments of systems and methods for a layering concept for a repository of a user interface framework for Web applications are described herein. The content of a repository provided by different parties (e.g., vendor, partner, customer, user, etc.) is separated. The separation is achieved by assigning solutions to the parties that store content in the repository. Simplified access to the repository is achieved by layering the solutions in a stack and implementing a layer strategy for the layers and their order of access.

Layering concept for a repository of a user interface framework for web applications

A host software application implementing business processes and providing a graphical display associated with a user interface (UI) for a user in a client program executing on a client frontend device that is separate from a backend device storing metadata associated with the UI may be initiated. An automation graphical symbol may provide the user with an option to initiate a test on events of the host software application, during execution of the host software application. A request from the user may be received, to initiate a test on events of the host software application. Information may be received from the user indicating one or more selected specific events for performing the test. The test may be initiated on the selected specific events, based on a state of execution of the host software application at an initial time of the user indicating the selected specific events for performing the test.

Automation of testing for user interface applications

Various embodiments of systems and methods for lifecycle stable user interface adaptations are described herein. All adaptations done by partners/key users/end users to a user interface of a computer software application are preserved during the lifecycle of the application. In one aspect, the adaptations are persisted as additional metadata used for the generation of the user interface. In another aspect, the lifecycle stability is achieved by attaching the adaptations to semantically coherent set of fields placed in the UI that reappear in future releases of the computer software application.

Lifecycle stable user interface adaptations

A component object binds business driven services to a graphical user interface (GUI). The object includes a data model, view model and controller. The view model graphically presents, and the controller manipulates data used by the object. The controller includes an event handler that respond to events generated within the GUI and binds data used by the object to a data source which can be another component object or a remotely located source. The event handler can call a local script to calculate the value of a data element within the object. The component object can be instantiated on a client, and can be configured to communicate with a corresponding component object on a server. The client and server component objects can exchange only that data that needs to be exchanged to maintain the current state of a user interface in the client computer.

Growing community of inventors

Walldorf, Germany

Markus Viol