Provide an uninterrupted experience for the users of your offline-enabled mobile app by routing possible case status conflicts to designated work queues. By adopting this functionality, users continue to use the app while a designated person (for example, a system administrator) can address the conflicts to ensure that no data is lost.

After an offline-enabled app synchronizes with the server and the case status on the server progresses in respect to the case status on the client, Pega Platform creates a status conflict case (named Sync Error Case) in the Pega-Work-OfflineSync class that contains data from the case on the client. Pega Platform then routes the status conflict case to the work queue that you define, so that a designated person can address the conflict. Pega Platform stores the case data from the client on the corresponding pySyncErrorCase clipboard page.

For example, a uPlus employee submits an expense report through the designated company app, and then switches the mobile device to airplane mode because of a business flight. During the flight, the employee, whose app is now in offline mode, decides to make changes to the expense details and resubmit the case. The changes are queued for synchronization after regaining connectivity. However, at the same time, the employee's manager approves the expense report in the web application. After the employee gets off the plane and goes online, the app synchronizes with the server and a case status conflict arises because the case has the Resolved status on the server and the Pending approval status on the client. Pega Platform creates a status conflict case that contains the data that the employee updated during the flight, and then routes the status conflict case to the system administrator that analyzes and addresses the issue.