Skip to main content

 –

Propagating application model changes to offline-enabled mobile apps

Suggest edit Updated on November 9, 2021

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.

For example, you can modify the flow of your expense reporting application by adding a subprocess for creating a new expense category. Then, make the new flow available to users by propagating the change to their mobile devices.
  1. In the navigation pane of Admin Studio, click MobileManage cache.
  2. On the Manage cache page, in the Clear cache section, click Clear cache.
Result: When the offline-enabled mobile app next connects to the server, full synchronization updates the app with the application model and data from the server.
  • 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.

Did you find this content helpful? YesNo

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us