Abstract: This disclosure describes software for supporting an application. In one aspect, software for supporting a business application receives error and dynamic context information from a remote business application in response to an incident. The dynamic context information at least partially identifies one or more business objects (BOs) associated with the incident. The software is further operable to clone at least one of the BOs associated with the incident. The software can then start a transaction simulating the incident. Conversely, the business application (or other supported software) can transmit error and dynamic context information to support software related to an incident within having a particular execution environment. In response to an automated request from the support software executing a simulated transaction simulating the incident, the supported software communicates a clone of one of the associated BOs to the support software.

Abstract: A collaboration system providing a guided procedure framework for handling business workflows which include non-persistent data. Data is copied from a business object linked to a database to a temporary business object that is independent from the database. Fields of a form are populated with data from the temporary business object. A workflow object including the populated form and guided procedures is provided to the user who initiated the workflow. After the user makes changes to the workflow and the data, the workflow object is relayed to a next recipient specified as having a task for the workflow. When all of the tasks necessary for the workflow are complete, data from the workflow object is integrated into the database.

Abstract: Various embodiments of systems and methods for integrated metadata and nested authorizations in a user interface framework are described herein. User interface components metadata and authorization metadata are stored in one integrated entity. The primary user interface application components have authorization metadata and are checked at runtime for accessibility to the user interface application for a given user. The user interface framework ensures the security of the embedded user interface components via nested authorizations using metadata relations. The metadata relations are used for runtime authorization and policy generation. Generic user interface components are aggregated at runtime.

Abstract: 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.

Abstract: Various embodiments of systems and methods for user programming access to data model in user interface design are described herein. User interface modeling is merged with a scripting language for additional functionalities. In one aspect, scripting enhances the dynamic access to the whole user interface model. In another aspect, additional controller and navigation logic is exposed by means of script inputs. A user can model, bind and run advanced logic through runtime declaration.

Abstract: This disclosure provides various embodiments of software for supporting a business application. In one aspect, the software receives error information and dynamic context information from a remote business application, where the dynamic context information may partially identify the particular execution point of the business application and a portion of the business data associated with that execution point, present a search interface to a support user utilizing search criteria that is automatically populated using the received information, and, upon request of the support user, generates an execution environment that simulates the remote business application execution using the received information. In some implementations, the software is farther operable to retrieve static context information related to the remote business application from a static context information repository.

Abstract: 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.

Abstract: A tool is proposed for supporting active documents. In one embodiment, an active document may be opened in an application program executing at a first computer, the active document being in a format recognized by the application program. Data relating to a first active document may be received data at the first computer from a user of the application program, and a search request based on the received data may be sent from the first computer to a second computer that maintains a plurality of data objects. In one embodiment, the application program at the first computer is unable to perform any functions with data objects at the second computer. The first computer may receive information relating to a result of the search request from the second computer and may store the information in the first active document.

Abstract: Various embodiments of systems and methods for a composition model for components of a user interface framework for Web applications are described. The methods include a loosely coupled method and a tightly coupled method for composing components in a UI framework. The loosely coupled method includes triggering a navigation pipe from an out-port of a first component to an in-port of a second component and defining a context mapping between a first set of parameters of the out-port of the first component and a second set of parameters of the in-port of the second component. The tightly coupled method includes exposing a binding reference from the first component to the second component and specifying a first data model entity from the first component to be bound to a second data model entity of the second component via a binding contract.

Abstract: Various embodiments of systems and methods for improved user interface framework for Web applications are described herein. The UI framework is based on the MVC architectural pattern. An additional controller, a server controller, is included in the server part of the user interface framework runtime. A client controller is running at the client side of the user interface framework runtime. The client controller and the server controller form one logical synchronized controller. The server controller ensures that all needed controller calculations, which would lead to additional roundtrips between the client side and the server side, can be done on the server side. Thus, exact one roundtrip between client side and backend for every user interaction and transporting only the bare minimum of data needed to render the current UI state is achieved.

Abstract: The present subject mater relates computer system configuration and, more particularly, to system configuration comparison to identify process variation. Various embodiments described herein include one or more of systems, methods, software, and data structures to retrieve configuration information from a first system and a second system, apply a set of rules to the configuration information to identify process variants implemented in each of the first and second systems, and output a representation of process variant implementation differences between the first and second systems.

Abstract: The subject matter relates to software application collaboration and, more particularly, collaboration between software applications via formular updates. Some such embodiments include systems, methods, and software to receive a definition of a content item from a first party, wherein the content item is operable within an application of a second party to cause data to be exported by the second party's application in a manner that can be imported to an application of the first party. Some such embodiments further include sending the content item to the second party.

Abstract: Displaying a plurality of objects on a grid. Metadata indicates an object's display column and span. A lowest position is determined from objects displayed in the same column span. The object is displayed in the column span at the lowest position. A lowest position is determined after the last object is displayed. The grid is resized to minimize whitespace beyond the lowest position to border whitespace. Display overlay of first and second graphical objects. When the first object is directly manipulated in a GUI, the second object is automatically manipulated the same way. When the first object is scrolled in a first direction by a first amount, the second object is automatically displaced opposite the first direction by the first amount. When the first object is resized in a first dimension by a first amount, the second object can be automatically resized by the first amount in the first dimension.

Abstract: 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.

Abstract: Methods for synchronizing data in client-server architectures are described. A client stores data in first and second fields. The value stored in the second field depends on the value stored in the first. When the client writes a new value to the first field, it disables writing to the second field. The client sends a refresh request and receives a refresh response from a server. The refresh request and response contain differences in data stored in the client and server fields. If the refresh response includes a new value for the second field, the client writes the value to the second field. A round trip pending flag associated with the first field is set. A data invalid flag associated with the second field is set. New data can be written to a third field when the value of the third field does not depend on the value of the first field.

Abstract: A computer system can include a data handler configured to receive data for display within a plurality of layout elements. Each layout element from the plurality of layout elements can be identified for display within an application. The computer system can include a boundary generator configured to associate a first plurality of variable-size fields with a first column and associate a second plurality of variable-size fields with a second column. Each layout element from the plurality of layout elements can include at least one variable-size field from the first plurality of variable-size fields and at least one variable-size field from the second plurality of variable-size fields. The boundary generator can be configured to define a pair of alignment boundaries using a predicted size of each of the variable-size fields from the first plurality of variable-size fields.

Abstract: 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.

Abstract: In an aspect there is provided a method. The method may include providing, at a repository, storage for a plurality of tenants, providing a plurality of layers, and providing a plurality of versions; and separating, based on the plurality of layers and the plurality of versions, data for each of the plurality of tenants, wherein during runtime one of the plurality of tenants corresponds to the plurality of layers and one of the plurality of versions. Related apparatus, systems, techniques and articles are also described.

Abstract: 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.

Abstract: A non-transitory computer-readable storage medium storing code representing instructions that when executed are configured to cause a processor to perform a process. The code can comprise code to receive, on a client side of a network, an indicator that a first software object has been moved from a first application into a dropzone region of a second application. The code can include code to receive an indicator that a second software object has been moved into the dropzone region of the second application, and code to access a plurality of dropzone conditions. The code can include code to determine that a dropzone condition from the plurality of dropzone conditions has been satisfied based on the first software object and the second software object both being moved into the dropzone region, and code to send to a server side of a network an indicator that the dropzone condition has been satisfied.