Sap Ag

Theo Held

Martin Schrepp

Ingo Deck

Annett Hardt

Sandra Bicker

Martin Dauer

Till Brinkmann

Erik Oster

Boris Bierbaum

Iris Nieder

Dietrich Mayer-Ullmann

Kerstin Dittmar

Janaki P Kumar

Deborah Elizabeth Rodgers

Susann Stieler

Peter Conrad

Bernhard Teltscher

Carsten Fuchs

Martin Wegmann

Michael Kuehn

Hena Mau

Nadine Beigel

Stefan Kirchfeld

Edward Palmer

Ute Weber-Schaefer

Presenting links to a user includes: (i) identifying at least one of several work center screens to be made available to a user on a screen. Each work center screen is customizable and contains role-specific information associated with a topic in an enterprise resource computing system. (ii): for each identified work center screen, any screen of a particular type to which the user can directly navigate from the work center screen is identified. (iii): the screen includes: (A) for each identified work center screen, a first link providing navigation to the corresponding work center screen, and (B) for each first link, a second link to each screen of the particular type identified for the corresponding work center screen, providing navigation to the identified screen without visiting the work center screen, the second link displayed to indicate an association with the first link.

Presenting a link to a user

A context control interface may include a context name field that is arranged and configured to identify a working context, one or more attribute name fields that are configured to identify one or more attributes that define the working context and one or more attribute value fields that are arranged and configured to correspond to the attribute name fields and to define one or more values for the attribute name fields. The attribute name fields and the corresponding attribute value fields may be mapped to a first set of fields in a first application and may be mapped to second set of fields in a second application and the attributes and the values populate the first set of fields and the second set of fields such that the working context is persistent across the first application and the second application, where the first application differs from the second application.

Context control

In a computing system, an input that a user makes under guidance of a graphical user interface may be received. The input specifies several query portions to be used in searching a data repository in the system. Each of the query portions comprises a value entered by the user that is associated with any of several attributes of objects in the repository. The input does not specify a logical operator between any of the query portions. A search query is generated for searching the repository by: (i) determining whether any of the query portions have a common attribute, and associating any such query portions with each other into a new query portion using a logical OR operator; and (ii) thereafter associating any of the query portions that were not associated in step (i), and any new query portion formed in step (i), with each other using a logical AND operator.

Search query formulation

A request is received to display a first object in a graphical user interface (GUI) of a computer system containing several objects having more than one type, some of the several objects being associated with each other. An operation mode setting is accessed. In response to the request, an overview screen is displayed including a first GUI component presenting attributes of the first object, and at least one second GUI component, presenting information from at least a second one of the several objects associated with the first object, and configured to operate in (i) an auto load mode for automatically loading and presenting the information upon display, and (ii) a deferred load mode where the information is loaded and presented upon the user activating the second GUI component. The second GUI component uses one of the auto load mode and the deferred load mode based on the operation mode setting.

Providing an overview of an object

One implementation provides a method for accessing a window previously viewed by a user in a graphical user interface (GUI) during an interaction with an individual. The method includes displaying to the user a first window in the GUI. The first window contains a collapsible/expandable menu. The menu contains an entry that refers to a window previously viewed by the user. Upon selection of the entry in the menu, the method further includes displaying to the user the corresponding window previously viewed by the user in the GUI. The corresponding window has a data-entry field that contains a latest version of information that is related to the interaction with the individual that was previously entered or modified by the user.

Accessing previously viewed windows

In a computing system, a communication that includes contents retrieved from a data repository and configured to be organized in a table is received from a second device. The received contents are displayed in the table on a user interface. The table includes multiple rows, one of which is configured to remain empty while the table is displayed to indicate a possibility of adding a new row to the table. While the table is displayed, a user input that indicates the empty row and is configured to trigger the new row to be added to the table is received. The new row is added to the table without first communicating with the second device regarding the addition. The new row is configured so that new contents entered into the new row are to be added to the data repository in a subsequent communication to the second device.

Editable table modification

A graphical user interface (GUI) includes a details area containing first detail information for a first object instance. The first object instance is part of a hierarchy that includes several object instances of more than one object. The first detail information is presented using at least one GUI component associated with the first object instance. Included in the details area is a hierarchy GUI component that presents at least a portion of the hierarchy including the first object instance, and providing for user selection of any of the several object instances in the hierarchy. The details area is updated to instead contain second detail information that is for a second object instance selected using the hierarchy GUI component and that is presented using at least one GUI component associated with the second object instance. The details area can include GUI components associated with any of the several object instances.

Visualizing navigable object hierarchy

Usability of a software program can be tested by generating a first electronic record of input events that a user executes with at least one input device during a test session. The operations comprise applying the generated first electronic record to a predictive model to generate a prediction for performing the predefined task. Usability of a software program can be tested by registering input events that a user executes with at least one input device during a test session in which the user performs a predefined task of a software program. The operations comprise generating a first electronic record associated with the test session. The first electronic record includes at least one characteristic of the registered input events and a prediction for performing the predefined task. The prediction is generated by applying the registered input events to a predictive model.

Testing usability of a software program

Growing community of inventors

Wiesloch, Germany

Theo Held