Skip to main content

Table of Contents

Offline case packaging optimization during synchronization


Only available versions of this content are shown in the dropdown

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.

Optimized offline packaging occurs under the following conditions:
  • A case is packaged during a delta synchronization only when a new work item for the case is added to the user's worklist and the case was not already packaged during a previous synchronization.
  • A case is packaged during a full synchronization only when the work item for the case exists in the user's current worklist.
For example, in an offline-enabled Expenses mobile app, users need to add attachments to existing group expense reports that are later routed to other users, instead of creating a case. In such a scenario, you can enable offline case packaging optimization to improve the performance of an app.

Enabling optimization of offline packaging means that only the flow and its dependencies are packaged, for example, the flow action, sections, data transforms, and data pages. Packaging optimization has the following limitations:

  • Only the packaged flow advances in offline mode. After the current flow, if the next flow is not packaged, the Confirmation page is displayed in the app.
  • Question shapes are not supported.
  • When you enable offline packaging optimization for a case, case creation is not possible.
  • 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.

  • 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.

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