Abstract: An intermittently connected mobile device asynchronously communicates with a middleware system for subsequent communication with a back-end system. Local data objects are given an inconsistent state when charged on the mobile device and the back-end system is not available for data validation. Due to the intermittent communication, a waiting period for possible validation may be hours, days, weeks, etc. If an error occurs, the mobile device then receives and maintains a list of the error notifications. Upon selection of an error notification, an error resolution process is executed on the mobile device so that the user can select between the local data object and the remote data object. If the back-end object is selected, the process terminates otherwise if the local is selected, the user is presented the interface to update the data object, which is again verified by the back-end system.

Abstract: An intermittently connected mobile device asynchronously communicates with a middleware system for subsequent communication with a back-end system. Local data objects are given an inconsistent state when charged on the mobile device and the back-end system is not available for data validation. Due to the intermittent communication, a waiting period for possible validation may be hours, days, weeks, etc. If an error occurs, the mobile device then receives and maintains a list of the error notifications. Upon selection of an error notification, an error resolution process is executed on the mobile device so that the user can select between the local data object and the remote data object. If the back-end object is selected, the process terminates otherwise if the local is selected, the user is presented the interface to update the data object, which is again verified by the back-end system.