Abstract: Computer-readable media, methods, and systems are disclosed for electronic data conflict resolution in periodically offline systems. In response to detecting one or more conflicts on a particular electronic data entity, conflict metadata items associated with the one or more conflicts are inserted into a conflict staging data structure. For each of the conflict metadata items inserted into the conflict staging data structure, the conflict metadata items with their associated datasets are retrieved and evaluated. Based on the conflict evaluation, a valid data value is selected from among the associated datasets. Based on the valid data value, the particular electronic data entity is synchronized to one or more backend systems.

Abstract: Computer-readable media, methods, and systems are disclosed for electronic data conflict resolution in periodically offline systems. In response to detecting one or more conflicts on a particular electronic data entity, conflict metadata items associated with the one or more conflicts are inserted into a conflict staging data structure. For each of the conflict metadata items inserted into the conflict staging data structure, the conflict metadata items with their associated datasets are retrieved and evaluated. Based on the conflict evaluation, a valid data value is selected from among the associated datasets. Based on the valid data value, the particular electronic data entity is synchronized to one or more backend systems.

Abstract: Disclosed herein are system, computer-implemented method, and computer program product (computer-readable storage medium) embodiments for implementing database cloud platform integration with third-party CRM services. An embodiment includes operating first and second computer systems and interfacing with first and second database components, respectively, that are differently formatted.

Abstract: Various embodiment of systems and methods to execute a rule based on context data has been described. Initially a trigger to initiate execution of the rule is received at a context processing service. A plurality of context parameters included in the rule are then identified. Context data corresponding to the plurality of context parameters from a context database are then retrieved. Context data may be received from a plurality of context providers including: an Internet of Things (IoT) network; and an application executing at a portable electronic device. Based on the retrieved context data, the rule is executed at the context processing service. Finally an action is executed corresponding to the rule based on execution of the rule.

Abstract: A context profile is created. The context profile includes one or more types of context data to be captured, frequency in which the one or more types of context data to be captured, data format in which the one or more types of context data is to be outputted and one or more custom data types. The context profile corresponds to an application identifier. A mapping of context profiles to application identifiers is created. Based on the mapping, the context profile is sent to a corresponding context provider. Upon reception, the one or more types of context data are evaluated. Based on a number of data processing rules, the received context data can be processed or discarded.

Abstract: Various embodiment of systems and methods to execute a rule based on context data has been described. Initially a trigger to initiate execution of the rule is received at a context processing service. A plurality of context parameters included in the rule are then identified. Context data corresponding to the plurality of context parameters from a context database are then retrieved. Context data may be received from a plurality of context providers including: an Internet of Things (IoT) network; and an application executing at a portable electronic device. Based on the retrieved context data, the rule is executed at the context processing service. Finally an action is executed corresponding to the rule based on execution of the rule.

Abstract: A context profile is created. The context profile includes one or more types of context data to be captured, frequency in which the one or more types of context data to be captured, data format in which the one or more types of context data is to be outputted and one or more custom data types. The context profile corresponds to an application identifier. A mapping of context profiles to application identifiers is created. Based on the mapping, the context profile is sent to a corresponding context provider. Upon reception, the one or more types of context data are evaluated. Based on a number of data processing rules, the received context data can be processed or discarded.

Abstract: A system and a method for providing software supportability involve a server receiving a first electronic record from a client application on a mobile computing device. The first electronic record describes activity that occurred at the mobile computing device during a request sent from the client application to the server. The server creates a second electronic record that describes activity that occurred at the server while processing the request. The first electronic record and the second electronic record are stored in association with each other and can be analyzed to determine issues with performance or security. A diagnostic application, based on the stored first electronic record and the second electronic record, identifies at least one faulty component at the server or the mobile computing device to correct the identified at least one faulty component.

Abstract: A server system may include a request handler and a storage. The request handler may receive at least one request from a program on a user side. The storage may include a first cache and a second cache, storing data in format directly compatible to the program. The first cache stores only data matching to a server. If the at least one request corresponds to a change to the data from the program, then the second cache stores the at least one request and the request handler sends the at least one request to the server for updating the change.

Abstract: A system and a method for providing software supportability involve a server receiving a first electronic record from a client application on a mobile computing device. The first electronic record describes activity that occurred at the mobile computing device during a request sent from the client application to the server. The server creates a second electronic record that describes activity that occurred at the server while processing the request. The first electronic record and the second electronic record are stored in association with each other and can be analyzed to determine issues with performance or security. A diagnostic application, based on the stored first electronic record and the second electronic record, identifies at least one faulty component at the server or the mobile computing device to correct the identified at least one faulty component.

Abstract: A server system may include a request handler and a storage. The request handler may receive at least one request from a program on a user side. The storage may include a first cache and a second cache, storing data in format directly compatible to the program. The first cache stores only data matching to a server. If the at least one request corresponds to a change to the data from the program, then the second cache stores the at least one request and the request handler sends the at least one request to the server for updating the change.