Skip to main content

Table of Contents

Excluding data pages from delta synchronization in offline-enabled mobile apps


Only available versions of this content are shown in the dropdown

Optimize data exchange and save time when your offline-enabled mobile app synchronizes with the server, by excluding data pages from the delta synchronization process. For example, you can exclude a large data page with a list of countries that does not change often and therefore does not have to be packaged during delta synchronization.

Prepare the framework for excluding data pages from delta synchronization in your offline-enabled app:

When users work in your offline-enabled app, the app performs delta synchronization quite often. Depending on the complexity of your application, the process might be performance-intensive. You can optimize this process by adding data pages to the delta synchronization deny list in your offline configuration template.

  1. In the header of Dev Studio, click Configure Mobile Offline configuration .

  2. On the Offline configuration tab, in the Configuration template section, click the template that you want to use with your offline-enabled app.

  3. On the Delta-sync deny list tab, populate the autocomplete field with the data pages that you want to exclude from delta synchronization, and then click Add.

  4. On the offline configuration template form, click Save.

When you configure offline support in the mobile channel, you can select the template that you modified to ensure that the data pages you select are not included in the delta synchronization packaging.
  • Enabling support for components in offline mode

    Make all elements of your offline-enabled mobile app work as designed, by populating the list of offline-supported components.

  • Excluding data pages from packaging in offline-enabled mobile apps

    Improve the performance of your offline-enabled mobile app by excluding data pages from the app installation package. For example, exclude a resource-heavy data page from packaging when you plan to replace the data page with a large data page that is optimized for offline mode.

  • Making custom resources available in offline mode

    Ensure that your mobile app displays custom resources and continues the process flow in offline mode by including the resources in the app installation package. For example, you can add offline support for a custom font that matches your company's branding guidelines.

  • Routing case status conflicts in offline mode

    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.

Suggest Edit
Did you find this content helpful?

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us