Abstract: Methods and apparatus, including computer program products, are provided for handling database table changes. The method may include receiving, at an event processor, a request from an application to subscribe to a database table event at an in-memory database; storing, at the event processor, a subscription to the database table event; sending, by the event processor, a subscription request to the in-memory database, wherein the subscription request indicates a subscription to the database table event; handling, at the event processor, a notification, wherein the notification is received on behalf of the application in order to determine whether to publish the notification to an endpoint coupled to at least the application, wherein the notification indicates an identity of at least one database table at the in-memory database that has changed; and publishing the notification to the endpoint. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: Various examples are directed to methods and systems for describing message payload data in computer messaging. A messaging client may receive a first message that comprises first payload data. The messaging client may identify from the first message a first metadata identifier data and send a metadata request to a metadata source indicated by the first metadata identifier data. The messaging client may receive from the metadata source first payload metadata describing the first payload data. The messaging client may identify a first payload record from the first payload data based at least in party on the first payload metadata.

Abstract: Various examples are directed to methods and systems for describing message payload data in computer messaging. A messaging client may receive a first message that comprises first payload data. The messaging client may identify from the first message a first metadata identifier data and send a. metadata request to a metadata source indicated by the first metadata identifier data. The messaging client may receive from the metadata source first payload metadata describing the first payload data. The messaging client may identify a first payload record from the first payload data based at least in party on the first payload metadata.

Abstract: A computer-implemented method of user interface control includes receiving request to display data in a user interface and displaying data in a visible part of the user interface. Data requests in a hidden part of the user interface can be assigned to bins. Data requests assigned to a first bin can be transmitted to the backend computing system and a responsive output of the backend system can be displayed in the user interface. If the display request is still active and all of the data requests assigned to the first bin have been transmitted, data requests assigned to a second bin can be transmitted to the backend computing system and a responsive output of the backend computing system can be displayed in the user interface. Related apparatus, systems, techniques and articles are also described.

Abstract: Techniques are described for time series based enrichment of messages that are persisted and published in a flow according to the time series data. Inbound messages may be received and processed to add timing information. The modified messages may be stored as a time series in data storage. In response for a request for a particular sequence or set of messages, the messages may be retrieved from data storage and provided in a flow instance to the requestor. The requestor, such as a consumer application, may replay the data from the messages according to the order of the time series of the messages. In this way, implementations enable a time ordered sequence of messages to be replayed at any time after the initial receipt of the messages, and enable any number of instances of such replay including simultaneous replay of a particular message sequence to multiple consumers.

Abstract: A system for presenting a common user interface (UI) of multiple applications on diverse client computing devices as a web page that includes a set of UI elements leading to the multiple applications. The diverse client computing devices have display screens of diverse sizes. In the system, backend servers host a UI infrastructure including the common UI and one or more object page floorplans of respective UI object pages representing the multiple applications and representing application information and data on the diverse client computing devices. Design tools are available to process the object page floorplans to display, create, or edit the UI object pages. The object page floorplans include a first object page layout including a title bar, a header, an expanded default state, a navigation control, a content area, and a footer toolbar containing actions that are performed upon a corresponding first UI object page.

Abstract: In one general aspect, a method is described that includes populating and transferring parameters across a plurality of applications executable on multiple user interface platforms. The method may include receiving a request to launch a first application executing on a first user interface platform, accessing a plurality of parameter values and populating fields in user interfaces associated with the first application with the parameter values. In response to receiving a request to launch a second application executing on a second user interface platform, the method can include accessing a signature associated with the first application, determining that the signature matches a predefined signature, associated with the second application, generating at least one uniform resource locator of the plurality of parameter values, and transmitting the uniform resource locator to the second application.

Abstract: Techniques are described for employ a mock server that executes on a client to facilitate negative testing of an application and/or other types of testing. The mock server may intercept OData requests sent from an application toward a backend server. For at least some of the intercepted requests, the mock server may determine a mock response to be returned to the application instead of a response that would be generated by the backend server. In some examples, the mock server may employ various mock server extension components to generate the mock response. The mock response may include an error message, warning message, and/or other content, and may be provided to enable negative testing of the application. In some instances, the application employs a user interface (UI) model to provide UI elements.

Abstract: A system for development, deliver, deployment and operation of an application includes at least one memory including instructions on a computing device and at least one processor on the computing device. The processor is operably coupled to the at least one memory and is arranged and configured to execute the instructions that, when executed, cause the processor to implement an application within a platform associated with a namespace for the platform, where the platform is one platform of a plurality of platforms. The processor implements a descriptor having an identifier that uniquely associates the descriptor with the application, where the descriptor comprises a single file that is platform independent and that includes a plurality of namespaces and application-specific attributes for each of the namespaces to enable the application to operate on multiple different platforms using the same descriptor.

Abstract: Various embodiments of systems and methods to control interactions between an application user interface and a database are described herein. In one aspect, a secondary persistency of application data is generated based on a primary persistency of the application data in a database. A request to modify a value of a field of the application data in the secondary persistency is received from the application user interface. The field of the application data in the secondary persistency is updated in response to the received request for modification. A determination is made that the received request for modification influences other fields of the application data according to a set of rules. The other fields of the application data are updated based on the received request. The application data in the secondary persistency is then transitioned to the primary persistency upon request.

Abstract: Techniques for providing an error log include establishing, by a hub computing system, a connection with a back-end computing system, the back-end computing system executing a first computer-implemented programming language; receiving, at the hub computing system, a request for an error log from an Open Data Protocol (OData) application that resides on a mobile communications device, the mobile communications device executing a second computer-implemented programming language different than the first computer-implemented programming language, and the error log including error log entries associated with a runtime processing of a data model; registering, on the hub computing system, the error log as an OData service configured to be provided over an OData channel between the hub computing system and the mobile communications device; and providing, by the hub computing system, the error log to the OData application as the OData service over the OData channel.

Abstract: Techniques for providing an error log include establishing, by a hub computing system, a connection with a back-end computing system, the back-end computing system executing a first computer-implemented programming language; receiving, at the hub computing system, a request for an error log from an Open Data Protocol (OData) application that resides on a mobile communications device, the mobile communications device executing a second computer-implemented programming language different than the first computer-implemented programming language, and the error log including error log entries associated with a runtime processing of a data model; registering, on the hub computing system, the error log as an OData service configured to be provided over an OData channel between the hub computing system and the mobile communications device; and providing, by the hub computing system, the error log to the OData application as the OData service over the OData channel.