Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Data synchronization in offline mode

Updated on March 3, 2022

When an offline-enabled mobile app is not connected to a network, an action queue stores local user actions. When network connectivity is restored, the contents of the action queue are pushed to the server, and Pega Platform processes them. At the same time, all modified data pages and work objects are synchronized to the mobile device.

When you design an application that users can access with an offline-enabled mobile app, consider the following information with regard to data synchronization.
Offline-enabled mobile apps support two types of synchronization:
Full synchronization
Sends all queued user actions to the server and synchronizes the application model and all data items and work objects to the mobile device. Full synchronization happens in the following situations:
  • When the user starts the offline-enabled mobile app for the first time, and you do not prepackage the access group data in the mobile app executable files.
  • When the user clears the local storage on a mobile device for debugging purposes.
Delta synchronization
Sends all queued user actions to the server and synchronizes only the changed data items and work objects to the mobile device. Delta synchronization can happen in the following situations:
  • When the user starts the offline-enabled mobile app for the first time, and you prepackage the access group data in the mobile app executable files.
  • Each next time the user logs in to the offline-enabled mobile app.
  • After a single user's action appears in the action queue, for example, when the user completes a transaction by submitting an assignment.
  • When the user taps the connection status indicator in the offline-enabled mobile app.
  • During a periodic syncing operation: every 5 minutes, if the server was last accessible, or every 1 minute, if the server was not accessible.
  • When the device goes from offline mode to online mode or a new hardware network interface is attached.
  • When you call a JavaScript API method that starts data synchronization.
Note: When the mobile app initiates synchronization, the server determines if it is delta synchronization or full synchronization. You can synchronize mobile data even after you suspend or terminate an app. However, system settings and status, such as battery life or network connection, can limit or delay the synchronization process.
  • Customizing synchronization indicators

    Customize the background color and font of the synchronization indicators in your mobile app to better suit the overall look and feel. Synchronization indicators keep users informed about the synchronization status when an offline-enabled mobile app regains network connectivity and starts synchronizing data.

  • Offline case packaging optimization during synchronization

    When you design an application that users can access with an offline-enabled mobile app on a mobile device, you can improve the performance of an offline-enabled mobile app when the application contains a large number of case types. You do this by optimizing offline case packaging during synchronization.

  • Propagating application model changes to offline-enabled mobile apps

    Ensure that changes to the model of your application are reflected in your offline-enabled mobile app by clearing the cache of the app and forcing full synchronization.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us