Sap Se

Sap Ag

Carsten Brandt

Markus Viol

Lars Erbe

Alexander Rauh

Stefan Haffner

Tobias Haug

Thomas Uhl

Felix Riegger

Christian Voshage

Axel Warner

Karin Bornheimer

Gerd Ritter

Hilmar Demant

Tim Kornmann

Thomas Gieselmann

Niels Hebling

Franz Müller

Aaby Sivakumar

Thomas Konstandin

Abdul Aziz

Mahesh Gopalan

Vinod S Nair

Jayakanth R

Debobrata Bose

Indranil Dutt

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

Techniques are described for dynamically synchronizing applications executed on a client device with backend systems. An example method includes identifying a triggering event associated with a request to perform a synchronization of a client application, where the request is associated with a request for a partial synchronization of the client application. A set of information defining a request context associated with the request is obtained. A set of potential partial synchronization scenarios are identified, where each of the potential partial synchronization scenarios associated with a predefined synchronization context. The request context is compared to the predefined synchronization contexts of the set of potential partial synchronization scenarios to identify a particular partial synchronization scenario corresponding to the request context. In response to identifying the particular partial synchronization scenario corresponding to the request context, a set of synchronization operations defined in the identified partial synchronization scenario are performed.

Flexible configuration of offline synchronization scope

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

This disclosure provides various embodiments for generating reports relating to UI models' compliance with a set of UI style guide rules. A digital UI model is parsed to determine whether a user interface, in a plurality of user interfaces within a software environment, satisfies at least one UI style guide rule in a plurality of UI style guide rules associated with the software environment. The digital UI model defines a plurality of attributes of the user interface. At least one statistical measure is calculated relating to compliance with UI style guide rules. The calculation of the statistical measure is based at least in part on the determination of whether the user interface satisfies the at least one UI style guide rule. A report is then generated identifying the at least one statistical measure, the report configured for presentation on a user interface of a computing device.

User interface style guide compliance reporting

This disclosure provides various embodiments for checking user interfaces' compliance with user style guide rules in connection with a UI development tool. A particular digital UI model is identified in a plurality of digital UI models, each UI model representing attributes of a corresponding software application user interface in a plurality of user interfaces available for access by a UI development tool adapted to modify attributes of user interfaces in the plurality of user interfaces. The particular UI model represents attributes of a particular user interface accessed by the UI development tool. The particular UI model is parsed to determine that at least one attribute of the particular user interface violates at least one UI style guide rule. Results are presented in a user interface of the UI development tool, the presentation indicating that the particular attribute of the particular user interface violates the UI style guide rule.

User interface style guide compliance

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

This disclosure provides various embodiments for performing operations on entities of a meta model modeling one or more software components. A request is received to perform a particular operation of a particular type on each of a plurality of model entities, each model entity modeling at least one attribute of a software component. The request includes an identification of the particular type of operation in a plurality of operation types. The model entities are retrieved in response to the request. A handler object is instantiated of the particular type adapted to perform the particular operation by calling a set of reusable software modules, each software module providing functionality used to perform at least a portion of the particular operation on at least one entity in the plurality of entities. Result data is generated based on the performance of the particular operation using the instantiated handler and reusable software modules.

Unified interface for meta model checking, modifying, and reporting

A method, including executing instructions recorded on a non-transitory computer-readable storage media using at least one processor, may include loading a component from a repository in a first user interface, notifying a second user interface that the component is loaded in the first user interface, performing one or more checks on the component using a check engine and generating one or more check results, storing the check results in a buffer and displaying the check results in the second user interface. The first user interface, the second user interface, the buffer and the check engine may be integrated modules of a single application.

Time application having an intergrated check engine

Growing community of inventors

Mannheim, Germany

Carsten Brandt