Abstract: Disclosed herein are system, method, and device embodiments for transaction merging for offline applications. An embodiment operates by generating an offline store, performing a first operation and a second operation of a transaction over the offline store at a first time and a second time, respectively, generating queue entries corresponding to the first operation and the second operation, respectively, generating transaction information including the first operation and the second operation based on a transaction identifier associated with the transaction; and sending the transaction information to a service provider for synchronization with a remote storage system of a backend service.

Abstract: Disclosed herein are system, method, and computer program product embodiments for allowing a client application to modify failed update requests in an request queue accessible by a mobile device. As a cloud platform may provide offline data services to client applications, a device may need to synchronize a locally stored or otherwise accessible offline store with the cloud platform when connectivity returns. The client application may place failed requests into a request queue, store information about the failed requests in an error archive, and subsequently allow users to directly modify the requests in the request queue for resubmission to the cloud platform. The client application may provide an interface to users to fix the failed requests that is familiar and to the standard interface in the client application.

Abstract: Disclosed herein are system, method, and computer program product embodiments for allowing a client application to modify failed update requests in an request queue accessible by a mobile device. As a cloud platform may provide offline data services to client applications, a device may need to synchronize a locally stored or otherwise accessible offline store with the cloud platform when connectivity returns. The client application may place failed requests into a request queue, store information about the failed requests in an error archive, and subsequently allow users to directly modify the requests in the request queue for resubmission to the cloud platform. The client application may provide an interface to users to fix the failed requests that is familiar and to the standard interface in the client application.

Abstract: Disclosed herein are system, method, and computer program product embodiments for efficiently determining a delta of changed data in response to a refresh request from a data consuming application received by a data producing application. The delta response may be formulated using an association-tracking approach or a change-logging approach. These approaches reduce the number of changes that need to be sent to the data consuming application and improve the efficiency of the replication process.

Abstract: Disclosed herein are system, method, and device embodiments for transaction merging for offline applications. An embodiment operates by generating an offline store, performing a first operation and a second operation of a transaction over the offline store at a first time and a second time, respectively, generating queue entries corresponding to the first operation and the second operation, respectively, generating transaction information including the first operation and the second operation based on a transaction identifier associated with the transaction; and sending the transaction information to a service provider for synchronization with a remote storage system of a backend service.

Abstract: A method for providing mapping between a first data model and a second data model may include sending a request for metadata to a data producer providing data using the second data model. The metadata may be received from the data producer and analyzed to determine a structure of the second data model. System tables may be created based on the analysis of the metadata. The system tables may include data tables to store data from the data producer and to provide the mapping between the metadata of the second data model and the data tables in the first data model. Requests may be made to the data producer for data to be retrieved and populated in the data tables using the first data model.

Abstract: A method for providing mapping between a first data model and a second data model may include sending a request for metadata to a data producer providing data using the second data model. The metadata may be received from the data producer and analyzed to determine a structure of the second data model. System tables may be created based on the analysis of the metadata. The system tables may include data tables to store data from the data producer and to provide the mapping between the metadata of the second data model and the data tables in the first data model. Requests may be made to the data producer for data to be retrieved and populated in the data tables using the first data model.

Abstract: A server system may include a request handler and a database generator. The request handler may receive at least one request from a mobile client device on a user side or from a source server. If the request handler determines that the at least one request requires an initialization of a first mobile database in the mobile client device on the user, the database generator may generate a second mobile database in the server system populated with corresponding requested data from the source server, and the request handler may transmit the second mobile database with the corresponding requested data as a file to the mobile client device. The file of the second mobile database may be stored on the mobile client device as the first mobile database.